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
- 8e1829ef14d208490c2908b656739776cc1ed2954b6c50ae8f222be1216332a2
- request
- 05a47d73b107098736a6274660c8d85208813f021462528680de09f8787c69f0
- transaction
- 22c5e0d2a56a4c8b78fc876e30ea6d81d2f6d06cf99d073cd6fb963d0eac9e36computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61218
the chainentry 61218
- sealed to the entry before
- a050214a4e85ac686313e658fbeae20d06511d542d2fecf4848d6f9d2367d596
- this leaf
- 1cf62d2e881ea1553a66ad9835f5a10c91daf5e1834a4aa0ccc240f18284d419
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fdv88tuMJdGB1THhYKJuLKshTPmxy0lOF3LLag+j0Ye0lCI/f84LoAzJb7vqvgliZJrIfD2doAJxySxbfLprCg==