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
- 6e388dc477f6f2774258b20567726dfa4981385adce3f6b5ede8bb7b732dc20b
- request
- 2d5912a666dd07de994cc0ab24d446851503e757f90decf7ae6d4b5ae7024afc
- transaction
- 1306fd169adb684a9ae62ffc5efac3aed165d91af8a2acbb1bc5998347b8186acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20210
the chainentry 20210
- sealed to the entry before
- 5a42a710568298a6ce1b3630e284a41c8e309e18c70a845dfba0a3b2c5475c80
- this leaf
- 2ecc201a1e0b4bb14982b11723195fc5311403f2ceec703184afd1e795b87635
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M9OvATqdsRw6DvU8OjH2Bu3ddxAfAARqoAFNkgRe6iDAhivMmvBchbhpRFswD5t14B58eJkFrxZdtEb8L6x3CA==