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
- d579c5b72d3661d86d141b9a1bf4290daf60aee797c55d391c916c4b49f21112
- request
- 6af56ca79431b2e32099b4bf5433dfcbf55d16ab43cc5a4a509e757216d7ccaf
- transaction
- 99194a895660e5b4be32e841ed696a5263f111b8d7cbae5c88aaf9cd7bca26b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60619
the chainentry 60619
- sealed to the entry before
- 3006649ea49996018cd37d0bdcecc622efeb939d62318fdd4737113ac9aca9e8
- this leaf
- 28e0ac5e1e261b4f8d988243e05b641f60c70655c3b5600613253c90216fb152
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WZ+bQRiJgoJT22l9Dft61PTl2jDRoLmTfAzETlSlHM9if3ffxbjlwDJkGc5z5slDz9gyQ0KBAklWMRAEy01RCQ==