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
- 096bad08243726d70ddc46a181d5929ba8751483d4b940bdc6b00df9fe02a207
- request
- f24964fcbea0d95c2ad32470ecc326b76c849c94d7a50630f465dd73c3fdb595
- transaction
- 0bb399e76770357bfba92cdf1d5737688dc134a8261f73fbd8e6abd7cbc3c054computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17200
the chainentry 17200
- sealed to the entry before
- 62aa323251d91ccc576e1eef85d68ca55d566d17e6900b99fdebb5dfbcc7e51e
- this leaf
- 23bc540f7d42f03cb21d4b7a2dd72b30b50e1d819da4bbe27f292331ff076940
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HDtOLqfiRCMiPJaythYg+mtPO95dl267Tmwn1+05v73q4OfzNwbxkM9OXoiIhhkG95IbWIVa0kAJLvX5RUZTAA==