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
- fbc0bc0d7d156f49276bc16aba9872a03519da3be65997e8b5c1fbf8220c809f
- request
- aa77945a50a6eada873d23b0d154939076a350e5eda27f58f6bad8cb285d9824
- transaction
- dd3f73f82d9d40091c9d498e697b9169ef8647b550ef2d41d0d9afab911422abcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61786
the chainentry 61786
- sealed to the entry before
- 16e6add2eb4b6def16367e74f9474d2c2d801884beaecf79607364febeef1fc7
- this leaf
- 21cd0616dbf0c3c89f59798928c068695e12ac53e338ccd725601727f6b3a3f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CU0hcz0gvVJianvbkvgomujrmvc5POIgvrzwBz2t0I2sGydYqSBApDLDv1JrHWlznWzX8gf7HNC33DmNrXdzAA==