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
- 83951503800444f4dbdde9304998eaf6c2977d053a9a7fca89cc6808c801e970
- request
- f2546e16ff0ad0189ecdf2b5f964ed1befabb0c7d12276d56c8a4373e8f2614f
- transaction
- 8040b587667e03fe99753b2d19da547c54cebb6128a4c3929039e66977d728dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27220
the chainentry 27220
- sealed to the entry before
- c12e6ae5c6357965038c61c0886518e79dc7af390e05bd01fec886508ec3a4ca
- this leaf
- cdc281f1219d6b6a380ebb0820ba67e81abdb8dc514dcfb652efca781f23de30
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LEIOaad7FcKN8WLATE+TAKjItq3Bl9WzMqFW2Q9Afpb1fY0uDsyUth7zPIVoRIV7PzMhBkzNk9EL5rjM25qEAg==