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
- eb8710b90fb807d06ab6c9a052339eafb159bd593a006b349d2b482b22e773c7
- request
- 43a2c3d5ab2233e49b673e271351ff92508115aa3b0db9684ffe6f6fcb1bf8cb
- transaction
- dcf107a5265c7f82e48d9f8db6af59964ff8bf598ebf00f8176fbba283973f06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53794
the chainentry 53794
- sealed to the entry before
- 692ec6e6de510a246ff3fcd5ba07b536fdc9279aa7dab0ad7f2a4001c5b8518f
- this leaf
- 805cc6f25248f4d2d705d4d5eefdb515ceddc2659ea098664bcd03b97b2db1c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- om1MBzec33W0i6RsAOBkcCyMP560NOA0UK+dyVZT233xIaH+OkTs+rwg+zPCNnxvNXYoTSmAHl19nia+RD+KCQ==