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
- cfcd4a7f752d65d14e3d2680ee69f111c12ad9938cfd2bcec3d7ef170b2f7601
- request
- 383598daa91f6140e521606ec3e6f13c1c18e503ba07570009827d4eddc89b22
- transaction
- b1fc763ad764dc95f81764da5f96584dd77fdc708f89988003c82a25cd2f1d90computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2225
the chainentry 2225
- sealed to the entry before
- d458b54477646e753d87d2b69cd4807f0866fb63d44cc96ba07b562e019345d4
- this leaf
- 5eeaf8af14e80b5765dd75cdfce931b36d76f17fcd9b0639f91f92fc4012e820
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- teW6PqUiBuUZATGBesvBXg7jFEE7ZrV5n+6WGavA+/HerSe+qGwdrxjnmQ3Kh6WpEUDrFpeTb4VFCZyxzYAvCg==