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
- ff2288d11af9254b2b6f575ad993606524e3074092057521126064942a90ceb4
- request
- acb8c2f70248cc08872467c410a228c78b9ac049e842da7f030fa37c89da181e
- transaction
- 7feef2972f41e68ecf21c306b35b8e84290f6931e7db9b6f85b8299a829e0c61computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12022
the chainentry 12022
- sealed to the entry before
- 332409790175e2f262ca7a3b48b3e56d0314b614dfeddbe74c1c9c25f0ac9ed3
- this leaf
- 10056fbcec15e590d1c5be977f91af699fb4e75b3119431366a7a822efc1b989
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yWERjYIw8UZH77hgIWjAJkpi2Wuxp+LEbZBN3b6U0ypWW0VjYYEbme2IoAUX7YeMAy/hcXdqcw/TICtY44qeCw==