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
- 9c176dc323898794347252a41d841808419bed6d68b0b66a4f38187290910a40
- request
- fccb9c0a50fef6695846430afe94b7987024b4238cff08dbf15034d9e1491c6f
- transaction
- 420da3081690c429447e5001002ebc9ecfc77581d8b5b3328b46902ce0900e7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33029
the chainentry 33029
- sealed to the entry before
- f05941a6173c582108cfa2fbf95d370958eee74df4ea59255ab115059ac933d8
- this leaf
- cb6f77ca3b3e6d85288cb3de63ba1dc19a3f6303112042d418ed6f82896ecec3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F643J92M18HEezywdPpzOdI3KVwqShb7s6FrJu83mSztLfeaqvmcPgMqOPPQIsp0hxNzKbCGSyz70scSuLsvDw==