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
- 7e5e6ac985defb6864916a070c14dc0b68c6ea2593268f82d679ded2fb3c5b2f
- request
- 3da60f7b2e2da55cbcd614c9b03bd6136ed5f73f81d83194c5164271bb009ba7
- transaction
- 5c2bc057ecb1892c7455a854ab09217878216ef7aca300860a59262202bda17bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56277
the chainentry 56277
- sealed to the entry before
- 33f96d5727b032dcd5a2952843db3eca4d62146a3b4e8f143f76f37e9f5ae281
- this leaf
- c36503c2b1497d243233e548d6c0ea26ab2d3f2540768249033f66e961bcacba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3+0Bs+P7J7m4At5zYowTT7+NWK9G8Fjo1gQBx0zR36jKiBoaa6wsVvLEV3hbZkmnTi+yMTRKqGYljafgSOb0DQ==