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
- 1cde6654aaf684ccd9f7d9638d357e710930719ba400b0e5696ea20587d2d3b2
- request
- 15e7de4c4f231eea4734dde80f0c952951a00521e77f025f7f69242cca642759
- transaction
- 342bc8040305597483df9b77e72bb47ef91f722614b642abb37d5fbc69084dbccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32052
the chainentry 32052
- sealed to the entry before
- 2e2da015244afea739154f2058df28fed845f0751ba9deda4bfb55b240d05244
- this leaf
- 84e233d70a356c90c56e1056fa3d4a8e2ab93627261e0e5a208b1159b817e815
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1/4iqdJDiuVxwly3e4atvxpIPluWWdM7FD6xlPey2Hmnv+xoZtGP140OqEFBJ73fHvUUFpAElwDKRTlS3uxFCw==