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
- 44f8a4f34d6113cdad74ef33317d69da18a55846ac5895933bef3baec5114c63
- request
- fc20dc3de5bd2204b434269da7138e8d7e96f148340bf037fd3532a4d87157e1
- transaction
- 50cca9ec86332407a1874ed35eaf1218dcc6286302ba6ffcce598a854217aee8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40808
the chainentry 40808
- sealed to the entry before
- 08b8fc093d91c3e41347de5e83051a789178b8a0d06b25e0f58be8070f36a1fd
- this leaf
- caac652168edae66289de05d6228c964d7c76620ddba696854d9ee480dc35183
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a84ybbQVrLhGTUxM5tAt8E4FTJYjrKo0qQS5OrBr0Cbxg5EaiH5EKA9qq/Pu/MOBJofP8XLKJa3vDcWA8105DA==