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
- f57f2966aef98ff9558afe04530b6065cf237c953fa328800e2065aa0dde0eff
- request
- ec1f7c8dfe24783eaf0f005205e87b40b70adf59ab192ccc1abaaeed42750938
- transaction
- 667f52e1b29ec52cf5c04eb081270467dd306624fc906a281f8446b023d35b13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4131
the chainentry 4131
- sealed to the entry before
- eb9df1579a48893149eedc3063c603b3a68c3905491c5df0d2fd0d926c986296
- this leaf
- 95069a38b536aa745e5e283c93590b321e7093d7cadc1a7f10af88f6ebdcb3f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xu0pbEuKgFk2fsBJbo3gNqO9wEp39uo7xaoE5dAjn/k2wXwwAzaDU2NRdKlhyLb4cqj0/eAW+8Wxzsk6CYp9DA==