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
- 5dcbcc374c3b330409d01e5d28501ef4a2a947a8442a114bc4826b088f986b19
- request
- 00cbe69c168de815d0861f909d5386a3f6f77b843f328943f91eede024aaa519
- transaction
- 859b6bf12dbdb1cabb94e60cc0590a91d22e38ed73fbabd67f650e1bb03fc8ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52348
the chainentry 52348
- sealed to the entry before
- 385affc6716f00c1db6e89f7c453845fd766b28cc21785fe1cd221e5aa8b835e
- this leaf
- 91495511d2b7259d0fe2c0c29b1d5c58c9329b49fe71a956564b78d9a90ae6fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KXJM9k3LDYXh7lFfE8YfPvDqJBmhdcQGuBTK+lBbvTNODXBJuO9406oMAtaz3yVbCZfet5MkF4QOPvqSMNorDg==