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
- 1037e51eeaa05cf8242f6960845642070fe47e6f5ea89135f06b48947864dcc3
- request
- f631df6f1380bf6487ffb43d1ac26d67b9c027da889eb0bc0627c50260226827
- transaction
- 97d30e42a172dc384fd591fc4039a7fcfc2282a9b58162cd5dffeba69f3546bdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41182
the chainentry 41182
- sealed to the entry before
- 55d9ea31f5a15eabd105cc3e254be01aa3c9f23345a3afad7d2e4d0561da5f27
- this leaf
- 8496886fa7a4eacbd3607187743fcd3aa0680d2a530193ab53ee0a29fa80ac1d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9zYpkJqYSq0R+OhHNkPvsAPajBIBMI9LMt0Tf+FiTTrpvPiK0HkNTatccoaF7PtTJoEucljT94CZqRdATeLfAw==