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
- a74ebcbf7ec016bdbf4247951140905c8026cf878ea450ec3b4a7559f57f427f
- request
- 55742bf510a3177730a71f9e5f3984ecc482789cf25695b153d530c838770840
- transaction
- e0eb0927795beaba25a855ad19da41f2ca5dfe0697b2b490c4bbce43352afd96computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9430
the chainentry 9430
- sealed to the entry before
- 2a520a62aa18d3505c0c1b9698cb58647111669a4e618a88ab950fb8e0d4fac2
- this leaf
- 5e16e3e66ccde976b977d0c6b3ec7ad72043193652f213ccf24625c99f177f4c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YFmIsb8gqUva/ooBrXSyRgSMxqvRRzp6tZ1qE8rPJCMXtG/HbypOLKU6tV19oPijCQ/i9QETXYoqQEPQysT2BQ==