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
- b2782243bc634f4ce3aae40a59ce8131178dc91a872f90bcf3a58ee4bf25cc96
- request
- 4eaa6bfc8b73b7922af27bb62289165e5c74cef9fc6360052a48246977bec974
- transaction
- a78ff3ba9853210b72756ad3092d0e26b85e57a42d6e01af7c020e7a03f6c59ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9878
the chainentry 9878
- sealed to the entry before
- fafe38948477435e8785017ff61fc3c0ed0b740dfe76e86166513c3efd31ee6a
- this leaf
- 3fd697e8722de0537934e0950999e4d5610487b7019fab73e2b2b66fc080dbe1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NdCClXctBcWhRWGdG9yziMg/jTOONuvHIDP2163bQBnKXIfPSetAuwciLgcC/HhN+sZv5Fc0IQMVWT6BEKyRDg==