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
- f4d831e3769305a27eab886dc25548bd2203b9d3ddae43778cedfd7e62f20dbb
- request
- 2c54350e45ce444d17c0a38c87707d0ba177200e7f09d521761d7930ac6c318c
- transaction
- f9377f5df54d2671235d8fbc0e7287cb59c573ff843f286a21c1652fbee28b02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42014
the chainentry 42014
- sealed to the entry before
- 93897a012066288172684bda19f42cf659901689a7cd15726a64bc292c43548d
- this leaf
- aeaac55a5b12f701d480ce46ba3eb55b53c1503a6bd89ab6a4ac2806e6b7a2e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bvBtMQ8SrRxQSjffmj4LUuvcSQhvhK6hyL0R4jDMrD8rKYf8WkyY1utOOKsnisI/qJJmq3I8chIYa73sbMSVAA==