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
- 54e7431171b76899d6b5a9005387f73e3319cde26f789d94b6a4d9d1dd389f5f
- request
- 1fc84e3eaaf5949955fe57aa766b1d9f369e7d9bc710dcf47692f7340bf58cb7
- transaction
- e79605e7bce1816df32a8ad45955815c2dbeb24b9428c0eae8da1562eb9d59d1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60944
the chainentry 60944
- sealed to the entry before
- 0d4a848e7955b7949671a4b6e111839e3c366b325c8e82acc071c650c7209a87
- this leaf
- 08e63fbe0c89acccf5b4166de3c28c6a53788bce224b63fdb4aa06275d37a277
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VlGsbaXeV99QtD9bqv2XstZBemWIrHzBF3ctE5ZmhVo9RoX9zo0uqiOK4uFJxbt4FJtZBFc5cjEgPnZXgAbJAg==