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
- 85e21218b4c5b802171a1bc65cfb502136bf282cebbd4e23026784e000b335b0
- request
- 654fbcfb51908e5fc324c0881df459ce41045c22898efc618305ddf451debea3
- transaction
- e1a0b18a0ff0d6677ca0a80dbfe42f3c63656e83ea138b96c7973cca7042af28computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41996
the chainentry 41996
- sealed to the entry before
- 27f841f17ac71141c857a1d398a8365545d26eaa34a9deb8914e72d3a0cb39cc
- this leaf
- 33eb77d8bee7d14d2c055ed0e6854b5f2f25b018d354a9ba8b84942f24655bb3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0tfo5EiTB49jEBB0Pg7xiqjenNTY9jj7Of1ETbWLDbZGb/KaSG2U8tj8bEL68Xf9yP6g+UCN3WYiwTrgrFofAw==