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
- 1f8b3b034defb080aae55d59f28ddf867ba19d70612e10b12358d306edeea9d5
- request
- 80d61094a8695e46f86dae3fd1c9998b20fbdee0a05ef72b81a3599becbba953
- transaction
- 0fe1d24eee2150e17930c1bc7e37eee550c8ee486fc31556e6ab8ef6882cbf79computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59416
the chainentry 59416
- sealed to the entry before
- 0dffc128708ea36b899aa2df64671cf647237d907880f395ced4ef4e2fc38063
- this leaf
- fda7104c41632613b87ceb884f519ebc1f8a4bfd0f2797aac6603004b1a6cecd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ETIPAj/khoopGrvXhnlhXGZsYdefjFoU0dK3okS+tlsWxkagwxGO7T7HPxcoJNWqX9a/JPHzkiJ6J1lsRST/DA==