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
- 78afaf29e8daf3ef704793d372b8057efe523be068267c0051fd1b37410de940
- request
- 302b1a20d9d8c3f2a334fb724513eefcb8ef28820cae57f48a9354a138df6766
- transaction
- 9217ffb5340b3babcc433a0613ed214bd5768b0459049359b8fe97afcb6c9cdacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21456
the chainentry 21456
- sealed to the entry before
- 8960e64397c8a5a5f9ee8100f1f3e469e3a56cd1b4583392b666649f9cf759a2
- this leaf
- 16ab85bb1cd8d12162b30ebe826b00cfe4fb7acdf3bf77d5c8110ac7bfe1b48e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ISW3Jy5g8/uIeqoD7fbDg695usrxuRpRWxrx93VIdRXUqgt68EithBd6JFn/8NuzegKvMmxjsNriEy+pji3TBg==