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
- 20aebb080573151f3cd76eb985d805bcb4c748f88f4fa04216e192b7456491ff
- request
- 6c7b41d77cd2e1a809adca75163ac7f1f6d7def6678b85b05059d42fbe7aafc6
- transaction
- 3664ed9b9d985ee345a64bd57f2e8f0163b1d9a71c4aaaec195db67119fbd7f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65598
the chainentry 65598
- sealed to the entry before
- 54930e0a3b51649662e69588d7b855627e369f8640ef6759e6db50776247b6aa
- this leaf
- e2e9a2960f019b9cba730789e3132b3b1f49043727f88b9977790efa3ad646dc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mYhG5y8Iueji4EYKFoDBcF+KHpAaVtgoINvdWkkKUcwuX7OsZuoiZ0Z44vkbT5/L5838Uz5sccv9++V26xCeBA==