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
- 82b7b5460e6367f924bf7d313ff4660cdba78dcc77ef5569bca3cebdab8bef29
- request
- 87f2e1cc7ca287fe1ccaa74027e4627f4d6c43d57e0f384780c94b96cba95a6c
- transaction
- 386c01c27210ceaca42dcb3e94c015dcc28ed0f883cfafa0f2cc888fcb7182dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27809
the chainentry 27809
- sealed to the entry before
- 77656509aceb6cdcb66f16d099a8821e193ce72137d344658b1ac81d27db200d
- this leaf
- 578a75f8e7f131678042381b4b91e9b4c49ec7ef3dfcade2986b5702b3b56442
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wa/4YY3P0ewDV86m1nJv+y8v6kayAMqlZ0u9JBErLLL+JxdfIKwo315CmkdOek6JFY1AwHttAQTipWikXgQbBA==