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
- 336060e017efe8bc61502fb96a605ba67be052db26ad1153135cfe8dda1a5d91
- request
- e5e8914f0698499ba4175c66eecb08852287af27220de2bb70bd24f969d2170a
- transaction
- 55f05d8fc792270ed14fa464b6a141da4d4e1ed0f379a1f58d0a6f53bb6a9003computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21913
the chainentry 21913
- sealed to the entry before
- 6a3283c5ffac1a31d4b6417b576d60b218b025389ffab416e31ed87715088373
- this leaf
- da5691a32be5887e27185fbba20f0286b74b1f9148229f9c59f29c02db10d493
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YQ+PT8/ll6VORekkwyGDCFsCJ3OJ/PH+c9tRXe92AgA33l8CxRmkQaHhcDg0AXWavPZ3tpHQcnfNXSyTAMKNDQ==