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
- f0c695d12ddfde56228d7b38d8fe00ed2ac5bcdbc0afa4ed8bffec91ee38316b
- request
- 5141afa609a4ad08f0160af83d93b680d7586494d414737e1683b786792fc9a9
- transaction
- 5b406668890c55c854eb2995eeaecd41c5eb833f5e828f55c14c7cc43531add2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53561
the chainentry 53561
- sealed to the entry before
- ab8a328ea4585b660495f3300ba1953599271df365b3fe92099a57df8f16a24c
- this leaf
- 23748e7595104e88c9b5668c99575c66200eb354390e9be6ce688574a32a837a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- doOQBhlkt/eDYTsZrvqXnb44X6chEMPscUg+vfX6LoWQxb69x6b3rLvkn6UPTLJvnJHYk4zSEnKRZrBrRBkgDg==