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
- 69da293702e80f7050f2530d150d1e47cd31ee876caae4d666502cccf6c2801c
- request
- 7d1e130388fc68303771ee45dadcf3454fc54875b8b9d63dec5ff2278936ea08
- transaction
- 9acf4722bbf218197ec06ced18769fa41062fbdb49f3edf4f85e11809f7031f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1088
the chainentry 1088
- sealed to the entry before
- 9f572cff5fac36fa98f6d44b7589c3a758a546125ec7244e93ce19e5f573da57
- this leaf
- 861fa923e3d7b8d69ec21f61a920f2ec044410bf4730d9be716b9fc118eb6735
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z3TuLwC6WtM3dQaPxkhdsG88SkU9Vtp0gInH04GjGTUcG8sm/dFR1VUBDds548Tyid6wwWdab1QQe3XM5YnHCg==