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
- ac9e81c3d41ac5f387de6b4485dca81f5138922dc575ff880e1f06d7bb4be96b
- request
- 9d01f05460d984cb7cd4929bbad9f768c97e18a36f3693057b49e8c1a68bfd11
- transaction
- d010ccdffefa941cca9820991d8890512f5b1adac6dadd365a8502db7a94da21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72716
the chainentry 72716
- sealed to the entry before
- 441ab910482d3ee4741c0f2e1dafd40d1355679224de948071814c857345ad73
- this leaf
- d45a39f699a5aba36c093866f7f6d4497894f74863cc85e7d49e7b448823cd30
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EV6oU5hHpGZOi4qvfaEs26skgaM9Hy8kleoRq0c98Dj++tBDRSru8s/HVxdzz3skiDXreJZ5AIgZhLLTrg9aCA==