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
- 880d03c5abb4a684d0aefbe9dbcc4ef58c13bda4e2c439223dc849f49faef0ae
- request
- c86c0bb9eebf4da292ed5edafe5c7967ef27fd82a085079849bfbd311a79c901
- transaction
- 1767ff1081e1c4408ae0ce94f555ea6eab161179d09aeff182e9fa426355aab9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74808
the chainentry 74808
- sealed to the entry before
- ef77f8c5b1f2c5cd94b40bebd9cc782456c4c9382acbaeee3b39a10460875880
- this leaf
- 6043077307239df733d439766aeeba592e71cdd98faae7ccbc064de7e5ca84d4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DqXR2SQR7aPQxI/sJZjAYa2KTUW33Vsu2Zm3LdeoHb77HsIwgXOs9RKUxaaADskHfoLOl3VniJ27HvuVn5pBCQ==