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
- 20baa66e60ede3783161282d10ce2e9c574dbea6efc29367076af491d44a1109
- request
- 8b47cce5cd43d31a303a18bb58d50db535e8b4accfb404f511a27f4163c99a0e
- transaction
- d0680594442a459e77fd0ea04c015295e2ea541e55dfc8969e8d01c1eeee5137computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61497
the chainentry 61497
- sealed to the entry before
- 56d1e432170cb7664ccfb1a485f329ef12ebcdd9236f9642333a9967de76bb11
- this leaf
- 1d24272c7f872bfebc3b50fde94ce90a21d3a50880bac6f1d9ad8d11a67d8a62
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3+yHJd0tIJRxDDmeYSMOS+jQmCJNlWW1RMkkxUtSLyHYTQq+Ee61cOPrbLIV6lofkQAnlxab+JoIqcrcBbYzAg==