Definition
Taqabudh (تقابض) is the requirement of mutual, immediate, simultaneous possession in a contract of monetary exchange. It is the first of the four conditions of valid bai' al-sarf laid out in classical sarf guidance. Unlike qabd in the abstract — which is just possession by one side — taqabudh insists that both parties take possession in the same session (majlis al-'aqd) of the contract.
The principle exists because deferred settlement on a monetary exchange creates the conditions for riba: if one side delivers immediately and the other side delivers later, the time-difference itself becomes a price the deferring party effectively pays — which is interest in disguise.
How taqabudh applies to crypto
A spot trade on a regulated exchange satisfies taqabudh because the exchange's matching engine settles both legs in the same transaction cycle: the seller's crypto and the buyer's fiat (or quote-asset stablecoin) cross hands within seconds. Even when blockchain confirmation takes minutes, this remains within the classical "session of the contract" — Ibn Qudamah and other classical jurists explicitly accepted that "immediate" allows for the time required to physically complete the exchange.
A futures contract violates taqabudh by design: the entire purpose is to defer one or both legs to a future date. A perpetual swap violates taqabudh permanently — there is no settlement event ever. A margin trade violates it via the borrowing leg — the borrower's repayment is deferred and bears a cost.
Why this is the structural reason for spot-only
If you accept that taqabudh is a non-negotiable condition of valid sarf, and you accept that contemporary scholars treat crypto exchange as falling within sarf, then spot-only execution is not a stylistic preference — it is the only structural form that can satisfy the condition. The futures-vs-spot distinction is not a question of leverage magnitude or risk management. It is a question of whether possession transferred in the same session for both sides.
Implementation requirement
For a launch audit, taqabudh maps directly to workflow controls. The product should not ask users to enable futures, margin, options, earn, or universal-transfer permissions. The API integration should be scoped to spot balances and spot order routes. The user interface should say when onboarding is assisted and when payment is complete, instead of implying that a bot is active before the underlying account and permissions are verified. These controls keep the religious concept tied to actual system behavior.