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
- 19b85bf9e19ffafe2fadb45981b434316a6c0ed7fbf74fc9eef414ff56bda3f3
- request
- 995b576628dffe5ee4399de382485f926b7b46acea65792264226c00cd223864
- transaction
- 6da53495de60f726dc7716490e12e444709575b02933a76b954a559e55ddbe6fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26131
the chainentry 26131
- sealed to the entry before
- be51690cb206d5985d67d9117fda7648c25b3982dc35214b2608f981c6a2d2b0
- this leaf
- 5bfa91e3f9dd3af347cf5534ede83120073cb9158fb5151b11c7390082c19cb9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7xDde514wVHivluGvYItZmpdFeENEXEc6a15oPMs+xb1UnnofAnsZ9dG4UcrDku4X4DCHgq1uttJzugGZVrSCA==