All insights

What Actually Happens When a Property Is Bought With Crypto

Kate SwiftKate Swift
What Actually Happens When a Property Is Bought With CryptoPayments

A contract is signed on a house. The price is agreed, the closing date is written into the deed, and the buyer's money is sitting in stablecoins. Both sides treat the financing question as settled.

It is not settled. The difficult part of the transaction lives in the days between the buyer sending value and the seller being able to use it, and almost none of it happens on a blockchain.

The deal has more parties than the contract names

A purchase reads like an agreement between two people. Operationally it involves at least six: the buyer, the seller, the seller's bank, the notary or escrow agent that most jurisdictions require for real property, the regulated intermediary converting crypto into the currency the deed is written in, and a compliance function inside every regulated participant.

Each of them can stop the transaction. None of them is scheduled around the date in the contract. The buyer negotiated with one counterparty and inherited five more.

Three clocks, and only one of them is fast

The on-chain leg takes minutes. A stablecoin transfer settles, the movement is visible to anyone who looks at it, and no business-hours calendar applies.

The conversion leg is usually quick as well. In ordinary market conditions, turning a stablecoin balance into euros or francs is a same-day operation.

The third clock is the one that decides whether the deal closes. The seller's bank has to accept an incoming payment whose origin is crypto, and that is the bank's own decision under its own anti-money-laundering obligations, not the sender's. This clock does not run in minutes, and nothing about a faster settlement layer speeds it up.

What the receiving bank is actually asking for

Most buyers misread the request. They hear "prove the money is yours" and send a screenshot of a wallet or a statement from an exchange showing a balance. That answers a question nobody asked.

What a receiving bank needs is the chain of origin: where the value was earned in the first place, and how it became crypto. A withdrawal confirmation describes the last step of a journey. The bank has to be able to describe the whole journey, because it is the institution that will have to defend the decision to its own supervisor.

This is what makes a crypto-funded purchase different from a conventional one rather than merely slower. When money arrives from a salary or the sale of a company, the origin comes with a single document and a counterparty the bank already recognises. A crypto balance may have accumulated over several years, across exchanges, self-custody and more than one jurisdiction, with no single institution able to attest to any of it. Reconstructing that history to an evidentiary standard is document work, and document work runs on human time.

The mistake that costs the calendar

In a conventional purchase, financing is arranged first and the formalities follow. Crypto-funded deals routinely invert that order: the contract is signed, the closing date starts counting down, and only then does anyone begin assembling the origin of the funds.

That inversion, rather than any outright refusal, is the most common reason these transactions slip. The documentation was always going to take the time it takes. Starting it after the deadline exists is what turns a manageable review into a missed completion date, a renegotiated contract, or a deposit at risk.

The order that works is the reverse one. The origin file is the long pole, so it belongs before the signature, not after it.

Why the bank behaves this way

It is tempting to read a bank's caution as a verdict on the buyer. It is usually neither personal nor really about crypto.

Banks have spent years reducing exposure to categories of client and corridor that cost more to supervise than they earn. De-risking works on categories rather than individuals, which is why a well-documented buyer with clean funds can still be declined for the category the payment belongs to. A compliance officer approving an inbound payment they cannot fully evidence carries a personal and institutional risk that no single transaction justifies.

Read that way, the task changes shape. It is not to convince a bank that crypto is legitimate. It is to hand the bank a file it can defend.

What changed, and what did not

Two things genuinely moved over the past few years. Settlement in regulated stablecoins shortened the transfer leg from days to minutes and made the movement of value auditable in a way a correspondent chain never was. And regulatory frameworks gave banks vocabulary they previously lacked, so a supervised institution can now point at a rulebook instead of at its own risk appetite when it explains a decision.

What did not move is the acceptance question. The chain got faster while the review that gates the money stayed exactly as long as it was. The bottleneck did not disappear. It relocated, from "will the transfer arrive" to "will the receiving institution accept where it came from".

Anyone selling speed in this market is describing the leg that was never slow. The part that decides whether a purchase completes is the fiat edge, and it is measured in documents rather than in blocks. That edge is where Stablegate's work sits.


Published for general information and education only. Not investment, financial, legal, or tax advice, and not an offer or solicitation in any jurisdiction. This is not marketing - Stablegate does not market its services to persons in the EU/EEA, the UK or the US (Restricted Persons).

The views expressed are current as of the publication date and may change. Third-party quotes are attributed and used under applicable quotation exceptions. Sourced and first-party data has not been independently verified and is provided without warranty. Any forward-looking statements are illustrative only. Past performance is not indicative of future results.

STGG AG is not a MiCA crypto-asset service provider (CASP) and does not offer or onboard services to Restricted Persons via this hub. Any service relationship arises only away from this hub, at the client's own exclusive initiative.

Kate Swift

Kate Swift

Kate writes on Stablegate's stablecoin settlement infrastructure and how banks are adapting to on-chain rails.