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
- 1b3cfce241765f1abc8a4afa78502304757428e1647208575d502e19f45a4f19
- request
- 92911d7815939061952ee5c40bdf2dec9fa7e2d47997901cddc750c5d8759b14
- transaction
- 507db57d8a8903c15e8d7f7084554465f0731881651ca0dc92b45e946ab48b6ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35968
the chainentry 35968
- sealed to the entry before
- 476fa4e29f57d024e9b6ce474a309862e7a86c93f791e8013f9292be56d3277f
- this leaf
- bb82d0295590733729734835b0194b142392534274cf75a60ef3a700088be1e0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JGha69njIPPsIBYDX31VOeQOv9yxBvo4GX+Dt1mfOBN3JWUXVjxLt9m5pdDDzV78bD74tWchRdkmC/RibdP6Cw==