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
- def5e5724b885d13858c84bcb8999da7e456ea196c1e01152cb8462709400ba6
- request
- e2788686662d42b9eafe54b6c51a8556af8ae7b02d28716318d02cac1d53a99c
- transaction
- 35de6664ecf403019f6267a11bebf4bec037c6ae1890e17624522e1a9fc1af6bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26333
the chainentry 26333
- sealed to the entry before
- 658249d23cec640864b5f499974e1dd868c8fa20514225a4e093f8a2291f605f
- this leaf
- 711a5f5c829f1499e318cb397af38c4d6b2e3ef610ba851d35d8928e716dcb4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OOewUyeSKjf0+TE3mWXF0VUiCiMnT+PI4S4Ta76XQsTm4U/qfJ56DUkhzYlG2GAGKrJ72MYX3dVQ+8UilnfuDA==