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
- ade3370500dba77520e478677698fe3622b1e70498f25d5857e60a4e994ee6a6
- request
- 9f1da057de4807a43e3213e19746f58008dfb5aaceb2e9a3ef1e637a76c1d9c9
- transaction
- d790d317027c1e15639b0e075268e9224d8b7430e2ce448c5e1951f6ba47c300computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66815
the chainentry 66815
- sealed to the entry before
- 7e180eefdbba4e428d08d1764dff076b8ccbf8e32ec6a616f88f16b45e4ec863
- this leaf
- a04cd42b1048cf824a0be0ffdebd32d653b6898a1c42d2c8670e2e6ba3f290a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ruF28p75QhCs4PGo98Oa5HAf0K7Tfftql8jKXLSXnyiEXsJEjZ7lf4HP6Yg1OQkLLFuSVBBHSVlQupKLRBaJDg==