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
- 75ba010823789b5a58c54960221da31e471b66bdef44c211ca020821fe83bd04
- request
- 12afbbac23bda94b8486310aceac77621385d93649383dae9da8272f2a26fd7e
- transaction
- 67a39fdb76fc8633bdd9646a23d78b3245a952b091953536521b988ee243e3a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38290
the chainentry 38290
- sealed to the entry before
- c0644894e2fa8115447d6c4d6fceb442bde8d0cf80bd7f644752a655f2fad714
- this leaf
- a1df29e196ca4fa1a2a7009c97d53ce8fcf47962c32c4956e0a47e117bc95797
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HLgrG0xG10arBsnjrsbomARI5ftS1bh4MQ+2Q9emVOHc7Lc+d7jwJB1WF+pxm1vx0zzSidPoPpvWmh/YbIo7Bg==