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
- 7fc582b530a1685409852293868ec0dcfdcf6c8641a71650d4918153aacd569e
- request
- 846dbccce5cedac75cca62b0500947122399bdd4de55eff5bb31513404297d45
- transaction
- ca5cefde2dde8033b276320e848dd2b5a51818464d8ef3ba1fccddf9e72882f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59381
the chainentry 59381
- sealed to the entry before
- 29f9cc9dfb9020435ca8616b5569c37362f93819afcb35573fe134d9b4c16cbf
- this leaf
- 8c3f2a5d0361df0b5a5a05e2920fd31b9b6d1112fe506c27db75f271db451a76
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LJwaAnEFuc9mh8qFJjc8MV+44j0wgO63IxdQTsudPK1vTdLA4EwDWVHknmYcBTmNRlBsKe/UyP5C6Lqq5g+IDw==