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
- 74775ad05b454c37e5769b0144b1e7cd4cdbfe48965783c5ce385dc6091535e1
- request
- 9baf2060934af3960abe5374c282118a3f14404c0f4bcb99b2f841be90e976b6
- transaction
- fd1587c6acd7771f84eaf7e5ceac26874d13926c2d66d92fcdab702cbde8c862computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12680
the chainentry 12680
- sealed to the entry before
- cadc53ce3cb53b95d921c27fce58cf0fb80f0b666e1778212e75cad8b3eb84c3
- this leaf
- d88498db612fca97e4f8f882dfedeb0bfad314b83d1b1029c871d7f17cd91345
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5f8EtLtpLGwQfjtZED+0kTCratKR9r4mvjACbOOi7JEKjZNRtNyuurOlG09i/8+yuUoI5wVqJsfislV2vl9oCg==