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
- f9b4d996bdcb60af0ca6e7ebf1a102ea8d9c9f48c465fb6dd67d83b871d8eeef
- request
- 6e04bef9154bf2973343a52976dbf3666ad807344e30dfcbfb9d7d12cda66dec
- transaction
- 905ae31e52000bf1be8bcc887976c43789d2c391f0488950f997c4761b50982bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68961
the chainentry 68961
- sealed to the entry before
- f928ef64b96d6b53f7e2705670a0fbfb3a134d52d07fb99ef9f7abaef3152d67
- this leaf
- 27103c1a1a47c02de66f08c144c9391af922a329c0e2e19794323bd4f564df0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c86jAZZ9u7UBxUCcSZxN5NldfBlrCXBI4DYbWdxJiJgPMUyGZNMk3nL7GnpfJxxp9xtiUSSA43PayLXkInS3Aw==