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
- 5318e0633bb7502cb79fb957d0ca8c68d981988bc25a3910493289d32df2f414
- request
- 6d65e8691f0251e287b78aca22d71977dc6dcbf838a35f04d6e4b99e4b1eb867
- transaction
- 1ff6d70cfa87bfb2e988ca06d69c8c4213d7e9ab4dc869ff9059726703f3ee25computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26911
the chainentry 26911
- sealed to the entry before
- d6653d034163d143a291e524910d3b244121e1aeaa6ac230d20eac217274af92
- this leaf
- 5e4e792cef3b30a2554e23ce8681adbdd58a8ddf06c886b4f104f2fd5f8b1eec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wQOuEJn0o29w6orn99U6u43ZCGtAeEoPoMNVPOUDLorskKe4JOOgGxyCFm3T2QeKHkvC3OEAndH+4dyxa4LIAQ==