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
- 7c95b753893c4ef82e78c7f5bb06bdedf76e5d36194e29fed6d422428f81650e
- request
- 883e1dd71b2d22bc8bf1494b781f3452d49b00785b63d93bee6ce1f3198e00b9
- transaction
- 55f5aee3b2042479e2479c538ee578c02ca3cfb6dba23cfdd97550b9a495a587computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25808
the chainentry 25808
- sealed to the entry before
- b4fc4afc876592acf0befbcc4dd63ec904cd1389fe99913ce322e5164aefb1f9
- this leaf
- 68defadb91cc8555a187e6da5b70388a51fca32b7b9a062285dd79d2512b231e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b95kDsWHy81K6CIWfQdvdCnd6dRuFr6cJSGUgpPRBdg3/epVwHJww4LJfEM5eTwA6g9IdgtPcNJVMxs3NCS/Dg==