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
- 3a220cc8994df26aaa8cafe942de5cec235559da501090fcee70b27b2b019297
- request
- 38f3299157bcd98539f61ed7bec3818955c99222b26991fb6860c7a444e0d4b0
- transaction
- 8845daff73a22384c3db18520d52a35f7d77b8710280cfe38868bc616e88f668computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2215
the chainentry 2215
- sealed to the entry before
- 125c50888cda39ad1da310ff6d0f3c06911e3122cc2c633b51912f76e7026ef0
- this leaf
- c048b5f2f2a0603789778386e7adcaae278900d0d483a362920bfa19a645dee4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HM9xs3u+W0j57j54K0hMatR3U3pDaPuhCAT+FghesY5v/iZs4nOU4qqxc9uMeTE0tepvXaRRM0Ipu0jTTcZ7CQ==