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
- fd90c8e2e055a23fc4f63c543e762e788fb764041c1bcaad26020e23635c70a0
- request
- 3f2d67365c2b6a6a5608e0721ced7c24bcccea035afed9eeb3ce16a3ec44a71b
- transaction
- 19dfd52e7887117dd57e305fc8a13660ff0e733f335dab6e58f36c5374d0af06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55688
the chainentry 55688
- sealed to the entry before
- d9ba860aa7af0e1ee68e33a17c6d1130d72ea59b20c02a6d11ba4525cde03abf
- this leaf
- 60f225544954ba71166fb51c0cba515446bbd00ed1fd9382bab1bf9c9df3479b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ah87EmszQAZ0iQGMDAMNJiYsDpJvwIyK/8wEu8GhHBhacIPaTWq34XkVpw3T7lQx3f5u5SSSjymbgs9e2NYYAg==