Deuteronomy 22:28-29 presents a challenging passage, both in terms of translation and ethical interpretation. The passage reads, according to many English versions, as a directive that if a man finds a young woman who is not betrothed and seizes her to have sexual relations, he must pay her father fifty shekels of silver and marry her, without the possibility of divorce. This passage raises significant ethical questions, particularly concerning the apparent treatment of the woman involved. To understand this passage, it is crucial to examine the Hebrew verb taphas, the context provided by the surrounding verses, and the broader ancient Near Eastern legal context.
The Hebrew Verb Taphas
The key verb in Deuteronomy 22:28 is taphas, which generally means "to seize" or "to take hold of." Some translations, such as the King James Version, use the term "lay hold on her," while others, like the NIV, use "seizes her." The term itself is less forceful than the verb chazaq used in Deuteronomy 22:25, which clearly denotes a violent action, often translated as "forces" or "rapes." This distinction is crucial, as the passage in verses 25-27 describes a situation of rape where the man is to be put to death, indicating a more violent and forceful act.
Scholars such as Jeffrey Tigay, in his commentary on Deuteronomy, note that taphas does not necessarily imply violence or force akin to rape. Instead, it can denote a range of actions from mere physical contact to a more aggressive seizure, but without the explicit connotation of violence that chazaq carries. This suggests that the situation in verses 28-29 may involve seduction or consensual premarital relations rather than assault.
Contrast with Deuteronomy 22:25-27
The passage immediately preceding, Deuteronomy 22:25-27, deals with a case of sexual assault where a man rapes a betrothed woman. The law prescribes the death penalty for the man, recognizing the violence and violation against the woman. This starkly contrasts with the treatment in verses 28-29, where the focus shifts to compensation and marriage rather than capital punishment.
This contrast has led some commentators, such as Walter Brueggemann, to argue that the latter case involves a less severe situation, possibly consensual. The differentiation in legal response underscores a distinction in the nature of the acts described, with the former being a clear act of violence and the latter potentially involving mutual consent or at least a less violent interaction.
Ancient Near Eastern Law Codes
To further understand the context of Deuteronomy 22:28-29, it is helpful to consider how other ancient Near Eastern legal codes addressed similar situations. The Code of Hammurabi, for example, contains provisions for cases of seduction, where the man is required to pay a bride price and marry the woman. This reflects a cultural emphasis on restoring the social and economic status of the woman and her family, rather than focusing solely on punitive measures against the perpetrator.
Such legal expectations are intended to ensure the woman's social standing and future security, given the significant stigma and economic disadvantage associated with being unmarried after such an incident. Thus, the requirement for the man to marry the woman and pay a bride price in Deuteronomy 22:28-29 aligns with broader ancient legal practices aimed at protecting the woman's future prospects.
The Word Deuteronomy Did Not Use
Hebrew has a verb for seduction, and Deuteronomy 22:28 does not use it.
Exodus 22:16 legislates the case that every defender of the seduction reading appeals to: "If a man pathah a virgin who is not betrothed and lies with her, he must make her his wife by payment of a bride-price." The verb pathah means to entice, persuade or seduce. It is the verb of talking someone round — used of Delilah coaxing Samson, of a prophet being enticed, of the simple being persuaded. It describes an act performed on someone's will.
Deuteronomy 22:28 legislates a case with the same participants — a man, an unbetrothed virgin, intercourse, fifty shekels to the father, marriage — and uses taphas instead: he seizes her, and lies with her.
This is the question the seduction reading has to answer, and it is rarely put to it directly. If the two passages describe the same offence, the drafter of Deuteronomy had the exact word for it, in a law he demonstrably knew, and chose a different one. Legal texts do not change their operative verb by accident. The change of word is itself evidence that the case has changed.
How Taphas Is Used of People
The claim that taphas is a mild verb can be tested, because the Hebrew Bible uses it roughly sixty times. The pattern that emerges is not ambiguous. When its object is a thing, it means to handle or wield — those who "handle" the lyre in Genesis 4:21, the priests who "handle" the Torah in Jeremiah 2:8, a soldier who handles a shield. When its object is a person, it means to capture.
| Passage | Use of taphas |
|---|---|
| Genesis 39:12 | Potiphar's wife taphas Joseph by his garment and says "Lie with me." He abandons the garment in her hand and runs. This is the one other place in the Hebrew Bible where taphas appears in a sexual context, and it is an attempted assault that the victim escapes. |
| Joshua 8:23 | The king of Ai is taphas alive — taken prisoner in war. |
| 1 Samuel 15:8 | Saul taphas King Agag of Amalek alive, while putting his people to the sword. |
| 1 Kings 18:40 | "Taphas the prophets of Baal, let not one of them escape." They are seized and killed. |
| Jeremiah 37:14 | Irijah taphas Jeremiah — arrests him — and hauls him before the officials. |
Not one of these is consensual. A prisoner of war, a condemned king, prophets about to be executed, an arrested man, and a man fleeing a sexual advance: in every case the person seized is going somewhere they do not wish to go. The Genesis 39 parallel is the most pointed, because it is the closest in kind — a person seized in order to obtain sex from them — and no reader has ever proposed that Joseph consented.
Honesty requires naming the one passage cited against this. Numbers 5:13, in the ordeal of the suspected wife, says of a woman who committed adultery that "she was not taphas." She was a willing participant, and the verb is still used of her. But the sense there is "not caught," not "not seized for sex" — it concerns whether she was apprehended as an offender, which is a different use again. It is worth noting that the Jewish Publication Society renders even that phrase "without being forced." The exception does not establish that taphas is a gentle word; it shows that its niphal can mean "detected."
What follows is narrower than the strongest version of the argument, and should be stated at its real strength rather than beyond it. Taphas is not a technical term for rape; that is why the translations divide. But it is not a soft word either, and the specific proposal that it denotes a seduction to which the woman consented is not supported by a single one of its other uses with a personal object. The seduction reading has to make taphas mean, uniquely here, something it means nowhere else — while the word that would have carried that meaning sat unused in a neighbouring law.
The Verb in Verse 29
The taphas argument rests entirely on verse 28. Verse 29 supplies a second verb, and it points the other way. The man must marry her tachat asher innah — "because he has innah her." The Jewish Publication Society renders it "because he has violated her."
This is the standard biblical verb for sexual violation. It is the verb used of Shechem and Dinah, where Genesis 34:2 says he "took her and lay with her and innah her"; of Amnon and Tamar, where 2 Samuel 13:14 says he "overpowered her and innah her"; and of the Levite's concubine at Gibeah in Judges 20:5, who was innah until she died. In each case the act is unambiguously forced, and in two of them it is a violent crime the narrative itself condemns.
An argument that verse 28 uses a milder verb than verse 25 has to reckon with verse 29 using the same verb as Dinah, Tamar and Gibeah. That does not settle the question on its own — innah carries a broader sense of humiliation or degradation of status, and a woman's position after premarital intercourse could be described that way without force. But it is a substantial piece of evidence, and any treatment that discusses taphas without mentioning innah has presented half the vocabulary.
How the Ancient Versions Read It
Before any modern committee weighed taphas, ancient translators and interpreters had already made their decision, and they leaned considerably further toward force than several later readings do.
| Source | Wording of Deuteronomy 22:28 | What it implies |
|---|---|---|
| Hebrew Masoretic Text | u-tefasah — "and he seizes her" | Force is possible, but the verb is broader than "rape." This is the ambiguity the whole debate turns on. |
| Septuagint (Greek, pre-Christian) | biasamenos — "having used force" | The Jewish translators in Alexandria read it as forcible. Brenton renders it "should force her and lie with her." Decisively, the Septuagint uses the same construction here as in verse 25, the acknowledged rape case — collapsing the very distinction the taphas argument depends on. |
| Latin Vulgate | apprehendens concubuerit cum illa — "seizing her, he lies with her" | Jerome preserves the seizing but does not reach for a specialised Latin word for rape. The Latin tradition is closer to the Hebrew's ambiguity than the Greek is. |
| Rabbinic tradition | Treated as the law of the ones (the rapist), distinct from the mefatteh (the seducer) of Exodus 22:16-17 | Classical Jewish law splits the two offences and assigns this passage to the rapist. |
The Septuagint evidence deserves particular weight, because it is the earliest interpretation available and it is Jewish rather than polemical. It is also the Old Testament that the Greek-speaking Church read. Whatever a Father in Antioch or Alexandria thought about these verses, the text in front of him said that the man had forced her — and said it in exactly the words used of the rape three verses earlier.
Here honesty requires a limit. Direct patristic commentary on Deuteronomy 22:28-29 is sparse; the Fathers did not linger over these two verses, and this article does not claim a chorus of them calling it rape. What can be documented is the text they were reading, and the Jewish legal tradition running alongside them, and both point the same way.
The rabbinic position is the most explicit of the four. The Mishnah in Ketubot 3:4 sets the two offenders side by side: the seducer pays three penalties, the rapist four, "and the rapist drinks from his vessel perforce" — that is, he is compelled to marry her — "and the seducer, if he wishes to release her, he releases her." That distinction maps directly onto the two biblical passages. Exodus 22:16-17 lets the father refuse the marriage; Deuteronomy 22:28-29 permits no refusal and no divorce ever. The rabbis assigned the compulsory case to the rapist. Later talmudic discussion (Ketubot 39a-b) does harmonise the passages in places, so the tradition is not perfectly uniform — but its basic legal architecture treats this passage as the rapist's law.
Why Modern Translations Say "Rape"
English versions divide sharply, and the division is not random.
| Renders verse 28 as force | Renders it as seizing |
|---|---|
| NIV — "and rapes her" CSB — "takes hold of her and rapes her" GNT — "caught raping a young woman" GOD'S WORD — "rapes a virgin" The Message — "grabs and rapes her" |
ESV — "seizes her and lies with her" NASB — "seizes her and lies with her" NKJV — "seizes her and lies with her" NRSV — "seizes her and lies with her" KJV — "lay hold on her, and lie with her" |
The NIV detail is the sharpest. It renders verse 25 "and rapes her" and verse 28 "and rapes her" — the same English verb for both, exactly as the Septuagint used the same Greek verb for both. The very distinction offered as the decisive argument for the seduction reading is one the NIV translators considered and declined to make in English.
This cannot be waved away as carelessness or as translators capitulating to modern sensibilities. These are committees with no motive to make their own scripture harder to defend — the NIV and the CSB are produced by conservative evangelical scholars, and this rendering hands critics of the Bible their sharpest verse. A committee does not volunteer that outcome unless it believes the Hebrew warrants it. Whatever else is true, "rape" here is a considered philological judgement by people whose incentives ran the other way.
Later Christian Commentators Divided
Among the standard English commentaries the disagreement is open, and it does not fall along predictable lines.
John Gill (1697-1771) argued explicitly that this was not rape. He read "lay hold on her" as an initial seizure to which the woman then yielded, and set it against the forcible case in verse 25. Matthew Poole (1624-1679) went the other way, taking "lay hold" to indicate force or overpowering, something stronger than seduction. Ellicott's Commentary heads the verses "SEDUCTION" and ties them to Exodus 22:16-17. Keil and Delitzsch describe the man as having seized her, but likewise read the law in close connection with the Exodus provision for an unbetrothed virgin.
Two features of this disagreement are worth naming. The commentators who read it as seduction generally do so by linking it to Exodus 22:16-17 — but that linkage is an interpretive move, not something the text states, and it has to explain why Exodus lets the father refuse the marriage while Deuteronomy does not. And the disagreement is not a modern development: Poole and Gill are separated by two generations, both are working carefully from the Hebrew, and they reach opposite conclusions.
Range of Scholarly Readings
Christian scholars have approached this passage with varying perspectives. Some, like Richard M. Davidson, emphasize that the passage must be understood within its historical and cultural context, where marriage after such an incident might have been seen as a protective measure for the woman. Others, such as Cheryl B. Anderson, critique the text from a modern ethical standpoint, acknowledging the difficulty of reconciling it with contemporary values of autonomy and justice.
A third group of scholars declines the question as posed. Carolyn Pressler, in her study of the Deuteronomic family laws, argues that the passage does not distinguish rape from seduction at all - that the law is drafted to cover the unbetrothed virgin's case generally, because what it is regulating is the damage to the household and the woman's marriageability rather than the presence or absence of her consent. Alexander Rofe, Cynthia Edenberg and Sara Milstein have all treated the passage in relation to its ancient Near Eastern parallels in similar terms. On this reading the modern debate is asking a question the drafter was not answering, which would explain why the vocabulary supports neither side cleanly.
Many scholars agree that the passage, when read in its historical and linguistic context, does not necessarily endorse or condone the act described. Rather, it reflects an attempt to address a complex social issue within the legal and cultural framework of the time. The text, therefore, should not be seen as an endorsement of harmful behavior but as a legal provision aimed at mitigating its social consequences.
Conclusion
Deuteronomy 22:28-29 is genuinely difficult, and it should not be presented as settled in either direction.
The case for the seduction reading is real. Taphas is a broader verb than chazaq; the change of verb between verses 25 and 28 is unlikely to be accidental in a legal text drafting cases in deliberate sequence; the penalties differ sharply, death in the one case and marriage with compensation in the other; and a stream of serious commentators from Gill to Keil and Delitzsch has read it that way.
But the evidence on the other side is stronger than the passage's defenders usually allow, and it is not the invention of modern critics. Hebrew has a verb for seduction, pathah, which Exodus 22:16 uses for exactly the case the seduction reading wants this to be - and Deuteronomy did not use it. Taphas, the verb it used instead, is applied to people some dozens of times in the Hebrew Bible and means capture every time: a king taken in war, prophets seized for execution, Jeremiah arrested, and Joseph grabbed by Potiphar's wife while he ran. The Septuagint, the earliest interpretation we possess and a Jewish one, used a verb of force here and used the same construction it had used of the rape in verse 25. Verse 29 describes what the man did with innah, the verb applied to Dinah, to Tamar and to the concubine at Gibeah. Classical Jewish law assigned this passage to the rapist rather than the seducer, on the reasoning that this is the case where the marriage cannot be refused. And the translation committees behind the NIV and the CSB, who had every incentive to render it gently, rendered it "rape" — the NIV using the identical English verb in verse 28 that it uses in verse 25.
Where that leaves the reader is uncomfortable, and the discomfort is the honest result. The Hebrew of verse 28 is ambiguous, and the ambiguity is real rather than manufactured; taphas is not a technical term for rape, and that is why the translations divide. But the choice of taphas over pathah, its usage everywhere else with a personal object, the vocabulary of verse 29, the ancient versions, and the earliest Jewish legal reading all lean the same way, and the modern translations that say so are following the evidence rather than the culture. Any confident claim that this passage is simply about seduction has to argue past all five - and the argument for it usually rests on one verb in one verse, while leaving unmentioned both the word the drafter declined to use and the way he used the word he chose.
What remains true in either reading is that the law's remedy — compensation to the father and a marriage the man may never end — treats the woman's future security as the interest to be protected, in a legal world where an unmarried non-virgin faced severe economic and social consequences. Readers should be clear-eyed that this is a remedy framed around her standing rather than her consent, which is precisely why modern readers find it troubling whichever way the verb is decided.