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
- e36591bd7f537b99bb545110c4cc740452ce1b62f223fe465945576e04320f94
- request
- 8df84fd2b37206b98a41b395b92bef6149e475348e05a894983010f17dfa2383
- transaction
- 2926f591d3b551e222035b3e6b2816c45959ce8ce3c0497d355438e8f910d701computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66022
the chainentry 66022
- sealed to the entry before
- 1f2d000825d644c7365fc44cd4da169aa455abed3c50bae3ac5d7525fa487caf
- this leaf
- 83a07fa8306af460fd5b45a0b1d6674df9f8c014689b51a76daf9b3e3cd8a622
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LbkdC3Bn/bs/jBdWZ0rYQlY7hCWOh3JLbevspYYSy9GHzhDpcp9Ogmhpb4NEU0iUdBzFjV4IkaQgC/CObjgyBA==