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
- 5e0b3fcd7daa5070cf3e0a67d4e881a49b06a9af5f011b8a748e20bc379a7549
- request
- 8f6579f4073c657c533de8cd103e789f3abd55b7964b6990241294df9a87af73
- transaction
- 3a3fabd0d39a67813e5bd92c80c33037c74162adf0a34fa98ed33a6fef599ec6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29148
the chainentry 29148
- sealed to the entry before
- 78c4151755dd069959dc9472302b0ef19f082a67617823f4d84db9260c855949
- this leaf
- 8760b92027f128007e3d8a970a2d756a74b096647ad16f5ff29ab3be3b3e79a9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eXgYEjpMMxU3wbTzHuieeB38lK6RvvRPQ8Nmt5CefVPynDPa5/KFUgoIlFgGIIGg/rjcWpkbiWz1kFA9izRjBA==