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
- 70f3875f38637a1ee3a6b993aa53e4cf706711adbef5d8de12a485c5cf093dd2
- request
- 431ed4a6253fadf465e44bbb036cb91bc6da0899a10af6d0b6da619ab442c7d3
- transaction
- 68976a375ad0382ead96201eb2bc7ccc9d15fff570e9f203040b1ae700050808computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53390
the chainentry 53390
- sealed to the entry before
- 3c611be0dc0668c609a9da8c57079576d0f9b445fd47cd2beeeaa51f526b4169
- this leaf
- fd8f88f3c376100ec732d08bd213ca5c49f465230dd7be26d463489fe95bab36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9xxLSBd+7VQhc5kq5fXNf5p1XuiRUHkbpkXvhWZeIRT6H9YRT621QUBhETosSE9d32H47Tbp/1YBRxgaXXUrCg==