E-commerce: the checkout is the funnel.
Every other part of the funnel is optimised relentlessly, and then the payment step is whatever the gateway shipped. That is usually where the recoverable revenue is.
Two different losses, usually confused
An online retailer loses payments twice: customers who abandon at the payment step, and customers who try to pay and are declined. They look similar in a funnel chart and have nothing in common underneath. Abandonment is a checkout design and method-availability problem. Declines are a routing, authentication and credential problem. Treating them as one number is why the fix never lands.
What teams in e-commerce face
Abandonment at the payment step
A long form on a phone, or the absence of the method the customer uses, loses the sale after you have already paid to acquire it.
Cross-border declines
Issuers treat cross-border card traffic more cautiously, so the same customer who converts domestically may be declined abroad.
Missing local methods
In many markets the preferred instrument is not an international card, and offering only cards reads as a foreign site.
Refunds and disputes at volume
Returns are part of retail, so refund flow and dispute handling are operational processes, not edge cases.
Mobile is the majority
Most checkouts happen on a phone, and anything designed desktop-first quietly loses there.
How a payment moves here
Present the right methods
Only the methods the customer can actually complete, named and presented the way their market expects.
Minimise the form
Wallets replace card entry with a device confirmation; hosted and embedded surfaces keep the rest short.
Authenticate proportionately
3-D Secure applied where required or helpful, using frictionless and exemption paths where the route and jurisdiction allow.
Route the authorization
Issuing country, BIN, amount and method select the route, with domestic routes used where they lift approval.
Recover what is recoverable
Soft declines retried on a reason-specific schedule, or cascaded, instead of being shown to the customer as failure.
Built for e-commerce
Hosted, embedded or headless checkout
Pick the surface that matches how much of the experience you want to own, and how much compliance scope you want to carry.
Wallet one-tap payment
Apple Pay and Google Pay turn the payment step into a confirmation, which is the single biggest mobile conversion lever available.
Local methods per market
Bank redirects, local schemes and wallets added as configuration rather than as a new integration per market.
Eligibility-aware presentation
Methods render only where the customer can complete them, so nobody reaches a dead end at the last step.
Authorization optimisation
BIN-aware routing, reason-aware retries and credential freshness attack the declines that should not be losses.
Refund and dispute handling
Full and partial refunds against the original payment, with chargebacks linked back to the transaction and the settlement that carried the deduction.
Method-level reporting
Conversion, approval and cost per method, so the checkout earns its place on evidence rather than habit.
What tends to matter here
- Cards
- Apple Pay and Google Pay
- Bank redirects and A2A
- Local and alternative methods per market
Availability depends on merchant category, jurisdiction, underwriting and the applicable payment or acquiring partner.
Sector-specific considerations
- Card-not-present retail attracts fraud pressure, so velocity controls, lists and BIN and country rules carry real weight.
- Chargeback ratios are monitored by schemes and acquirers; trend matters as much as absolute volume.
- Authentication is a conversion decision as well as a compliance one, which is why blanket challenges are the wrong default.
Flowa Pay provides the payment technology and orchestration layer. Acquiring, scheme settlement and regulated payment services are provided by licensed acquiring and payment partners under their own authorisations.
What experienced teams get right
The practical details that separate a payment stack that runs quietly from one that generates work every week.
- Measure abandonment and decline separately. They have different causes and different fixes.
- Refund timing differs by method; customer expectations should be set from the rail, not from cards generally.
- Test the checkout on a mid-range phone on a slow connection, because that is where the majority of real traffic lives.
E-commerceE-commerce questions
In markets where the local method is the norm, usually yes, and method-level reporting will show it on your own traffic. Adding methods a market does not use just lengthens the list.
No. Hosted, embedded and server-to-server all produce the same payment object. The choice is how much of the interface you want to own and how much compliance scope you want to carry.
We do not publish a number, because it depends entirely on your current decline mix, corridors and card products. The honest approach is to measure your baseline and show the change.
Yes. Orchestration can route across your existing acquiring and ours, which is also the cleanest way to compare them.
Solutions that serve e-commerce
These are the parts of the platform that do the work in this sector. Each one is a full solution page.
Hosted payment page
A checkout page Flowa Pay hosts, brands to your business and keeps current with scheme, authentication and method changes, so you do not have to.
Explore →Digital wallets
Wallet checkout removes the keyboard from the payment step: the customer authenticates on their device and a tokenized credential is presented for authorization.
Explore →Alternative payment methods
In most markets the preferred way to pay is not an international card. APMs give you the local method customers already use, without a separate integration for each one.
Explore →Authorization optimisation
A meaningful share of declines are not the issuer refusing the customer. They are avoidable: stale credentials, thin data, the wrong route, a retry at the wrong moment.
Explore →Ready to build for e-commerce?
Tell us about your flows and volumes and we will scope the routes and methods that fit.