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
- 27345c5951fb7092a45bba49fa44c7cc2a0073a8d6cff61b3a85a64dfb36436d
- request
- cd6188db4bd5212bf156a28d4dc14b7987efa52c4cc6178e24dab78fdefd0240
- transaction
- be0bc617e7f7547b532197179741f650fa8aa290fe35cedd96f88030354dbf06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12328
the chainentry 12328
- sealed to the entry before
- 4ce47a8bee799058debc20e375624745ceec8ed1f259c8e8e0a283aeb4877a06
- this leaf
- bcb1a9e16edc9516d46d45c7d9bbc9dc932f84d846f3658c2b5b1a599e83618a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RCjGT9YJMg3mJKX2H04SeTc9aWnb0VCVKPf09lPIZSpIUg7/XWCt5raRye4DGpebiBykl1cWugl4+uAzjblIAw==