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
- e86c42f156701302b706593715a1275b3779a8afdca0500445dd0da3c5fc7d55
- request
- 808d9ffcdc702e88316b78c2e3088ef9227cf744c188f7e80eb6645a60ee385a
- transaction
- 0ccd9a38a68ae66a74061b387fda8334bd63d021f7edbef9ae4b9b93eca988f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39207
the chainentry 39207
- sealed to the entry before
- 85c1cc04f9e6cfb0f22a847348bd1eca3904b4bcca9bbac5d8fa8934fa6a346c
- this leaf
- 8266bd6a9c30ab046ff5c7e3d4a24238afbf5858d7dfcfdac4c1c9658d5e5dd5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7woS5xJYnULkbX2vwZg9rkxD1aiFXd3njs/H8+0KcA9fN4p7+1RTwftF8t2AeLtkeYWlZDgl2LEpMCf84G4TDA==