Setting up payment gateways for fewer declines and lower fees

Most stores choose a payment provider during the original build, accept the default settings and never look again. That is understandable, since payments either work or they do not, and nobody wants to touch something that works. But "works" hides a lot. We regularly audit stores where three to eight percent of legitimate payment attempts are declined, fees are higher than they need to be, and nobody has looked at the decline reasons in years. Payment configuration is one of the few places where a week of engineering can move revenue directly.

Start with the decline data

Every gateway reports why a payment failed, but the categories are buried in dashboards or raw logs. Pull three months of attempts and group them by reason. The pattern usually falls into a few buckets:

• Issuer declines: insufficient funds, do not honor, or suspected fraud flagged by the card issuer.
• Authentication failures: the customer abandoned or failed a 3-D Secure challenge.
• Your own fraud rules: payments blocked by risk settings you or a previous developer configured.
• Technical errors: timeouts, misconfigured webhooks or browser-specific wallet failures.

Insufficient funds is not your problem to solve. Everything else is at least partly within your control. On a recent audit for a subscription brand, a single fraud rule that blocked any mismatch between billing and shipping country accounted for almost a third of declines. Most of those customers were expats and gift buyers with perfectly good cards.

Offer the methods your buyers actually use

Wallets such as Apple Pay, Google Pay and PayPal reduce friction and often reduce declines, because the tokenized credentials carry stronger authentication signals. For many DTC stores, wallets now account for 30 to 50 percent of mobile orders once they are placed prominently at the top of checkout rather than hidden behind a card form.

Beyond wallets, match payment methods to your markets. Buyers in the Netherlands expect iDEAL, in Germany many prefer invoice-based payment or SEPA, and in parts of Asia local wallets dominate. Adding a method that 20 percent of a market prefers is often worth more than any design change to the checkout. Buy now, pay later options can lift average order value on higher-priced goods, but they come with higher fees, so test them on the categories where they matter rather than enabling them everywhere.

Payments either work or they do not, so nobody looks. But a store losing five percent of legitimate attempts is losing money every hour it stays that way.

Handle strong authentication gracefully

In regions with strong customer authentication requirements, 3-D Secure is mandatory for many transactions. Handled poorly, it is a major source of abandonment: a modal that fails to load on mobile, a redirect that loses the cart, or a challenge requested when an exemption could have applied. Modern gateway integrations can request exemptions for low-value or low-risk transactions and apply challenges only when the issuer requires them.

Check three things. Does your integration use the gateway's current payment API rather than a legacy charge endpoint? Are exemptions being requested where eligible? And does the challenge flow work reliably inside in-app browsers from social platforms, where a surprising share of mobile traffic now arrives? Testing these with real devices finds issues that sandbox testing misses.

Reduce fees without hurting conversion

Processing fees on a mid-size store can easily exceed the cost of hosting and development combined. A few levers are worth reviewing annually:

1. Negotiate. Once you process more than a few hundred thousand dollars a month, most providers will discuss custom pricing. Ask.
2. Understand interchange. International and premium cards cost more. If a large share of your volume is cross-border, local acquiring in key markets can cut costs significantly.
3. Watch currency conversion. Charging in the buyer's currency with poor conversion rates can cost you both fees and conversion. Compare the rates your provider applies.
4. Retire unused methods. Each extra method adds complexity. If one sees almost no volume, remove it.

Build in resilience

Gateways do go down. A 45-minute outage during a promotion can cost more than a year of fees. Larger stores should consider a secondary processor that can be switched on quickly, or routing logic that fails over automatically when the primary returns errors. This is more complex on hosted platforms, where the checkout is controlled by the platform, and more straightforward on custom or WooCommerce stacks.

Retries also matter for subscriptions and saved cards. A payment that fails for insufficient funds on the first of the month often succeeds a few days later. Smart retry schedules, combined with a clear dunning email sequence, routinely recover a third or more of failed renewals.

Monitor like it matters

Treat payment success rate as a core business metric. We set up a dashboard showing authorization rate by method, device and country, with an alert if the rate drops more than a few points below its trailing average. That alert has caught expired API keys, broken wallet buttons after theme updates and a misconfigured webhook that stopped orders from being marked as paid.

A periodic security audit should cover payments too: how keys are stored, who has dashboard access and whether webhooks are signed and verified. Payment configuration is both a revenue system and an attack surface.

Our payment gateway integration work covers audits, new method rollouts and failover setups across Shopify, WooCommerce and custom platforms. When the checkout itself needs work, it pairs naturally with conversion rate optimization so the payment step is measured alongside everything that leads up to it.

Find out what your payments are costing you

If you have not looked at decline reasons or fees in the last year, there is likely money on the table. Ask us for a payments review and we will send a fixed-price quote within 24 hours.