why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- c1a4685fc52fbc7781a674367ddc08065296618a83657413700e6aaec173b29c
- request
- fbcb866664c349d9ab76695bf9ca781da79f06de7a72e209fd95b3106a8b4ffb
- transaction
- a26a79985ec863b85593ba3eb52bf2c9ba260c94f5748ce5ef511856a3146107computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33906
the chainentry 33906
- sealed to the entry before
- e6d9aabb12bdb97bc90fea9d83da839b207cb7207ce144e9b1d3656cec8f9ade
- this leaf
- d58032fb9e1016106a605df630a78b964d6c77d522ea5a212d5397b7b398a255
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZYmPv7Bmwx0De3iorQwWb+tSfumgUCvRyjyvvzhPZRRLi7QLTpxp+dUk1E8lhFWLoW9kscj0B+L3HHPNc0snAA==