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
- 0aa0ffa3c3c2026e505493d68f82da5465c0c1070377e1011fac1549d70792d9
- request
- f213d7b269a70b569910527f74ddc3769c304480100f1d6f4fa91687b10bd2aa
- transaction
- 40b639b14dcc951a2cb39aaf65fc5f875ad1c25f9aba9f9c357460dda47c6b5ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68709
the chainentry 68709
- sealed to the entry before
- 2cdefa2557cb77fc68b5cd4f056a653dcf7a2f5af12a27d22e3c4ff2b5d9c49f
- this leaf
- 256980be540d5d37300999cd18a97f01759006da3c1e3b36d147def415c28ecf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AKJu+eLb/wVLw2dBSE39mPubzUP1HfPggWtN4X1Mnjcr4e3lIOcBHEkionSGoeeFiw+urF9pbXr+BkA7fGhfBw==