NovA backup payment route belongs before the failure
How to prepare a legitimate second route for an international property payment without changing the recipient, transaction basis or evidence trail under deadline pressure.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
A backup payment route is useful only if it has been defined while nothing is wrong. Once a deadline is close and the primary bank has delayed a transfer, almost any alternative can look attractive: another account, another sender, another provider, perhaps a different currency. That urgency is exactly why the alternative needs boundaries. A second route should preserve the transaction wherever possible, not quietly turn it into a different arrangement.
I think of the problem in two layers. The property contract creates the obligation: a certain party owes a certain amount, in a certain currency, for an identified purchase or instalment. The banking route is the mechanism used to discharge that obligation. If the backup changes the payer, beneficiary, currency, payment basis or reference, the buyer may no longer be changing only the mechanism. The new setup may need fresh approval from the seller, bank or legal adviser before money moves.
Keep the commercial facts fixed before choosing a second bank
The first useful exercise is not to compare transfer fees. It is to list what must remain true. Who is paying? Who is legally entitled to receive the money? Which apartment and contractual stage does the payment relate to? What amount should the recipient recognise? Which document will prove that the obligation was satisfied?
Imagine a buyer who intends to send the second instalment from Bank A to the developer’s official account. Two days before the due date, Bank A says the transfer requires additional review. The buyer also has an account at Bank B. If Bank B can send the same currency from the same buyer to the same beneficiary using the same documented payment basis, it may be a practical reserve. It is still not automatically approved. Bank B can apply its own checks, limits and documentation requirements.
Now change one fact: the proposed backup uses a relative’s account or an intermediary company. That is no longer a simple channel switch. The recipient needs to understand why a third party is paying; the sending bank may require a different explanation; the transaction record needs to connect the sender to the buyer’s obligation. The phrase “we can always use another account” hides a material decision.
A backup only works if it addresses the actual failure
“Bank problem” is too vague to design around. A transfer can fail because the payment was never accepted, because account details are wrong, because the bank wants supporting documents, because a product limit applies, because the transaction is already under review, or because the receiving side has an issue. Those situations do not call for the same response.
If a payment is already in flight, launching the same amount through a second route can create duplicate settlement. If the beneficiary is not properly documented, another bank does not repair that weakness. If the sending bank is asking for evidence of source of funds or the purchase basis, moving the instruction elsewhere simply creates another institution that may ask the same question.
That is why I want the status of the first attempt before switching. “The app showed an error” is not as useful as “the bank confirms the instruction was not accepted.” A visible, documentable switch point reduces the risk that the reserve route produces two live payments instead of one completed obligation.
Agree the reserve scenario before the payment date
A good backup can be described in a few lines. Primary route: buyer’s account at Bank A. Reserve route: buyer’s account at Bank B. Beneficiary, currency and property reference remain unchanged. The reserve is used only after the buyer confirms that no payment is already moving through Bank A. The seller has confirmed how the alternative sending account will be recognised.
That short description does not guarantee success. It simply means that the buyer is not inventing the structure under pressure. The second bank can be approached in advance with the transaction context, expected amount and supporting documents. The seller can confirm the accepted reference. The buyer can see whether Bank B’s interface or product has practical constraints before the due date arrives.
Timing deserves the same treatment. If the contract cares about when funds are credited rather than when an instruction is submitted, a reserve route may need a different lead time. Banking holidays, cut-off times and intermediary processing can affect the result. The reserve is therefore better treated as a dated operational option, not a permanent promise that any bank can deliver by any deadline.
The alternative has its own cost and evidence
A second route can produce different charges, intermediary deductions and confirmation formats. Those differences matter when the seller expects a precise net amount. They also matter later when somebody tries to reconcile what left the buyer’s account with what arrived at the seller’s account.
A universal estimate for an international transfer would be misleading. The result depends on the banks, currency, correspondent path and account terms. The more useful comparison is between actual, current information from the buyer’s two institutions. Which fees are disclosed? Can the payer choose how charges are allocated? What documentation will the bank provide? How will the transaction be identified if it needs to be traced?
Swift’s payment infrastructure uses end-to-end transaction references and tracking tools to improve visibility. That is useful, but the buyer still needs the records available from the bank they actually use. A sophisticated network does not remove the need for a clear local confirmation.
One transaction should still leave one coherent story
When a backup route is activated, the documentary history often becomes fragmented. The original invoice sits in one email chain, the first bank’s rejection in another, the second bank’s receipt in an app, and the seller’s acknowledgement in a chat. The payment may have succeeded, yet the evidence becomes unnecessarily hard to reconstruct.
Those pieces belong together while the facts are fresh: original payment instruction; status of the abandoned route; written confirmation of the alternative; the new bank receipt and transaction reference; and the seller’s acknowledgement that the correct instalment was credited. If only the sending bank changed, the file should make that obvious. If something more material changed, the file should explain that too.
The purpose of a backup route is not to make money move at any cost. It is to preserve a valid transaction when one delivery mechanism becomes unavailable. The best time to define that route is before a failure, when the buyer can still distinguish a real alternative from an improvised workaround.
Sources
- NovAsia Estate — “Payments and banking when buying property in Cambodia”: beneficiary verification, documented payment instructions and confirmation of settlement; accessed 6 October 2026.
- Swift — Payments / Tracking: transaction tracking and end-to-end payment references; accessed 6 October 2026.
- Swift — About ISO 20022 and ISO 20022 for Financial Institutions: structured payment data and improved reconciliation; accessed 6 October 2026.