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
- a35661a92a2877e9fdd766402e8602444abe3340a82699a30ff0013df957122b
- request
- 18b88d88813493112caa10085c07c061cd5fcd4efcbe263dadf18a09e6cb5e63
- transaction
- fea2489fa19d31700eba1c333ea4247f7c6d5f39923950c2a629a017583e4a5acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41136
the chainentry 41136
- sealed to the entry before
- 5a2b80d8ddcdf572f06293b1b83271900f96bf152bce198e892e4ce8daa45002
- this leaf
- 9992ffbcf5c5811c847865e3adfbd16a0416c8bfed82b04ef18f7a19d3d31338
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ELvJUCVmwtLfQWcLE1G8ryZXxNF5bdhbeolMixA7dk/3Rn3lGU8T4CiCBfkQWjj1I+VX7friTXm93nZIQHFTCg==