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
- 0c49cc0af60d5b70808191eaad6865cf22bd7f967f194c546e69f58da5be327c
- request
- f7eb0786cc12fcae176a391036cc9d4ce01f5752dcf4a2b1e6e00a0af77ec605
- transaction
- 6f851319a887992b0ced86ff391798452bdd8ce5704c328c2f23251c45bbb313computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59233
the chainentry 59233
- sealed to the entry before
- 7d30c644b142b17ca141d8f08a51d0bcead8bbd719b2ddf56b7ace3b01c6bba1
- this leaf
- c2c43368455ec92124064d77e2efdd0cec8bb556c04567e45270a1d5edc55a52
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aTlX6nH9OkeCD5y4taDjHqs4Fr7pN9ndpr2TZzd6PHoQ2drM2UWWhdgeN54tscWi6nmeSdyhF0yHVRQwTS6zDg==