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
- 157e107e11f147177903bb5929cdb0fb6df58fd628be06282477096bf9f7e9ee
- request
- 305d875d414cf2afc5824987ba7ce7a892da0ffb59b142fcea36a3671fa30e90
- transaction
- 36a04a70bee931bf1cc971c97b5f32083c7c7c601e7db0f5c59c661f6926b12acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22929
the chainentry 22929
- sealed to the entry before
- fc1472ef847b98e018bd57fc32533f56848813b847af3c7ac1dc8d5380f69105
- this leaf
- fa38d6a8272885d1d1562791a1117c155955fc2a89a2014d3b73641c9548b0e6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /QSUKzoFYRRT1+c57vojHY9Rpe0//v4JR7EvgBADJDgYDa+Rg0nkNLvqunxqJLd76ZpRKCJE0tTFUQMWImMuBw==