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
- 4843fa5de8d716f7adb4ff3f06706ea8a8affc2f57a41970047d07b7c39dd071
- request
- 077b1fb73cfc98228840c494971d03e5174b6e62d3405ad2a471608d990f5eda
- transaction
- e2232135696a72a21af514e1b6228002b92a045bd9e565814fb30f7ceed1f10bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27035
the chainentry 27035
- sealed to the entry before
- 3dd533133a6197e7e05da3edf35bb81999d6878a0c6d8f5c23b1a9344fe43105
- this leaf
- 83c8d4b063f9467c64d60f1c7126c1c7e5ec8bde0485d78bb19896ffbc1fa1d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZQB7SIwnXp+1ALgaz1dT3O2GIKA1OhlpDSn/Xep6QCdlIPf+PYHM2jpzJTFxJYAxv/NXL1/Di+9aOqHhu8hvDA==