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
- ba91a2604b457a0113ded3a2dfdd8772c3bd9ef8b810a6d21211a2b4b2e1defc
- request
- ebc924d1d1b8bff8c98f5ef4260adced782cf5ed938c6cdf787bc436b22fcd43
- transaction
- 3742ac334688d65bd22556e7de91ee45c02b50f0d0ef616c4f3a9e864cc5dab1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49530
the chainentry 49530
- sealed to the entry before
- f68b5590dec5ba1633590316b9761c474e3000c1f05457490f6731f65261cfd1
- this leaf
- 5c6c17654c82e5e3a18c96956d526704577b72165a27418064d049f3045df60f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lUbRf0NFB3kyYL9tyvnD43SulpKb+Oa97mxEjpvL7Kvh78k+k4nrEOrNhsynVQxOs9B6CiR7Hh+bturSYAj/CA==