A payment gateway should be chosen as an operational and financial service, not merely as a checkout logo. A UK business needs to assess customer payment methods, fees, settlement, refunds, disputes, recurring-payment support, data handling and the quality of support when money does not arrive as expected.
Define the required payment journey
List the ways customers must pay: cards, digital wallets, bank methods, pay-later options or recurring payments. Then identify whether checkout must remain on the site, redirect to the provider, save payment methods, support deposits or handle subscriptions. A gateway that works for one-off card sales may not support the lifecycle of a membership or instalment product.
Compare the full operating model
| Area | What to verify |
|---|---|
| Eligibility | Supported business type, country, currencies and prohibited activities |
| Customer experience | On-site or redirected checkout, wallets, authentication and mobile flow |
| Charges | Domestic and international cards, currency conversion, refunds, disputes and optional services |
| Settlement | Payout schedule, reserves, minimums and bank-account requirements |
| Operations | Dashboard, exports, reconciliation, refunds and staff permissions |
| Reliability | Webhook handling, failed-payment recovery, status pages and support route |
| Compatibility | WooCommerce version, subscriptions, saved cards and other required extensions |
Shortlist providers by fit, not popularity
WooPayments provides an integrated WooCommerce experience where it is available. Stripe and PayPal integrations are also common choices, while other gateways may be required for a particular acquirer, sector or finance method. The correct shortlist depends on the business rather than a universal ranking.
Check current UK pricing directly with each provider. Transaction pricing can vary by card origin, currency and payment method, and the published headline rate may not represent the actual sales mix. Premium WooCommerce gateway extensions can also have annual licence costs in addition to processor fees.
Test the money lifecycle
- Complete a successful test payment and confirm the WooCommerce order reaches the correct status.
- Force a failed or abandoned payment and check what the customer and staff see.
- Issue a full and partial refund from the intended operating interface.
- Confirm settlement reports can be matched to WooCommerce orders and bank payouts.
- Test payment callbacks after a delay, duplicate submission and an interrupted browser session.
- Check recurring or saved-payment behaviour when those features are required.
Plan for disputes and access control
Decide who can view transactions, issue refunds, change payout details and manage API credentials. Do not share a single owner login. Keep recovery methods under business control and record the escalation route for a frozen account, disputed payment or withheld payout.
The gateway dashboard and WooCommerce are separate records. Reconcile them regularly; a WooCommerce status alone does not prove that money settled, and a gateway payment alone does not prove fulfilment occurred.
Avoid unnecessary payment scope
Use provider-hosted fields, tokens and supported integrations rather than collecting raw card details in WordPress. Do not copy gateway code from an old site or install unofficial versions of paid extensions. Review privacy information, retention and fraud tools with the provider and obtain specialist advice where the business has unusual regulatory or contractual requirements.
Acceptance criteria for the chosen gateway
The final decision should produce evidence, not only a commercial quote. Record the legal account owner, enabled methods, currencies, payout bank, refund permissions, dispute route, webhook status and support contacts. Confirm who reconciles payouts and how missing or duplicated payments are investigated.
- Test transactions appear consistently in WooCommerce and the provider dashboard.
- Refunds and disputes have named owners and audit evidence.
- API credentials can be rotated without losing the business account.
- The fallback plan is documented if the provider pauses payments.
Practical next step
Create two or three realistic test baskets and ask each shortlisted provider to demonstrate payment, failure, refund, settlement export and support escalation before the final gateway is selected.
Sources and date checked
This guide was checked on 21 July 2026. WordPress, plugins, hosting platforms and commercial terms change, so confirm the current documentation and licence details before making a material change.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.