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
- f2f129387d5c3c3fd309ae0645188821b5c6776d801a643ffccce2bb2009f1e9
- request
- 4ba1c6ae600b7f68b376e44ef850181eb2d0c219ab68a9fa50823950b1de53bd
- transaction
- dd13e387b615fec53f02408c4f132f715baa9294b2bdb72f391df51ce6491463computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57866
the chainentry 57866
- sealed to the entry before
- 2e8fcce1c5c75d90cb22224afb1565dcde78687a106ee02820392bb4ab474ee4
- this leaf
- 11de53b72489a0f02477029991cfe5a61dc413ee18ebc8509a264568997605a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tTb6ASrYLgWF95GWKd0jHuRcuM7v36s5Htl9oxWyDVxjdXsNXRw4b2Qs5SpHMFczEFOpQeLGUxxOFy6fA28JBA==