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
- ad3289c0ddb1e090b230813600d0b236e96657dc03d09d84fc638beefb1dfcc7
- request
- d635ce07dc52d9a6d431a29bd38e3bd32fc85e21e9553025db34351d56db5e61
- transaction
- cf496f805711e5cd49dcd7623d8371b8cdbfb85ad4c23535bd62bd0d55cba18dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52445
the chainentry 52445
- sealed to the entry before
- 31834b25432369fcbb281de4d13f65a61d4567abbc68677db32bfa56e48d5bdc
- this leaf
- ae1f8de5a9ae312c4af50e506a4d4c01efc0e4de2321eb46028ef6e2537d85a6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- k67jPAnumxywfoVZGKNYkNTpeRGNxeoR1mdIFVJ1nNUuWbr9mh0Hp252838dsOpGgYK2eYD5866SBQ2Bl0aZBA==