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
- a2b85b270f6e7b65884afb0ea3dcb6f2d1caf62243595e4f4b34af0c80652ad5
- request
- 3bbac08dbaa20b73984c50fc9f846962871d2d54318234b1b65e9c31c2000464
- transaction
- a3a37e9ce1db4e97321ba8816c81f5ac35f44e3fe06c8f81afe301ab52d77291computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22293
the chainentry 22293
- sealed to the entry before
- e7a30e440720f2ea981009c1617f49a260f3a934df81bda0abab1a954cb8b3a5
- this leaf
- 0cc0307533f22776c432107dcd4406dfac453e7b678b94d1a568a6cb1de850a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- C2naITRJ+X6dImBaRdMfBrxx532b1SBsNMxEJv5uueRMHN3U0v8S7LcDUAqXo6V3L6afYuxVDe4gP9RexuW1Cw==