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
- add1c3071fbb694f5684e43ee4def1e58cd42917c333149039cc2774880a7818
- request
- bcce81cd6123dd4b81cf87fcc310c81ab4907cdbfcd993b2fb8ed6178cad12e5
- transaction
- 535ecf036ff25cd94bd46cc2dceb511e5b2d797b5e03c9fb73b202eafe6fba47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21638
the chainentry 21638
- sealed to the entry before
- 6f3360dd5d58fbdc873db9f0bd2c8b6d9d6df90bc1737e0705a4f1c158e0b462
- this leaf
- 924672bc7c14c62c804b0b58683cc1170cd8272fc021e424543448fb4164a21a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pzDaMTqq1WIA5sIotvvUgO5jx4bpetNKVn6G5O9OGS22ftUHS9iYZV90vkzziExgHA+P0PHqGUPwDv2rlX+7Dg==