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
- f47d982fb18c01d2cc4fe111769906080384fb51201895d6514ed01d2f2429cd
- request
- 82db4280cc00a7007e2d24eff168a90a0575ae70f2ff88aba1ee210936508173
- transaction
- 045e871ee4cbd4c73f0ccf48b774f2f52608f1d968a32c196ab1301ef556b04bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5817
the chainentry 5817
- sealed to the entry before
- d91b8b6df88b924b3b8439c35ad6f81ba4a01e73b5deed392ace6322e93bb5d9
- this leaf
- d7b9aa2ec1d452d70bedd52b7eb3acc4e055adfda226687d9e97ae6c32ee1c24
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5eIZTPLBC5EH9APi39Bt87L7QvE5b0LhA1xPvROrjFfQGSD5g23BRzI/l87G7PSIN3vcIlvWhRL6HglsKzasBw==