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
- 4016bfbdf91c34a062413ffea466f88f1fb55f4952490404950a1238af6c6e24
- request
- 7336c9766ebf3fb561ac15c4fbc71879da81b20c738d2f581f42a473e7b7f25e
- transaction
- a3f82d1e56adbd71d9be5fd44e89500c9391697c7fe2514de03b40875d86179bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75150
the chainentry 75150
- sealed to the entry before
- 829f8daf23c448c7d926d2104e0da791e9174aad1b8f7a9484d47a05f841b72d
- this leaf
- d59604039008e1307b25aa405380edcaca88542945af0d21577b0435ae4f87bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g7GWVMUbo3ihgxHYYd5tpaYMEBats3lJ+ifuCWbKcakJJ7ZyXJJxCvBkNN1LR+/32YLFVvMhReEt3nXoy9ttAg==