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
- 5df0df778df4bd722d260d112f3294c5c91bbbfadabbb8605fab5ffe23a412bd
- request
- 02ca52f1daa47159a808edb4a0cb0207caf25609beb232d9269fd9e11ddf38a3
- transaction
- 164144fa2483e3e202ad89d815ab5cbacfc891429c5dd7b96d73c9eed83dfb45computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53673
the chainentry 53673
- sealed to the entry before
- 21f223e0fa8594ee273919edb0261e2fd3b69ab5816fc5bae4dc2a1a72b513a3
- this leaf
- 908b2f30d5511536f3e56642c038db85bc1ef7dfdbef6f3a6d418d98ac193cb8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9ymPxO8vuaFHAatw4a/dOk0KruwrsWmUDo/ySrglKz/fkJrtcNtVcPmIXTFxjxaumEwgAFTuRPag5X5LTZlrCg==