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
- a3962b47eba2ba84d69a2600d3497c866e0886336e86db51221af9a218dca69d
- request
- 7b9710f696a58fc353c31ac802691c6507c3a34bf9170140d23c7310a3939150
- transaction
- 95ab392c55ff960af669c54d8a02d82a3299e08194727bceccd0b513a50b3171computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62786
the chainentry 62786
- sealed to the entry before
- c5f2792d320828b045253be998cae4898d8572b20cbd9c0f24c057f7ef608210
- this leaf
- 2d33a0c98aeeebaf958d5d11085508fa9a4eafaf0c9dbb2d001bd4a9bd15e7ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VB1Sec/73jM/9gmw+SIuh8QLVE4mjHcQPD9mckejKiTgbraFaCZN7lq9Zgu2MzAKJ9mb++lY8AiCsDTDDPB5CQ==