Reducing Failed and Abandoned Payments at Checkout

Two different things are happening at your checkout and most stores lump them together, which is why neither gets fixed. Abandonment is a customer who leaves before payment starts — a design, trust or cost problem. Failure is a customer who tried to pay and could not — a bank, method or session problem. They have almost nothing in common except the outcome, and the diagnosis is the whole job.

Start by finding out which one you have. If you cannot separate them, that is the first fix: your gateway reports payment attempts and their outcomes; your store analytics reports how many people reached checkout. Abandonment is the gap between reaching checkout and attempting payment. Failure is the gap between attempting and succeeding.

Abandonment: the five causes, in order of size

1. Unexpected costs. Shipping, fees or taxes appearing at the last step is the single largest cause of abandonment in almost every store. Show the delivery cost before the final step, or offer a threshold above which it is free. Under the Consumer Protection (Electronic Trade Transactions) Regulations 2024, the full price payable must be disclosed before purchase anyway — so this is both a conversion fix and a compliance one. If your parcels are bulky, volumetric weight explains why your shipping quote may be higher than customers expect.

2. Forced account creation. Guest checkout is not a nice-to-have. Offer the account afterwards, when the customer has already got what they came for.

3. Too many fields. Every optional field costs conversions. Ask for what you need to deliver and to contact them, and nothing else. Note the tension with address quality — the fix is better-structured fields, not more of them; see reducing failed deliveries.

4. Missing the payment method they use. A customer who does not see their bank in the FPX list, or their preferred wallet, leaves. Check your gateway's coverage against what your customers actually use.

5. Trust signals absent. A Malaysian shopper on an unfamiliar site looks for a real business name, a contact number that works, a returns policy, and recognisable payment logos. Missing any of them is a reason to close the tab. Your returns policy is a conversion asset, not just a legal document.

Failure: what actually goes wrong mid-payment

Notice how many are outside your control. That is the important insight: you cannot prevent most payment failures, so the thing to optimise is what happens next. A failure that ends in a blank error page is a lost sale. A failure that ends with "that didn't go through — try another method?" and one tap is frequently a completed one.

The recovery flow, which most stores do not have

1. Never dead-end. Every failure screen offers an immediate retry and a different payment method.
2. Keep the cart. A customer returning after a failure should not have to rebuild the order. This alone recovers a meaningful share.
3. Say something useful. "Payment unsuccessful — your bank did not complete the transaction. Nothing has been charged. Try again or use a different method." The "nothing has been charged" line prevents the support message you would otherwise get.
4. Follow up, once. If you have their contact and consent, a single message with a link to resume is effective. Once. A second is nagging.
5. Use a payment link for the recovery if you are already talking to the customer on WhatsApp — see payment links.

The two numbers to track

• Checkout completion rate = orders completed ÷ checkouts started. Moves with design, cost transparency and trust.
• Payment success rate (authorisation rate) = successful payments ÷ payment attempts. Moves with methods, banks and session handling.

Track them separately and monthly. A store with 90% payment success and 40% checkout completion has a design problem. A store with 75% payment success and 80% checkout completion has a payments problem. Same total conversion, completely different work.

If payment success is low, break it down by method and by bank. A single bank failing far more than the others is usually a gateway routing issue worth raising with your provider — and it is invisible in the aggregate number.

What not to do

• Do not add a payment surcharge at the last step. It is the most reliable way to cause abandonment, and disclosing the full price beforehand is a legal requirement, not a preference.
• Do not remove payment methods to save fees without checking usage first. Losing the sale costs more than the fee — the arithmetic is in FPX vs cards vs e-wallets.
• Do not blame the gateway before you have looked. Most failures are bank-side or session-side, and both are partly yours to mitigate.
• Do not test only on desktop. Most Malaysian shoppers are on a phone, switching to a banking app mid-flow, and that is precisely the journey where sessions break.

Frequently asked questions

What is a normal payment success rate?
It varies by method mix, category and customer base, so a published benchmark is not useful. Measure your own for a month, then break it down by method and bank — the outliers within your own data tell you far more than any industry average.

Should I offer a discount to recover abandoned carts?
Sparingly. Regular recovery discounts teach customers to abandon deliberately. A reminder with the cart preserved usually performs nearly as well without the margin cost or the trained behaviour.

Customers say the payment page looks suspicious. What can I do?
Check that your business name — not an unfamiliar gateway entity — appears on the payment page and on the bank statement descriptor. Mismatched names are a common and entirely fixable cause of both abandonment and disputes.

Does adding more payment methods always help?
Up to a point. Missing methods your customers use costs sales; adding rarely used ones adds reconciliation work and choice paralysis at checkout. Add based on your own data, and review annually which ones are actually being used.

How much of this can I fix without a developer?
Most of it. Guest checkout, field count, showing delivery cost earlier, error message wording and trust signals are usually configuration or content changes on a standard store platform. Our checkout guide covers the settings.

Sources: the requirement to disclose the full price payable before purchase arises under the Consumer Protection (Electronic Trade Transactions) Regulations 2024 (in force 25 December 2024), administered by KPDN. FPX and DuitNow are operated by Payments Network Malaysia (PayNet). No benchmark conversion or authorisation rates are quoted — these vary so much by category, method mix and customer base that a published figure would mislead; measure your own.