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
- 136a946af301c36eb0ffa0e81a37a214ec99e5c269a7927eddf661b58806f8d7
- request
- 4953b6987de06986bdb1e9e80594acf7d01b0d0859417481b30409e03e2f2c5d
- transaction
- de7e278270c3ecee4a3d723948c4b9ad6cd6ea74375f7bdee715d94173df1b8dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65489
the chainentry 65489
- sealed to the entry before
- d4b7aae0652903863fd9237dfc6e3e2ea6b026200ac0d02fdaf66099ad843b4b
- this leaf
- 693835c0d3686787d5bdafc71f858196f1c155236f5c34d1209c6fbb886a9629
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7vIDiF3vlK0A6R1wIblvuXvZe976XENjENNi0g1EV/HMjUWqoOmAiKd7D89EK2t9YPaQX4EU1iS0J/VLBhk3Aw==