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
- f4a3c1e0819c6897e552240496b0b33ad7ee568acc717df10cba0a53ea3b4891
- request
- 1ec3d5ac99d37dbbb69d9a88d4f4b3a70f0a7b677dacb7bf554242c25d437421
- transaction
- f7f0c6a698688e33057f8652ee5d0b8c3f65a2fe0d477f63b8b63ec7d7848fcecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68153
the chainentry 68153
- sealed to the entry before
- f20769cb067503446674ac8f4da09eef6a04cac0de746ac962108cef48d15759
- this leaf
- 455c91c10464d6fd53b84f3f1ec828d1584af38b50d82cef33a7f69b64506a1a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EAb30wMK5HkwBYi1MNXexklLd3rGbhgngUquwyRlGjF20YeqLkySjOUBEA4HDdLUAjrrMBrIYs+FudP0SZTyCw==