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
- 43d8526693d1fda62444a3374521bd1e3471bab631fcdb5ed96f12d1f706384e
- request
- 48a0882b3d9825df7446feffa0a81583aaf23e0655999eed4a113bf52b7720a0
- transaction
- 61ba389fa2b5a08a3da672414fd82d892ef2f5a4a086f9682ff527ebf9ca4db4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25092
the chainentry 25092
- sealed to the entry before
- bc7e3df9000f07194db6ae8a4a19c63cadbc6d62cd6666a852ed8d76e2f41900
- this leaf
- 2369b98ee661f65507ff119ae17ef43dd9cd1ac73a64ef83d071bb67cc2784b8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NCRSeYrvaevGdrpqJN6E+IhF0Vk8wt79BaT7d9zbDmC7tKkZT1uCiUuUFaF+MUf4IDFge1gjA0C3beskEl8iAg==