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
- 2563ba447a2de119ff63585bf07fad9f351e23be60c8769ff461d3615a621b36
- request
- 598e5cb8cf1272957e974dcf18aeb644e832830c6326a89a64ffb29b7ac3ca4e
- transaction
- 0d948f523468e08a26a2ee3839351593069a76758538679b67baccc8bb81e193computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 556
the chainentry 556
- sealed to the entry before
- ef32611db7f29e4994dcd5102ddc9282d0c6687f6fa508f9f52b48428c1e6c07
- this leaf
- 2c6f4c738dc265a7028ff68fa6820bdff3922cd36f3cb680ff184e92d5041914
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /63rKonPvRBb3JCHggBvPbVBUKHFHx19TuM891jSdf1hHyb6+NIBEpU0cU0OgZO0SH/lGTv/5k9rKaGr+up2Dg==