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
- a920caf222740a9409b00a073010d38fbb9ae8ef66790792fa12172efa5fd9ac
- request
- 7a901839ecddbab0bbbfd39e45167990718a442c9fb17a6bb47dbb6394d8300f
- transaction
- fec4075d937605ca431c19422b0d090468c9c77c43c1792deab1bc92e26b81b7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43634
the chainentry 43634
- sealed to the entry before
- 6bd57da286f05c34ad6180ebcff1b44ba2d0fdceac5a422fe6f7dd339e4fe65c
- this leaf
- 37d8f077cec20881a31eb15dc3238485bc0cce47ba602e68ae96b60c85301595
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FKL/M9faQ8b8c+2JpWQrSmnQ6aOleMUrcUAjilF3vv6i55JarDHXVMmV5imtpBP9M3DM0qMnSJiLVbscc4CYCg==