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
- 69fddae60e384b84dee61f63e2f85fb19a9814f737b16706c888d650e8a1cf1d
- request
- 3fb5ee5fcc46cb27c9fc4392894efe57789f0fe30a5763c7e168301c8a4d1d04
- transaction
- 3522b27d58a3e2f5d0ca76338029adb7394902b779d85aa7b5c67080bced833dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64668
the chainentry 64668
- sealed to the entry before
- 6f2fd980eca95f15af637def56b256db72f105b22154f865c171f75131125acb
- this leaf
- 793391a007e49ab81208cc13b6c1e2e73b309f8c6ff1cc0383ec1c378bc234c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KnmwPXPmfEBknjOkKn9iFhwjuOlXcIq+G0Q0dBTEE0QqVJFiBz3srpsGxXj+vDfRK7CzzhduR+LJ9xDNZLPCDA==