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
- 3e638bf0aaf4673618a62ea90f76c99b5bc3e6139b48e64845c5b674292bdf38
- request
- 754ae91ebe452eff09a7551f590cacec4a8ad33ddb084ed5b92a50601108a00d
- transaction
- 5339a5aab47a4644c37532adaa4aa7ab5d3a72e43a9baa4ad6201cc4b25fa752computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31950
the chainentry 31950
- sealed to the entry before
- f037d9ba7a59a23aae38514917dc28b5fce0962e7799a52e08e4b1fde3d2e266
- this leaf
- 9cf4705bd851b8ecf96bf7135e1df4aec562885222e504ee08fdc6d292f22c6f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CThVRvE4FIO1epU50r199ovSVaV/ys76rIpHv5hp334i+KIFA7/eoC8ZqHwm8/W+zwhpyFAg+BIhPKEpz4b1CA==