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
- a775b1ddf00335e43af89b6163add4e5726d29900d4397de43b81349f6290196
- request
- 78f2cd2e305f646456086acd1baf8c3bb323393f5bff3ca7c1b8deed4dff709d
- transaction
- f6157a70c8fbad469d90afe19a48323b82977fe6efb424aebd09857fc904f2bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74497
the chainentry 74497
- sealed to the entry before
- c3c93cca1ca523774cd132be436deed58702f631d21d2c8f1edea577b4b0d0cf
- this leaf
- 01171fd22f361cde666c91defbfab1cce41ce23d035de7b6262e5819e45a971f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TBsoiomdloXG9nzeBYAySXMPKZGNogLfK07M5PqxwVEmnDfh6ov6EodIRobWwF6Y6KidthXU2dUZ8kYyxkNPCg==