Wrong guide? If you have a Vantiv/Litle Merchant ID, use the WorldPay US eCommerce (Vantiv) directions instead.

WorldPay WPG integrates with Recurly for global payment processing — covering credit cards, Apple Pay, Google Pay, SEPA, ACH, and local LATAM card brands including Tarjeta Naranja. LATAM processing is handled via Ebanx (or dLocal for existing merchants). This guide covers WorldPay account configuration, Recurly setup, and regional configuration for Argentina, SEPA, and ACH.

Available on all Recurly plans

1Definition 2Key details 3Credentials 4Configuration 5FAQs

Prerequisites

Established commercial agreements with WorldPay and Ebanx to facilitate local transactions. WorldPay supports dLocal for existing merchants only — new merchants should work with WorldPay on an Ebanx solution. Contact [email protected] for introductions if needed.
For Argentinian processing — An active Recurly account with ARS currency enabled, a WorldPay gateway configured for ARS, and a WorldPay merchant account capable of Zero Dollar Authorizations (ZDA).
For TLID storage — WorldPay does not return TLIDs by default. Contact WorldPay to enable TLID return for Mastercard transactions before using this feature.
For SEPA (Direct Debit) — An active Recurly account with EUR currency enabled, a WorldPay gateway configured for SEPA/EUR with mandate tokenization support.
For ACH (Direct Debit) — An active Recurly account with USD currency enabled and WorldPay NACHA pre-verification enabled for ACH/USD compliance.

Limitations

Tarjeta Naranja does not support ZDA — Verifications for this card brand are processed with a $1.00 charge instead.
WorldPay SEPA does not support free-trial subscriptions or verification transactions — SEPA billing info updates must occur within the context of processing a transaction.
Tax ID required for many LATAM transactions — Submit a tax ID (e.g., CUIT) with each transaction. If using CUIT, CPF, or CNPJ, specify the type via API using tax_identifier_type. For all other tax ID types, send the value without a type.
Sales tax may be required — Certain regions require sales tax on transactions. Confirm requirements with WorldPay and configure sales tax in your Recurly site. See sales tax documentation.
Prohibited businesses — Check WorldPay's prohibited business types to confirm your business qualifies.

Definition

WorldPay WPG is a global payment gateway that processes credit cards, Apple Pay, Google Pay, SEPA direct debit, ACH, and local LATAM card brands through Recurly. It supports 50+ currencies and regional specialization in the UK/EU and Latin America via partnerships with Ebanx and dLocal. WorldPay processes voids and refunds asynchronously — there is a small chance WorldPay may reject a void or refund request 5 to 45 minutes after submission.

Key details

Feature	Details
Services that work with Recurly	Payment processing, recurring subscriptions, MOTO processing. LATAM support via Ebanx and dLocal (existing merchants only).
Supported operations	Verify, Purchase, Void, Refund (online and offline)
Supported payment types	Credit cards, local card brands (Tarjeta Naranja), Apple Pay, Google Pay, Direct Debit: ACH and SEPA
Supported card brands	Visa, Mastercard, Discover, Union Pay, JCB, Diners Club, American Express (most currencies). Tarjeta Naranja on ARS only.
Gateway-specific 3DS2 supported	Yes — depends on WorldPay configuration. Recurly.js required in certain cases.
Card on file supported	Yes
Regions	Global, with focus on UK/EU, Argentina, Brazil, Chile, Colombia, Costa Rica, El Salvador, Guatemala, Mexico, Ecuador, Panama, Paraguay, Uruguay, Honduras, and Peru.
Currencies	ARS (Visa, MC, Amex, Discover, JCB, Diners Club, Tarjeta Naranja) · USD (ACH) · EUR (SEPA) · All others: ANG, AUD, BRL, CAD, CHF, CLP, CNY, COP, CZK, DKK, GBP, HKD, HRK, HUF, ILS, INR, ISK, JPY, KRW, KES, MXN, MYR, NOK, NZD, PHP, PLN, PYG, RUB, SAR, SEK, SGD, THB, TRY, TWD, UYU, VEF, ZAR, and more.

Online refunds WorldPay has enabled Online Refund Authorization, which allows banks to decline refund attempts in real time. If a refund is declined, resubmit it or resolve it with your customer directly. Review your Refund Invoice settings to avoid unintended behavior. See handling failed refunds for details.

Tip Before going live, see Recurly's guide to testing gateway configurations to verify your payment setup is working correctly.

Credentials

WorldPay WPG requires XML credentials from WorldPay. For SEPA, you'll also need additional information for mandate creation.

Billing address — Recurly submits billing address data to WorldPay whenever available. WorldPay requires four fields: Address line 1, City, Postal code, and Country. If any are missing, Recurly uses defaults: city = "city," address line 1 = "address," and country derived from the customer's IP address. If country can't be determined, no billing address is submitted.

Voids and refunds — WorldPay processes void ("cancel") and refund order modifications asynchronously. There is a small chance WorldPay may reject a void or refund request between 5 and 45 minutes after receiving it.

Tax ID reference For technical details on sending tax IDs such as CUIT, CPF, or CNPJ in your billing info block, see the Recurly developer documentation.

Configuring WorldPay with Recurly

Step 1: Configure your WorldPay merchant account

Contact WorldPay to configure your account

Reach out to the WorldPay integration team to set up your merchant account for processing and transaction updates.

Allow-list Recurly's IP addresses

In the WorldPay portal, authorize Recurly's IP addresses. See the IP allowlist documentation for the full list.

Set Capture delay to 1-Day

In the WorldPay platform, set the Capture delay setting to 1-Day.

Configure callback URLs

Add your Recurly callback URL in WorldPay for event notifications. Enable all event types — Recurly will use what it needs for asynchronous actions such as invoice updates and Direct Debit status updates.

Standard: https://callbacks.recurly.com/worldpay/YOUR_SUBDOMAIN
EU data centers: https://callbacks.eu.recurly.com/worldpay/YOUR_SUBDOMAIN

Enable MOTO permissions (if applicable)

If you're processing MOTO transactions, contact your WorldPay representative to enable the dynamicInteractionType parameter on your account. Without this, MOTO transactions will fail.

Enable local currencies and Zero Dollar Authorizations

Confirm your WorldPay account supports the local currencies you plan to accept and that ZDA is enabled where needed. Note: Tarjeta Naranja does not support ZDA — verifications for this card brand use a $1.00 charge instead.

Step 2: Configure WorldPay in Recurly

Add the gateway

In Recurly, go to Payment Gateways → Add Payment Gateway and select WorldPay.

Enter your credentials

Input your WorldPay Merchant Code, XML Username, and XML Password. These are not your WorldPay account login credentials.

Configure SEPA (if applicable)

Enter your WorldPay Mandate Prefix and Merchant ID for SEPA and ensure EUR is enabled as an accepted currency.

Configure 3DS (if applicable)

If using 3D Secure, enter your Issuer ID, Unit ID, HMAC Key, and Challenge URL.

Set currencies and card types

Select the currencies and card brands you plan to accept. Optionally, designate which card types should use Zero Dollar Authorizations.

Save and test

Click Add Payment Gateway, then use the Test Configuration option to confirm Recurly can communicate with WorldPay successfully.

Enable Direct Debit retries (SEPA/ACH)

In Recurly, go to Configuration → Payment Settings and enable Direct Debit retries so failed SEPA and ACH payments due to insufficient funds are retried automatically.

Step 3: Enable global and regional currencies

Enable currencies in Recurly

In Recurly, go to Configuration → Currencies and enable the currencies relevant to your markets — ARS for Argentina, EUR for SEPA, USD for ACH, and any other applicable currencies.

Enable Tarjeta Naranja (ARS/Argentina)

In your WorldPay gateway settings in Recurly, toggle on Tarjeta Naranja as an accepted card brand. This card is available on ARS currency only.

Enable ACH (if applicable)

Confirm USD is enabled in Recurly, at WorldPay, and in your gateway configuration. Verify that NACHA pre-verification and fraud flows are enabled at WorldPay.

Step 4: Configure tax ID collection (LATAM)

For Argentine and other LATAM transactions, collect the customer's tax ID (e.g., CUIT) during the initial transaction. Include the tax_identifier and tax_identifier_type fields in your transaction payload. If using a tax ID type other than CUIT, CPF, or CNPJ, send the value without a type definition.

Step 5: Test and go live

Test the full setup rigorously — including regional payment methods, tax ID submission, and any Direct Debit flows — before switching to production.

FAQs

Why is my WorldPay refund failing?

WorldPay supports Online Refund Authorization, which allows banks to decline refund attempts in real time. This became standard across all WorldPay accounts in May 2025. A refund can be declined if the customer's account is closed or the bank doesn't approve the refund. If this happens, coordinate with your customer to return funds through another method.

Why is my ACH transaction failing?

ACH bank accounts go through a NACHA-required fraud and accuracy check before being added to Recurly. If a customer is updating a bank account on file or signing up for a subscription and the transaction fails, a fraud check at WorldPay likely didn't pass — contact WorldPay for details and have the customer provide a different payment method.

ACH transactions that have been scheduled or approved can also fail later due to bank processing times. For failures due to insufficient funds or closed accounts, Recurly can retry automatically when you enable Direct Debit retries in Payment Settings. Recurly retries ACH and SEPA payments only when the failure reason is insufficient funds.