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
- 270181eb409e66d921e28b699e60bef7a3c6e8fca2769b6c31263410f52fbf3c
- request
- 6270da9de5c8bd9243636c102c91e8405bc54e9f7a3e07e6fe3dd16e6e62937b
- transaction
- 3b9e835676c5c537e289f924ec6013ec2074b671005c57044fb89874c98fc351computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1058
the chainentry 1058
- sealed to the entry before
- 674b0a845d223714cec138a8ea06dc0806b601257560bdbfcf5f7dbf7a45cfc2
- this leaf
- b159d2513a108ee1b9618bb4ec675efb33c7e5386083716f48adf6a61f3a8f96
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dxjxc6LP2MPCcxzRPIIk7KiF+diev//Yslj9gsoZSDycOdPH+jGS/wmvFgYz9FFb4xLFuKJ1tZg75I3QyPG1Cw==