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
- 6db1653b52927e5bf2c8b19885d7267d300dd1597bbd88c2b77f08aa0b505e03
- request
- 439c23c43cd4679e162668dbe854282f24b28528c315f64b6dfd848ba86c391d
- transaction
- 5cf459682ed503f0f42f4d654dd2b567476028c63ee44deada7abf14b0312e82computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52424
the chainentry 52424
- sealed to the entry before
- af071b7067f245d9f7100060845aa848aacb0f057f8c7d9488bce0cf5005c3d6
- this leaf
- 1c67e80be7236b9442fb58192a8dba8a4cf3a52e4e32f98329cedc3e5226dab3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OEjJJZPzSbQMEw/kS734M9R6i1qpW0M1giBC4Go4Jky1tNrPyLSa/wOe5yjE/Mbra05IkY3NnEqCP7AXPOz4Ag==