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
- d41ae12fa4f3c5d710f3944aaa623485a10427f6a5ec988a78efc1f176f9ae7e
- request
- 908f04ffc4019c4d872126cb3e0c5aa7a8dd8a4f70279206e9d545b8639d92b0
- transaction
- a9110e942fa2ea616af4816ec23cd27d6731b8d7ea5c0191ff17130753fd49b2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1008
the chainentry 1008
- sealed to the entry before
- 5d0bb59d9f8f6f52209415c47d9fb449fed2a4c97fda86637deb46da35f7177b
- this leaf
- 9327bd30d0104b5711b9fee3ab2849f12c102f5c2e736a7552e64cb6ba5eca39
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- alvpAZvG9BIBKd4JNOvSXN/AvZOLtoXbcKeFhZ6T1qm/dMmm5CE0viq3XS9vP1ZAUPOkobbMy0b4pNotHomJBg==