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
- bc972a82c19d882c8f92d6a181842c376655fb6733d8503e22f5603ad6ba23ea
- request
- a2f722430e2c1192c000d66cbaff3cdae4a8936ef2a32ed2149c0d29497c57d7
- transaction
- f2f774956bbefd1c77c0dd244a65a774a83bfc125084d17a24085453d7bdc2bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28311
the chainentry 28311
- sealed to the entry before
- 620aa0218a3f20920bdda3367b75954bd15cad22e0effb476d79c1f429fd6ae3
- this leaf
- ce549d123cd9e2252d11aa8c041cc32c6a7d2819c53391ba2ce5eeda5350dd80
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NJNmw4qlVyZp3nENDzLDWMdtjnegDnwiZ4viVMNbmYwyEgSanIj6fFbWzXUV4R6oqkt71tn8GOFpj1dOalLgCA==