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
- 042662072b5e1d5b3485902551b20dc2bbf3cbec7ba0dd5b2c81fed275f73d02
- request
- 097f21a7da0abaef8da1db6172bbee54472b954cba8af5ff076df713cd59b4f0
- transaction
- 41d0c921ecce9e2a903af8b648e30eb8d2dcef2a2f47ba134d23d520d62e9e1ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2460
the chainentry 2460
- sealed to the entry before
- e3789693340c53a622aeef8f4a5e5ae4ac3ba67b40063d28d4be14212bcfdc81
- this leaf
- a82b19197e03db4390e80502da5c1633a5291be20cab61fdd421e646ef06f30d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +fuVrsyvHlcRO7AqhA48CLfXEoGNaNshxuMLU4jW0VxeI5mz72PklBgQ9/ykP+Qxpw9SK7/TIMPROk4GsxfECw==