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
- e631e569c887bfa1763173eb9a1dd346621352fc61e6415f33a70c615c3a93d8
- request
- 55a6c991c46e272d38578db5c14bf00842e48f957de613fb176e3447bfa8b473
- transaction
- c4cc78e5c6ad882c20066cfb8fa30194140193f4887e672fa33ba32cc8dc0907computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33007
the chainentry 33007
- sealed to the entry before
- dfdc262f3a8216ad951a40ebf2a10baf940324e4adf133744a3a3ca2c7aa4c39
- this leaf
- 0c26a4d49369c738b491f87cdc5968e52286fb748df10bbb774093cb0c5af299
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xoiWiwEioIAxbztlZ2zZ0QiyjNacWJ1XU/HrvJoVF862j6WAUB7IaeGnX0i7LYQ7wHmMTIgzvfNzE3J4STpABA==