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
- d0d04432546cd5e7792c506bc7c4358103951fbfd3edf9253701f41ba2d700d7
- request
- 46d338a6e81eeff2410584b78af4283815ddfc79cc8c1b9327facd2f66c1d9a1
- transaction
- c55f89e6512a4fd3dc65d127050d9998a34a5541e3b581e89f3e70f85d1ba71dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9403
the chainentry 9403
- sealed to the entry before
- 218b891d1fe1035c9cef29a7178da903cb6a99d3e34b92997a08cbdf8bdd6134
- this leaf
- 6f726231d1c782a1c9f0d275dfc48cb38b024af44305e113572373c6d79e2d7c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mwPjbZW2OnlueTo7VmDI2ChyHJis/KsnT/RHSd5ekYgD0FjZwWGXB6UL5t5kOPtP3yXz9QgLLkUcCfn+PqhqCA==