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
- 8ff8fb7b6e52606ff719a710c885ae0de9f9ab675bd16e69e26b81e8479daf73
- request
- f92e69520aed9832de173080f58dc3b2909732c4b8da99ca961763b6c2ebe150
- transaction
- fac06f14f332d7e2844feacf542f73b8bebf3aa00f38b6672ea9e8a989d2dc33computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59608
the chainentry 59608
- sealed to the entry before
- acef8a09051a7b40670ca5fe7e73d3940b71da658923d2fe53680d827d3034c4
- this leaf
- a4721c3898db624e288d3abdb70397c4a1ba00cae555ec829b20aaf2923bc387
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jy+1o5GCpu+xvlb4RdWav9Ffoc/2P7kZUVZjtcj9uHehxG7PNDZuAi4f9RuPdMfusVlsDMB9nMw5BXtOWbANAA==