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
- 2eed44ce9d71c6f1e3cae60519e20de2dfe3bccb703562f4d5ca5c927f5fe22b
- request
- 29a361af98c8472e059d8bbb36a4ce31d80c658767e3caf6a843563d20636972
- transaction
- 555cbee6707a1b9d4b4854447ee66f80f76e044d963ec2cfad202e058df79db1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20311
the chainentry 20311
- sealed to the entry before
- 5a841150c84b7906e43139497e8190a5aff1302c1d0b7c21da988245f8c17b67
- this leaf
- 89a3c787ea5d3d0c56fda77692d678918a671f80f4ac4da9ed254857702c2e47
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8UShuw7Wcq1XjvxtYP23TGKZ6v76Ns/Ba1HhNay5IP/w/w4AdhVFIU+qypfykf6IKN+A0N8bS7G0F+2cBiFSBw==