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
- 672bfa4eb001009ddb51d37c3e95440a772379f12290841f180473dd955196d1
- request
- f3faf35a51f274cbb2a143a15bfcb4a6f1010d354703889e12be5815e69ff36b
- transaction
- 4316ed857f51e1ec568bcec7d070d6dbbda2b696b98b2a9ea4e02539b1460c0dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22175
the chainentry 22175
- sealed to the entry before
- c551883f34a9278b6d108535170076258662a15003e57f4c2803597c3d99672a
- this leaf
- 2f89456f268a363df014b64c9ac80c082e8caba93d0cde921be5bc35183c3580
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OTpVMxYEuFDBP77CRpdH5ShwEtQOWgXF6HaiAhfDCwbgYnppxxjq9VYwSy5Klmbp7CdoHJr6S/JZgQLdjZriBw==