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
- 1c739ad1a9b2279fc650cc3748641d1756a816ccbc7202f4bc57579d41f1d05d
- request
- 4713ff3c1fb1569f39f4ed8765c2666676bacf0660a17661759fe552f71fd16c
- transaction
- 5147e7e42fa139a50cb5534a9d180d2f7d03c3c6885aa93e092ce9e8fc8830f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42500
the chainentry 42500
- sealed to the entry before
- becae28920340de4b7327c53d6393d527ed9875c9de27b57a66842ed91e80279
- this leaf
- 4bcd6c00dc8af3496ab1785d05847e4f6a383f666570e18b74487a829d9bd4f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JQuOnsuU3QOryD9u58DYhb9BUtMHRRQWApaBwdKk3IMc9uJTAHPMnNm/kxs03NdJJowY2t77ORMUctX77ks6BA==