How UK Businesses Can Choose a Payment Gateway for International Expansion

Define your international payment requirements

Before comparing payment providers, turn your expansion plans into a payment requirements brief. For a UK business targeting the UAE, accepting payments from overseas customers, charging in AED and receiving AED settlement are separate requirements. Specify which you need at launch and which can wait until transaction volumes justify them.

Build the brief around six areas:

• Target countries and merchant entities: List your launch markets, planned expansion markets and the legal entity that will contract with customers and receive settlement. Distinguish sales made through your UK company from any planned UAE entity; customer location and merchant location are different inputs when comparing services.
• Transaction volumes and average order values: Estimate monthly transaction counts, payment value and average order value by market and currency. Include peak trading periods, typical maximum transaction values and expected refund rates. These assumptions give providers a consistent basis for pricing and capacity discussions.
• Presentment and settlement currencies: Record the currencies customers should see and pay in, such as GBP and AED, separately from the currencies you want paid into your bank accounts. State where those accounts are held and whether you want to retain foreign-currency receipts or convert them into GBP.
• Sales channels and integrations: Identify website checkout, mobile apps, payment links, marketplaces and any in-person sales. For marketplaces, clarify whether you collect only your own revenue or also handle payments and payouts for third-party sellers. List your e-commerce platform, accounting system and API requirements, including how payments, refunds and settlement reports should reconcile.
• Payment timing and subscription requirements: Specify whether you need one-off payments, recurring billing or both. Record fulfilment timing and when payments should be authorised and captured, including any deposits, pre-orders or delayed deliveries. For subscriptions, record requirements for securely stored payment credentials, customer consent, free trials, variable billing amounts, failed-payment retries and cancellations. Confirm whether billing logic will sit in your own system or the provider's service.
• Commercial constraints: Set acceptable limits for total payment costs, FX margins, payout delays, reserves, minimum monthly charges and contract length. Include your implementation budget and launch deadline.

Next, define what you are buying. A standalone payment gateway securely captures and routes payment information, typically connecting your checkout to a processor or acquirer. You may need separate processing and acquiring agreements. A payment service provider may bundle the gateway, transaction processing and merchant acquiring into one service, although the contractual scope varies.

Compare equivalent packages: a gateway-only quotation should not be assessed against a bundled service without including the separate processing and acquiring costs. Turn your brief into a shortlist checklist, marking each requirement as essential or optional. Essentials might include AED presentment, GBP settlement, recurring payments, a supported platform integration and a defined payout timetable. Ask each provider to confirm coverage against the same checklist before progressing to merchant eligibility and UAE market support.

Check merchant eligibility and UAE market support

Separate two possible operating models before comparing providers. A UK entity can sell to customers in the UAE through a UK merchant account if its provider supports UAE-issued payment methods and the relevant currencies. Alternatively, the group can contract through a UAE entity to seek local acquiring and local settlement. These models have different onboarding, pricing, foreign-exchange, settlement and regulatory implications, and support for UAE customers does not automatically mean that a provider will onboard a UAE merchant entity.

For a UAE merchant account, confirm the provider's accepted legal forms and licensing requirements. Providers may require a UAE-incorporated entity or branch, a valid trade licence or freelancer permit, an active local bank account and a physical business address. The permitted structures, free-zone coverage and bank-account rules vary. Do not incorporate or open an account on the assumption that every international provider will accept the resulting entity.

A UK merchant using cross-border acquiring should verify that its current legal entity, business model and goods or services are eligible. Ask whether UAE cards can be processed in AED, whether the transaction is treated as domestic or cross-border, and which entity appears in the contract and on the customer's statement. Local acquiring can improve acceptance or cost in some cases, but it may require a separate merchant account, local establishment and additional operational substance.

Prepare a complete KYB pack before requesting pricing. It commonly includes incorporation and trade-licence documents, constitutional documents, ownership and control information, identification for directors, authorised representatives and ultimate beneficial owners, proof of address and bank-account evidence. The provider will also assess the website or app, product descriptions, pricing, fulfilment, delivery countries, refund policy, customer support, expected volume, average order value and chargeback exposure. Regulated or higher-risk products may require sector-specific permissions and enhanced due diligence.

Confirm underwriting and onboarding lead times, outstanding conditions and the final approval required to process live payments; preliminary eligibility confirmation is not final approval. Ask whether new countries, product changes or significant volume increases trigger renewed underwriting and how this could affect launch or expansion timelines.

Check the provider's UAE regulatory position independently. Merchant acquiring, payment aggregation and other retail payment services fall within the Central Bank of the UAE framework. Identify each entity's role and the authorisation or other legal basis covering its activities. A purely technical gateway that never takes possession of funds may qualify for an exclusion, but an acquiring partnership alone does not establish regulatory compliance. Verify any claimed exclusion or agency arrangement, and confirm which party holds or settles funds and handles complaints and payment-service obligations.

Market support must be tested at transaction level. Request an availability matrix by merchant country, shopper country, currency, channel and payment method. A method shown on a global product page may still require local approval, a particular merchant entity or a separate commercial agreement. Confirm recurring-payment support, refunds, partial captures, chargebacks, tokenisation and 3-D Secure authentication for the exact UAE route.

Use a limited pilot before committing to a local entity or long-term volume. Measure UAE authorisation rate, checkout completion, all-in processing and FX cost, payout timing, disputes and manual exceptions. The preferred route should meet the business's current eligibility requirements and remain viable if UAE volume, local payment demand or settlement needs increase.

Evaluate checkout, payment methods and integrations

Evaluate the customer experience and the technical operating model together. A checkout that is quick to launch may provide less control, while a fully customised integration increases engineering, testing and PCI DSS responsibilities. Select the simplest model that supports the required UAE payment methods, branding, subscriptions and finance controls.

Localise the checkout for UAE shoppers. Test AED pricing, Arabic and English presentation where appropriate, right-to-left layout, local address and telephone formats, mobile performance and clear delivery, tax and refund information. Keep the final amount and currency unambiguous. Customers may incur issuer conversion fees when the charge currency differs from their card currency, or cross-border fees even when currencies match. Conversion between the charge and merchant settlement currencies is a separate merchant cost and does not itself create a customer FX charge.

Build the payment-method list from customer evidence, not a provider's global catalogue. Confirm major card coverage and evaluate digital wallets, buy-now-pay-later services, regional wallets or bank-based methods only where they are available for the merchant entity, UAE shoppers, channel and transaction currency. Check refunds, partial refunds, disputes, recurring payments and settlement for each method. A payment method that supports one-off web purchases may not support subscriptions, delayed capture or marketplace flows.

The following wallet examples provide a starting point for UK and UAE merchant accounts, not an exhaustive list. Confirm account approval, supported cards, AED acceptance and integration requirements before enabling them.

For cards, confirm 3-D Secure authentication, challenge handling, stored credentials and the distinction between customer-initiated and merchant-initiated transactions. Subscription businesses should test initial authentication, token creation, scheduled renewal, failed-payment recovery, card updates, cancellation and refund. Establish who owns the token and whether it can be migrated if the provider changes.

Review the integration as a stateful payment workflow rather than a single API call. Requests that create or capture money should support idempotency so a timeout cannot generate a duplicate charge. Webhooks should be authenticated, retained, deduplicated and processed safely when delayed or delivered out of order. Store both the internal order or subscription ID and the provider's payment, capture, refund and dispute identifiers.

• Confirm sandbox coverage for successful, declined, challenged, timed-out and duplicated requests.
• Test authorisation, manual and automatic capture, cancellation, full and partial refunds and dispute events. Confirm authorisation validity, capture deadlines and support for multiple partial captures against fulfilment timelines.
• Review API versioning, deprecation notice, rate limits, uptime reporting and production support.
• Check software-development kits and plugins against the business's current platform and release process.
• Require role-based access, separate test and production credentials, secret rotation and auditable configuration changes.

Finance integration is equally important. The API and reports should expose gross amount, currency, fees, conversion, settlement batch, reserve, refund, dispute and payout references. Confirm that these fields can be mapped to the accounting or ERP system and reconciled from order to provider settlement and bank receipt.

Run the shortlisted checkout on representative devices, browsers and network conditions with UAE test users. Test keyboard navigation, screen-reader support and accessible error messages and authentication challenges. Compare completion rate, authentication success, payment-method display, error clarity and support effort. The chosen integration should improve conversion without creating payment states that engineering, customer service and finance cannot explain or reconcile.

Calculate total costs and cash-flow impact

Compare providers on the cost of a successful, settled transaction rather than the advertised card rate. Ask for a written quote based on the same countries, cards, currencies, average order values, monthly volumes, refund rates and chargeback profile. Separate costs charged by the gateway or PSP from card-scheme, acquiring, foreign-exchange and banking costs so apparently different pricing models can be normalised. Blended pricing combines specified processing components into one rate; interchange++ separates interchange, scheme fees and the provider's markup. Do not add costs already included in a bundled rate.

Distinguish fees for issuing a refund from original processing and FX fees that are not returned. A provider may charge no additional refund fee while retaining those original fees; check the applicable fee schedule.

Model the complete currency path. A UAE customer may pay in AED while the UK business prices, reports or settles in GBP. Confirm the transaction currency shown at checkout, the acquiring currency, the currencies in which the provider can settle, the rate source and markup, and whether another bank conversion occurs after payout. If a UAE entity will receive AED locally, compare that structure with cross-border settlement to the UK, including the legal, tax, banking and administrative consequences.

Settlement timing can matter more than a small fee difference. Record the delay from capture to available balance and from available balance to the bank, including cut-off times, weekends and public holidays in both markets. Ask whether settlement is gross or net of fees, refunds and disputes. Identify rolling reserves, delayed settlement, minimum payout thresholds, negative-balance rules and the circumstances in which the provider may withhold funds.

Translate timing into working-capital cost. Forecast daily sales, provider receivables, refunds, chargebacks, reserves and bank receipts by currency. A longer settlement cycle increases the cash needed to fund inventory, fulfilment, tax and customer refunds. Conversely, more frequent payouts may carry a fee or create additional bank and reconciliation entries. Use the business's actual funding rate to value the difference. Reserve principal ties up cash but is not itself a fee; count its funding cost and any administration charge separately.

For illustration, assume 100 payments worth £10,000 in GBP equivalent, a processing rate of 2% plus £0.20 per payment, and a 1% FX charge on the full value. Processing costs £220 and FX costs £100. A £1,000 reserve held for 30 days at a 12% annual funding rate costs approximately £9.86 to fund, using a 365-day year. These components total £329.86, excluding other fees and losses; the £1,000 reserve remains separately recorded as cash withheld.

Calculate unit economics by market and method, using consistent periods, transaction cohorts and currencies:

• All-in payment cost equals processing and acquiring fees, FX, fraud-management and dispute-handling fees, internal operating costs, settlement and reserve funding costs, plus expected fraud and chargeback losses net of recoveries. Count each fee or loss only once.
• Cost per successful payment divides the cohort's all-in payment cost by its completed, non-reversed transactions rather than attempts.
• Net payment contribution equals the cohort's gross profit before payment costs and the losses listed above, expressed as a monetary amount, minus all-in payment cost. Do not deduct those losses again.

Run base, downside and growth cases. Vary volume, average order value, international-card mix, approval rate, refund rate, FX margin and reserve percentage. Do not count extra approved revenue as profit; apply the relevant contribution margin. Include contract tier changes and minimum commitments so the model shows where scale improves or worsens economics.

Finally, test the quote against sample settlement and fee reports. Finance should be able to trace an order through authorisation, capture, fee, conversion, settlement, refund and dispute entries. A low headline price is not a saving if unexplained deductions, slow payouts or manual reconciliation consume the difference.

Assess security, regulatory responsibilities and reliability

Map the parties and money flow before relying on a security badge or global brand. Identify the merchant entity, checkout operator, gateway, processor, acquirer, settlement entity and any subcontractor. A UK company selling into the UAE does not automatically become a UAE payment service provider, but the provider that performs merchant acquiring, payment aggregation or another regulated retail payment service in the UAE may require authorisation under the Central Bank of the UAE framework. Verify the relevant licensed entity and service scope. For UK-regulated payment services, check the contracting provider and its relevant permissions on the FCA Financial Services Register. Obtain legal advice for the proposed UK or UAE entity structure.

For relevant electronic payments within the UK regime, payment service providers must apply Strong Customer Authentication unless a valid exemption is used. The merchant's integration still needs to pass the required data, present challenges and handle soft declines correctly. Confirm how the provider applies authentication to UK-issued cards and how UAE and other cross-border transactions are treated. Test recurring, merchant-initiated and out-of-session flows rather than assuming one authentication rule covers every transaction.

PCI DSS responsibilities depend on how card data enters the system. A redirect, hosted payment page or tokenised component can reduce the merchant's scope, but outsourcing does not remove every obligation. Confirm the applicable validation route with the acquirer. The specific SAQ A eligibility criterion requiring confirmation that the site is not susceptible to script attacks applies to embedded payment forms, not redirect-only implementations. Match script-security controls, supporting evidence and merchant/provider responsibilities to the actual integration and applicable assessment requirements.

Check how funds are protected if the provider becomes insolvent: identify which balances are safeguarded, the responsible entity and the safeguarding arrangement. Safeguarding at a UK non-bank payment provider is not FSCS protection and does not guarantee immediate or full recovery.

Payment data can include personal information. Define whether each party is a controller or processor, put the required written terms in place and limit access and retention. Review international transfers from the UK and the locations of support, fraud and analytics teams. Where a restricted transfer relies on appropriate safeguards, consider the UK IDTA or EU Standard Contractual Clauses with the UK Addendum, and complete the required transfer risk assessment, also termed a data protection test. UAE federal or financial-free-zone data rules may also apply depending on the entity, customer and processing location, so confirm the applicable regime rather than assuming UK GDPR is the only framework.

Security controls must work through the whole lifecycle. Use least-privilege credentials, separate test and production, rotate secrets, verify webhook signatures, make API requests idempotent and preserve an immutable audit trail. Protect bank-detail and refund changes with strong authentication and approval. Reconcile provider records to orders and bank receipts so a cyber or processing incident is visible financially.

Reliability should be tested, not inferred from an annual uptime percentage. Review planned-maintenance exclusions, regional dependencies and the provider's definition of availability. Test timeouts, duplicate callbacks, partial captures, failed authentication, delayed webhooks, refunds during an outage and recovery after settlement files are missed. Define who may switch routes or pause checkout and how duplicate charges are prevented.

Contracts should allocate responsibility for fraud screening, SCA, disputes, data incidents, regulatory change, customer communication, business continuity and exit. Require prompt incident notice and usable transaction exports. The final assessment should combine legal review, technical testing and operational evidence; certification alone cannot prove that the business's specific implementation is compliant or resilient.

Compare Stripe, Adyen and Checkout.com

Stripe, Adyen and Checkout.com can all support international online payments, but they differ in onboarding model, UAE footprint, pricing presentation and operational fit. Compare the service available to the specific UK or UAE legal entity, not the provider's global feature list. Product availability, payment methods, settlement currencies and commercial terms can vary by account country, industry and risk profile.

Stripe may suit a business that values a comparatively accessible onboarding path, extensive developer documentation and published standard pricing. A UK account can accept supported card payments in AED with conversion to GBP settlement, while a UAE account supports local AED payouts. Apple Pay and Google Pay are available in both markets, subject to integration requirements. Confirm any additional settlement currencies and bank-account requirements separately.

As checked on 5 November 2026, Stripe's standard UK rate for UAE-issued cards is 3.15% plus 20p, with an additional 2% where currency conversion is required. Its standard UAE rate is 2.9% plus AED1 for domestic cards, with an additional 1% for international cards and 1% where currency conversion is required. These are published processing rates, not all-in quotations; custom pricing and additional product fees may differ.

Adyen should be assessed where the business needs local UAE acquiring or settlement capability, international scale or unified online and in-person commerce. Its single-platform model can reduce fragmentation across channels. Adyen lists GBP payouts and local AED payouts, with AED requiring a local bank account. Confirm the settlement configuration available to the contracting entity, minimum commercial commitments, supported payment methods for its merchant category and the service model offered at its volume.

Checkout.com is relevant for businesses seeking a provider with a substantial regional presence, direct UAE acquiring and detailed transaction-level reporting. Its published UAE country terms require the contracting company not to be a consumer, micro-enterprise, sole trader or charity. A UK group should therefore confirm whether it contracts through the UK or UAE entity and whether a UAE subsidiary is required for the intended local setup. Apple Pay and Google Pay are listed for both UK and UAE merchants; AED presentment, GBP or AED settlement, pricing, reserves and payout timing should be confirmed in the proposed account configuration and quotation.

Do not select a provider from headline currency or payment-method counts. Ask each one to confirm, in writing, the eligible merchant entity, permitted business model, UAE acquiring route, AED presentment and settlement, required bank account, payment methods, recurring-payment support, payout timetable, reserve policy, full fees and support response times. Compare UK-account cross-border acceptance with UAE-account local processing using the same transaction mix, including FX and local entity costs. The strongest option is the provider whose approved configuration delivers the required UAE coverage and cash flow with acceptable total cost and implementation risk.

Validate the shortlist and make the final decision

Turn the shortlist into a controlled selection process. Give every provider the same fact pack: UK and proposed UAE entities, products, sales channels, customer countries, currencies, average order value, monthly and peak volume, recurring-payment model, refund and dispute history, required payment methods and expected launch dates. Ask the provider to confirm eligibility before investing in a full integration.

Request a written solution map showing the contracting entity, gateway, processor, acquirer, settlement bank, fraud service and any subcontractors. The response should distinguish UAE local acquiring from cross-border acceptance and state whether a UAE legal entity, trade licence and local bank account are required. Obtain a complete commercial schedule covering processing, scheme or interchange, foreign exchange, refunds, disputes, platform fees, minimum commitments, reserves, payout charges and termination assistance.

Run a proof of concept using the intended checkout design. Test card payments in GBP and AED where supported, Strong Customer Authentication, saved credentials, subscriptions, partial and full capture, refunds, disputes, timeouts, duplicate callbacks and failed settlement. Confirm that internal order IDs remain linked to provider transaction, fee and payout references. A successful authorisation alone does not prove that finance can reconcile the service.

Model costs with a representative transaction file rather than a single average rate. Calculate the provider charge, acquiring and scheme costs, foreign exchange, dispute expense, reserve funding and internal operating cost for domestic UK cards, UAE cards and other international cards. Compare settlement timing and currency conversion because a lower processing rate can be offset by slower payouts or avoidable FX.

Treat merchant eligibility, required settlement support and essential compliance requirements as mandatory pass/fail gates. Only score providers that pass them; a high overall score cannot compensate for a failed essential requirement. Agree weights before reviewing final pricing, covering total cost, checkout and payment methods, authorisation performance, settlement and reconciliation, implementation effort, reliability, support and portability. Record any assumption that has not been contractually confirmed as a risk rather than awarding full credit.

Complete legal, security, data-protection and finance reviews of the proposed contract and money flow. Verify the relevant regulated entities independently, confirm PCI DSS responsibilities, review data locations and subprocessors, and understand reserves, termination rights and token portability. Obtain executive approval for material deviations from negotiable requirements.

Choose a provider subject to explicit go-live conditions, then pilot a limited channel or traffic share. Define a minimum transaction sample, representative customer and card mix, and measurement period before starting. Set acceptance, fraud, cost, payout and reconciliation thresholds, with named owners and a rollback plan. Expand only after the agreed pilot criteria are met, at least one representative settlement cycle is complete and the main refund and exception flows work as designed. One settlement cycle validates basic payout functionality, not long-term fraud or dispute performance.

After launch, review approval rates, realised costs, disputes and payout performance weekly during rollout and monthly thereafter. Agree escalation triggers, such as sustained approval-rate declines, costs above budget or overdue payouts, with deadlines for corrective action and criteria for reconsidering the provider.