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
- eec0b3fe0599dbb59b3a268d19ef911f3efa94055ff48819ec24e2f651c9258c
- request
- 9c8773548646686615db3d5c7840f5fe8cec4dd9d816d5366aa01052ce84f673
- transaction
- 50d8a7fdf0b3d05a9a22a4ed02ffce31c195930c58141d8a578c733d560e43c4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1157
the chainentry 1157
- sealed to the entry before
- 62ca1824ad569ae127fc80e1029c53e051723685550e7d283e37bf4031cdf68f
- this leaf
- 3aaa616e0a63740b27bf60959e9dd22872b31bfbb308564fe20c15fa0dda00ad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- poUH4gsTn+RaYCVPVArPBJCsBHwhMVuPt9p/FfQ6iA23VbDn3zz39nFWF7D7tdKbLpZveYBTECzC3CuaqjtHBQ==