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
- adb5b110d38d9f18dc8059bedd2159d1e06905bdaae730e9b8408aff9c472d01
- request
- 717748fba6aeba9ebdb80e48fe461f96577574049b84871d60d91283c0fb5c35
- transaction
- 8ff56b7c258163f5434a865632b8aa7a3038a129c83303d86c7b47299f2eead9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23658
the chainentry 23658
- sealed to the entry before
- ecf7d9d00dc077a92574d3042eb1440e38ecfa3c2fe89940e05c683d58d288fd
- this leaf
- d4285ec620dcb0de7e837114596a5a87f5bc34e1af30e7df3f00e4f7a37b6612
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6Rw4QJlkxf5QPMPyi6Fp2JyLMu06r/Jenwu8XyQWP3TqWar1RmJ74iQYOVXQybEQDEkOAfjrR07icf81ZX8MBA==