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
- 6edf2d670f301b490a49d0f7bb4d1feb9c074e3b750b1d3d54fb067e036d3fab
- request
- cf2a819662086648d1265e1437d9ab32c327c73e82cd701e9492136150677ecc
- transaction
- 9cf25ddfd25f356e0d68045dc93d60966924cc393848ddd2584ebfa07f8ea418computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12056
the chainentry 12056
- sealed to the entry before
- 463be6954e79d155c8190eeb6a793e407214a32d567df8362acadfee7c4794d5
- this leaf
- 5096864900eda340be442091dd23f35b5b3c7fdf989456dbad2267402751ff0c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A30TNuePSAFvhVYe7py9fEqrcOrHMETbHTAmAz35Yanriugdb2zztBZooGiHPLt6nyjhgIJooyO53n3tdj3TCQ==