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
- f6919fa450a126ca3550fa4026eb9a570ad02f10dd654a2c1f1491ce6561a0b7
- request
- 736d435111c5d5239e673426fb3b0b83f0accf464533503501c31ef7a9a57a42
- transaction
- 93e0c5fda0ebb583241760ba5874fd7ff1c7803ec0254ff8215f98384b2a29b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2340
the chainentry 2340
- sealed to the entry before
- 3555dccfab6282830cafc8b066401bab859631e752e1f06cbd7f2b23a098133b
- this leaf
- 2c9f11fda45b72d9bfc3b8a98634fc880e76b08c2e8d0b1a442ac0181d6db32e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PNStjSt81eVZgPlw2pO5Heo7PdQ0aM7eUbxNljocalJUTZqxdx85UBhPT5vOWAvOGzACmBgfYmiwMTdJ8QtCCQ==