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
- cbf22f02f1280367c95e68c8ee96b814907c9793d4bb2c59079215308156c18b
- request
- 4a2ec307277c8490a4fda1a7b711d5ffa4bf5271952d00730f76e6468a27d610
- transaction
- 1439571be6c4473be7ee98d694eeae044a77c57ed5dcb6f0daf34f1386fe41d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65133
the chainentry 65133
- sealed to the entry before
- 9303c3e654a4c71f37125b84ceb4de96cf8d29e9889c26cb43714c73ad8e0870
- this leaf
- fde88133e75a36c3f92daf27046b74208b188b325ec238046e22396a15d6e58c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b3+oRHNNi6DibFmhvEGx7DAKFVDuiiVfRWrnngWn1oWgwQxxyo3KynE9qQVT0IMs8bU8RuUvHsM/W+m8MbTCBw==