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
- 52bdff67a77f64ea514fa2a2c642a16f92d891462145520d4bc72ab2e996451a
- request
- 8a234cc3aa00769ea92dd1ec9c7abc44be645d8e7f3dbb1a5d2c0b7044115cb3
- transaction
- e9388b282c45d874ece184118031406142718527a9ad2e87225d7d9c46db6e2acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9648
the chainentry 9648
- sealed to the entry before
- cbf513bdfd5c79b58c97169b2e7f3ec7f0ff0b43502e2b6ea7aaa27112782a43
- this leaf
- 525743465998744d0bef58f017d31e2025e81cd0e181c9b1e01622432a43be7a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bKYpTWuy27GupNZBk3TH2c/STy3fno9SnGenJeFnu9Sc/2LbNGsvngTpwRdsrk9CtTNZbQSHhGaoFjrgzhTuBA==