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
- 8c899c9e71d9a1eb3efa844f57b110d0ef60013c24f693739608c8d8919da74b
- request
- ddcd02a13aa0acaf377fc5098210c24e259c67cad8b35da85e42c604e5eb2fa1
- transaction
- a823e5e6f20bf59c0c446a514bb021b303aaba64ebc9ee8e808011d311041945computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59899
the chainentry 59899
- sealed to the entry before
- 59ca96e42135b49c585dd2fb3c1fe4233e8b8a6e346f0ace3d5d7732e332ff88
- this leaf
- 9d04a0e85d5a1b80547511b4183bdbc6bd35808eec4610ccf409a81adf74a001
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jz1no0nztG10NEVOSTtuuxaXUYPBA3mbblurmH85AdT43Q8lRyGliVb9F1aV3cWOQ8z4tEkKzK95aWbf0fXYAQ==