Recently, requirements for the explainability of software systems have gained\nprominence. One of the primary motivators for such requirements is that\nexplainability is expected to facilitate stakeholders' trust in a system.\nAlthough this seems intuitively appealing, recent psychological studies\nindicate that explanations do not necessarily facilitate trust. Thus,\nexplainability requirements might not be suitable for promoting trust.\n One way to accommodate this finding is, we suggest, to focus on\ntrustworthiness instead of trust. While these two may come apart, we ideally\nwant both: a trustworthy system and the stakeholder's trust. In this paper, we\nargue that even though trustworthiness does not automatically lead to trust,\nthere are several reasons to engineer primarily for trustworthiness -- and that\na system's explainability can crucially contribute to its trustworthiness.\n