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
- 5ccecd9338c2b61fed78a83ac228c8802946b4ee78ffc59a5266152d8cbd5af1
- request
- 7c608e3cff1e62347eec97e13d86cdfc2e27d953af882db0ce02f896d0bafdcf
- transaction
- 70acee92b165e816f6028fd7b043bcf55a8fe77f41d1f437c0a313c6d66d22fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68433
the chainentry 68433
- sealed to the entry before
- 3868f3b811a9b6fff895f07d0e9c8139fea41f74a4108e7bba4af24cbd7901af
- this leaf
- e04ee4ee5844033bd1b85bda0b53712c08fd195796a06bc1385aa58c4e17ecd6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ls4F7Dkl4EHSrQXFt+WFCBSKdO/8iuxcTeINswEeSvV0ozKNAiQMoBXipBtf2gO/vRryABzWuH5kpWvlvkR8CA==