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
- 3a25929a6598be684fae522f8df62d18c8f87965f80829557df16efa998086ac
- request
- 7b67ddb3a528256449b34b84f06fe7593d46d97ef3e463975b0cfc84f5c69192
- transaction
- d80a191866ffad553dbcde9f727b50882db38a7d4ba01444e5dd61c9e1941c91computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46880
the chainentry 46880
- sealed to the entry before
- db84dc7badcbd711e67f4511c19e622eb8ff7d4051c54e91ff653bf616514529
- this leaf
- a1404218a79e9d7e6ff9a666f4d009f51b5aa4f19f9a9b87e1ac1ee02a871268
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Qj+qGUWqIyox1rC4Tr3YVToSmYH6cQ0+7uPDSnsFBGTJkOXCw2B8ANfrTeWiQxDyhbq81HLjmz1jv0PvgL8gAA==