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
- cbf04765ed283fc0651d1e05b590fac1ffc07cdd3a8f1ef87d9489fcb566733b
- request
- aa4f34d333d937c6ca79a4e38727ad3d638a2ac49864fdd71296c8791989d81b
- transaction
- 151709055c7e0f4ac02fd94298f0368792bdfc3fd7c905f80a7e86166756e3c8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67274
the chainentry 67274
- sealed to the entry before
- 3178b98185d3e5134cf8daa558bcc5a255f056bd90b76d09baf979e4106e2946
- this leaf
- 432aa2bbcf5e91fc27c10533d3641665ea53d4a8b21423824e62e8062ea44fbd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jbru2WnxJT+QZKGeSn0dNVHzwunhdUvBduHc6Cj3poGNObcWZsXGZVVtBauyKi5j7KpJXS3Yr3nz41+NkP5XBw==