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
- 4a1339e32d23d5055ac229a8a2f5ab65741de007cadc98fbf198830eb71fe389
- request
- 2fe9b8259f3c4966e971030b310255927fc044f274fad0a812c2a2b8c5874907
- transaction
- 5852b8712f53a5cf8c8111c776af3dbc97ec1f46a3cc91e67d601741ed7f19c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40525
the chainentry 40525
- sealed to the entry before
- eb61cd3632306332e51eabae38c7a42d80d919ceb9a2a1893ae9c98144ee54d9
- this leaf
- 02d9da1799ebfc1758546a3b6a80a91a0efa6d1ec26cd3a11a1b496efd418c2a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5t15qZ61NIQR/wJohktJMSPP6oQ0uKMTEMd4GkbH0Kg/LRFOPnyDfjeyfHS+csueiWJ2iCWAKIp87XXhfbSZAQ==