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
- 9cd98a8fc44d01521fca1fce4f31123f9fcfe72f1a844ccb41d442eef694cfe2
- request
- 987c2696e86ac3121fae4893cba42f5d89fc19750f2eefe2fd1ff9babe62f4a8
- transaction
- 87b0bc11b84e6cb9feece81b5e6db67c8f830ed01370f32c723c6b3fac54c769computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29051
the chainentry 29051
- sealed to the entry before
- 521fc030dddd1d0acf030254ba7964da7ccf9c17818e6e2f8cf4acc99cdfac61
- this leaf
- 98588e3175a3ac81cf027d840b59ef39d3a0ee679dd8428d2baadce9cf86fb61
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KJIFrl4h9+VG4l3swjxRYuCdLM67LLweuHHNOvCANjrvQp04d80rJgUK97RZvsAiupqxb3+Rn4rbmEjhj0qMCw==