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
- 52a4253aa0fb02fedbb1511b12f8baa5713d672f8b82bb800834357db37481fe
- request
- cf8a89ba79bb87c560ede431f5374893b948b8efac7a167f6c0fb0920e8982cf
- transaction
- f069c77bb80acea6fc559c287839c4fb7fca3fbd636122e0abe484ff52c5e065computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45706
the chainentry 45706
- sealed to the entry before
- 431a933b39599b0e28021d724472c9b29d1143cb86204c541a9de930ba682c0f
- this leaf
- 8ef0445a69d7a12277a90b874e176e0f041e22713f72501e3ff23efa57071c5e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0+19cxdoquulFs7YMmvgtSqBBAcKUfsf7Qx+gG6QWdzbtBGUYtXpp4DTWcA+kCZfloai9VzEe0Aa0lw0jva1CA==