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
- 0f4c8a708bedfe74d0b65aa341117e42c835c79a1a9dfbcbfc5761abd54cf940
- request
- 8bfa09f7fe8260e47a1c85ea02c31ca7e0fb2f7567265d04bea812a43fc5d33b
- transaction
- 6a4e4f88b1caba4f12f826ec746f18eb6aa7609a3459a1e5889e92289baecac1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27718
the chainentry 27718
- sealed to the entry before
- 8cecf57e4be90a1a1d9b4fed79065985c98a8ec6ea828fe2fdf4d0c7b74c5d2e
- this leaf
- 5a52a5244cc18e681791140591cab690d660eeaef2f4a00dc80b2cd3c46ad498
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /O7M+iovY9u7mrM+OwinbvLwlnFOtoVWLB2tGcU/jFBfrqFDf6NRQ+8OilKXStrZKL9ywh5A7YFijetmXpnwDg==