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
- f8804b74d07cad70ac70b434005b48482843ca43eb6021842688211b89318797
- request
- 8886fa3ca50a616d23ea3d840c88b8e6430b42148fa50e8110fcc7c1aa1db7f0
- transaction
- 3f7b6869f75ded1c7e032879e3bf7a8816146cb4c4d75d4c74d5a249dc9cc49ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9055
the chainentry 9055
- sealed to the entry before
- aa66ed6b0faa6918b5de2c88dfab58bd1fbf0f5a3bebc3e31d26ba4fb971f01c
- this leaf
- 2e0fce12cada1f3c18e0326fada3d8fca415422578e0acf95e0e9bd1a25a84d4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1jPUXfcV4D0Uo2OjxYxpC68V2HGgQYIfDldxwWa5o1AVtmbSU5RxpSLY4c33uxCZpUiGAd/CmGUwXsje2HkqCA==