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
- 46ef1610a5084c61fbe00b90b404136d3a947c54a057d6e385596c40a29abe87
- request
- 1bec6bc0058110b73cf13952893c4ef52efa2d9646d7b51a342abab45b1defe1
- transaction
- a81eb1fb26cb01e0147225cb5bbd0d76c068c20a3bbe8835e43952562ff9ff0acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63864
the chainentry 63864
- sealed to the entry before
- 4ea1341dd11c6366430c328076204dcb7933bc665542f2a4c78aa1c5c93fb02d
- this leaf
- 532ff1dd566d9940c28fd5736d3be4575de0ac877f8f335f2ba5e287fc9bb19b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9jiRkNtAr7M7e1sE9qKJ7sTEepmEoTNfh0B0wA0ftNSSIsAJFlpivsJy4cfdfx776dB4RXeLQAUn3rx1FiVlBA==