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
- 88918ad7054a001bcf6ec28d1da1b02fd7e71f70b826c07a0ae15e1f81e5e276
- request
- 59b21937c0edab24e8f60b3dd18fc4164815157b812d97e369b05a40ec3b4269
- transaction
- d968224800f97a68849e7360f7daa919ad35e7cf3273af0d34c7b805dfdaf29dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21990
the chainentry 21990
- sealed to the entry before
- d72582b0707575ed1ff3a16a06f104c598d42bce0068e0db0b284a11cec5a3b0
- this leaf
- 0e30922d9023e51fe18e350d5392cd944e59e77dc124b098abc56f71ded34409
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3RbspQFw1cf2uaffKesPvKtMk7bMZeTmPpQUTFqnMDVxz2gceC47vznLvYakG/eFLXyRoc2w7t6bYs22NGnPAw==