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
- e5011c3234cb91fa24b9876fd18fb4d89e46da4944c571e6d233e9b51bf09431
- request
- 338675c9ab7ea7bbffae6fe6078b9efcd8bd95bfb13219c7f34a1c14916d37f0
- transaction
- 5abd1878b1df48e30c26416901e4925cd54488830f3bf07f5ea2ad95d1470c58computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28500
the chainentry 28500
- sealed to the entry before
- 2d6b3b36e86611e4191b1eef21932bfe3efe8318876f93c28b2ec9421646b8e7
- this leaf
- 53571bcdde60d3793317be556afc9af71dd88511e08b4afa288f5c2baccc0c81
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jm3wAuAHAgbFw+Ce71mEBRS9u6MgDJPoV5ODnoLfMnDEaDcRT5UYBv5nYC1mxkPib0cHh6ye7zkFaDl9t3xWBA==