The risks in cross-chain routing, stated plainly
Direct payments are simple transfers. Routed payments cross chains and swap assets, and that introduces real risks. Here is what can go wrong, and what Apa does to reduce it.
Risks specific to routed payments
Every item below applies only when a payment has to be converted across assets or networks. An exact-match direct payment avoids all of them — it settles to your wallet and is final the moment it confirms.
Route delays
A route can take longer than expected when a chain is congested or a bridge is slow to relay. The checkout stays in a routing state and tracks each stage until it settles.
Bridge failures
Bridges are third-party infrastructure and can pause, fail or hold funds in transit. Apa routes through providers with safe-route filtering, but a bridge can still stall a payment.
Price protection
Conversions fill against live market prices, so the price can move between quote and execution. Apa applies price protection automatically and won't settle a route outside safe bounds — a conversion reverts rather than settling you a worse amount.
Wrong-network payments
If a customer sends funds on a network the checkout did not request, the transfer may not be recognised and can be hard or impossible to recover.
Quote expiry
A route quote is only valid for a short window. If the customer waits too long to sign, the quote expires and must be refreshed at the current market price.
Irreversible transactions
Blockchain transfers cannot be reversed once confirmed. There is no chargeback. A mistaken or fraudulent payment can only be resolved by the merchant sending funds back.
Mitigations applied to every routed payment
Apa cannot remove on-chain risk, but it filters and constrains routes so a payment fails safely rather than settling at a bad price or on a dead path.
- Safe-route filtering — Apa only offers vetted routes, and unsafe or illiquid paths are excluded.
- Quote expiry — quotes are time-boxed and refreshed, so customers never sign a stale price.
- Price protection — Apa won't settle a route outside safe bounds, so a conversion reverts instead of filling far below the quote.
- Automatic failover — if one path cannot return a viable route, Apa's routing engine falls back to another before failing the payment.
- Live status — created, pending, routing, paid, expired and failed are tracked end to end so a stalled payment is visible immediately.
- Non-custodial by design — Apa never holds funds, so a routing failure does not put your money inside Apa.
Refund-required cases
Because transactions are irreversible, crypto payments are final and chargeback-free. That is an upside — no fraud chargebacks — and a responsibility: refunds are handled by the merchant directly. Apa flags refund-required cases but, being non-custodial, cannot reverse a settled payment. These are the situations where a refund is typically warranted.
Funds arrived off-path
A customer paid on a network the order did not expect. If the funds are recoverable, the merchant returns them to the customer's address rather than treating the order as paid.
Customer sent too much
If a transfer exceeds the amount due, the merchant refunds the difference. Apa records the on-chain amount so the overage is clear.
Payment never settled
If a route fails after the customer's funds left their wallet, recovery depends on the bridge. The merchant coordinates a return once funds are accounted for.
Order cancelled after pay
There are no chargebacks on-chain. To unwind a confirmed payment, the merchant must send funds back to the customer manually.
Risk FAQ
Can a payment be reversed if something goes wrong?
No. Once a blockchain transaction confirms it is final. There are no chargebacks. Any return of funds is a new transaction the merchant chooses to send.
What happens if the bridge stalls mid-route?
The checkout stays in a routing state and the status reflects that it has not settled. Recovery depends on the bridge provider; Apa surfaces the state but cannot force a third-party bridge to complete.
What happens to my customer's money if a routed payment can't complete?
A routed payment that cannot complete is built to return the funds to the customer's source wallet, and the payment is marked failed or refund-required. Because Apa is non-custodial it never holds the funds at any point, so any leftover edge case is coordinated with the merchant — Apa does not move or hold customer money.
How does Apa protect the conversion price?
Apa applies price protection automatically. If the market moves outside safe bounds before execution, the conversion reverts rather than filling at a worse price, and the quote must be refreshed.
Does using Apa reduce my counterparty risk?
Apa is non-custodial, so it never holds your funds — that removes Apa as a counterparty. The remaining risk lives in the chains and bridges the payment passes through, which Apa filters but does not control.
Honest about risk. Built to fail safely.
Create your first payment link or API checkout in minutes. Direct payments are free, routed conversions are flat, and Apa never holds your funds.