Worldpay
Connect Worldpay to DEUNA, configure payment notifications, and verify the complete payment flow before going live.
On this page
Connect your Worldpay account in DEUNA Admin, then configure Worldpay to send transaction updates to DEUNA. Both steps matter: saving a connection adds your credentials, while notifications let DEUNA reconcile payment outcomes after processing.
Before you start#
Use this guide if you manage payment connections for your merchant or store. You need access to Connections in DEUNA Admin and to the Worldpay Merchant Administration Interface (MAI). Ask your account administrator for access if either is unavailable.
Confirm your account and credentials
Have the following ready for the environment you are configuring:
- An enabled Worldpay account and its Merchant ID.
- Worldpay XML connection credentials, including the values DEUNA labels Private Key and Public Key.
- Worldpay MAI login credentials to configure notifications.
- Access to the merchant or store where the DEUNA connection will be created.
Request these credentials from your Worldpay representative. Confirm that the credentials support the selected operation and environment; MAI login credentials and XML connection credentials serve different purposes. Enter connection credentials only in DEUNA Admin and keep them out of checkout code, screenshots, and support messages.
Confirm payment availability
Check the Worldpay capability catalog for your market, currency, card brands, and required operations. Availability depends on the account and connection; the feature descriptions below do not imply that every feature is enabled for every merchant.
Confirm local acquiring and legal-entity requirements with Worldpay for each country. If you plan to use 3-D Secure, installments, wallets, or multiple partial operations, agree on the required setup with DEUNA and Worldpay before testing.
Accepted currencies
ARS · BRL · EUR · GBP · JPY · MXN · USD
Currency availability depends on the Worldpay merchant account and connection. Confirm the currencies enabled for your account before testing.
1. Connect Worldpay in DEUNA#
Open DEUNA Admin, select the intended merchant or store, and go to Connections. Under Discover, search for Worldpay and select Connect.
The preview below follows discovery, credential configuration, and the saved connection. Its controls illustrate the setup; configure your actual account in DEUNA Admin.
Enter the connection settings
- Choose a recognizable connection Name so your team can distinguish it from other accounts or environments.
- Select the currency when requested and enter the Worldpay credentials issued for that connection.
- Choose Purchase to authorize and request capture in one payment flow, or Authorization if you will send a separate capture request later.
- Configure 3-D Secure only after confirming the supported authentication flow with DEUNA. See 3-D Secure handling before implementing checkout.
- Select Connect, then verify that Worldpay appears under Active Connections.
| DEUNA field | Value to enter |
|---|---|
| Merchant ID | The Worldpay Merchant ID issued for the connection. |
| Private Key | The Worldpay XML private key. |
| Public Key | The Worldpay XML public password. |
For airline payments, also complete the issuer fields required by your setup: Issuer Name, Issuer Address1, Issuer Postal Code, Issuer City, and Issuer Country Code. These identify the airline issuing the ticket; use a two-letter ISO country code for its country. They do not replace the passenger, ticket, and itinerary data sent with a payment.
A connection under Active Connections confirms that it was saved. Continue with Worldpay notifications and a payment test before treating the integration as ready.
2. Configure Worldpay notifications#
Worldpay sends provider notifications to DEUNA so payment state can be updated after authorization, capture, cancellation, or refund processing. Your backend receives status updates through a separate DEUNA webhook configuration. Configure both notification paths when your integration needs asynchronous updates.
See DEUNA payment status notifications for the merchant-side setup.
Set the notification address
In Worldpay MAI, open Integration → Merchant Channel. In the http row, set Active to Yes, set Method to POST, and enter the notification address for the matching environment.
| Environment | Worldpay notification address |
|---|---|
| Sandbox | https://api.sandbox.deuna.io/transactions/webhooks/payconnect/payment-processors/worldpay |
| Production | https://api.deuna.io/transactions/webhooks/payconnect/payment-processors/worldpay |
Confirm the address with DEUNA for your connection before saving it. Worldpay calls this address; your application does not call it to create a payment or retrieve its status.
Enable transaction events
In Merchant Channel Events (Production), select the following events in the http row. Keep the event identifiers exactly as shown.
| Payment stage | Events to enable |
|---|---|
| Authorization and errors | AUTHORIZED, REFUSED, ERROR |
| Capture | CAPTURED, CAPTURE_FAILED |
| Refund | SENT_FOR_REFUND, REFUNDED, REFUNDED_BY_MERCHANT, REFUND_REVERSED, REFUND_FAILED |
| Cancellation and reversal | SHOPPER_CANCELLED, CANCELLED, REVERSED, VOIDED, CANCEL_FAILED |
3. Test the complete payment flow#
Use sandbox credentials and the payment flow supported by your connection. A successful connection test must show both the requested payment operation and its resulting state.
Capture, refund, and void requests can remain pending while Worldpay processes them. An accepted request, browser return, or timeout does not establish the final outcome. Use the latest order status and configured DEUNA webhooks to reconcile the original payment before retrying or marking an operation complete.
See Payment Workflow & Statuses for the payment lifecycle and DEUNA webhooks for backend notifications.
If the expected result does not arrive
- If the connection cannot be saved, check the selected account, environment, operation, and XML credentials with Worldpay.
- If a payment remains pending, check the Worldpay notification address,
POSTmethod, and selectedhttpevents before retrying the original operation. - If DEUNA has the result but your backend does not, check your DEUNA webhook delivery setup.
When escalating to DEUNA, include the environment, order reference, attempted operation, and observed status. Do not include credentials or full card data.
Move to production
Repeat the connection and notification setup with production credentials and the production notification address. Confirm the enabled operations and any certification requirements with DEUNA and Worldpay, then verify the production payment flow before accepting customer traffic.
Supported operations#
Use this reference to choose the payment flow to configure and test. Confirm each feature against the Worldpay capability catalog and your account setup.
| Feature | What it does |
|---|---|
| Authorization | Reserves the requested amount on the cardholder's account without capturing the funds. A separate capture is needed to collect the payment. |
| Capture | Collects funds from a previously authorized payment. A full capture collects the available authorized amount. |
| Purchase | Authorizes and requests capture in one payment flow, without a separate merchant capture request. |
| Partial capture | Captures a portion of the previously authorized amount. Multiple captures require separate enablement. |
| Multiple partial captures | Allows several captures against one authorization, without exceeding the available authorized balance. The operating mode and authorization validity determine how and when captures can be submitted. |
| Void | Cancels an uncaptured authorization and requests release of the remaining reserved amount. It does not refund funds that have already been captured. |
| Refunds | Returns captured funds to the cardholder. A full refund returns the remaining refundable amount. |
| Partial refunds | Returns a portion of the captured amount to the cardholder. |
| Multiple partial refunds | Allows several refunds against the same captured payment when enabled. The cumulative refunded amount cannot exceed the confirmed captured amount. |
| Issuer installments | Allows eligible cardholders to split a purchase into installments under the terms supported by the issuer, acquirer, and merchant connection. |
| Digital wallets | Supports Apple Pay and Google Pay payments where the wallet is available and enabled for the Worldpay connection. |
| 3-D Secure MPI | DEUNA manages 3-D Secure authentication, including browser checks and an issuer challenge when required. Authentication can also finish without a visible challenge. |
| Airline data | Transmits supported airline transaction information, including passenger, ticket, and itinerary details. Supply the airline data required for your payment flow. |
Multiple captures and refunds
Partial capture and refund support does not automatically enable multiple operations. Confirm the operating mode and per-order limits with your DEUNA Technical Account Manager (TAM) and Worldpay.
Online multiple captures are sent to Worldpay individually and do not use a DEUNA capture cutoff. Worldpay's authorization validity and capture limits still apply. A configured DEUNA capture period applies to buffered (offline) captures, where DEUNA submits an accumulated amount when the sequence closes. See Multiple Partial Captures for the mode-specific rules.
Multiple refunds must stay within the confirmed refundable balance. If your connection uses DEUNA-managed buffering, a partial refund request records intent until the accumulated refund is submitted; it does not mean the customer has received the funds. See Multiple Partial Refunds for the buffered flow.
Handle 3-D Secure authentication
When authentication requires a browser action, DEUNA returns the hosted experience through the payment's next action. Your integration presents it using the supported widget, iframe, or redirect flow. Browser checks can complete without an issuer challenge; the cardholder sees a challenge only when required.
Successful authentication does not guarantee an approved or captured payment. Confirm the final payment status after DEUNA completes any remaining authorization or processing. Follow the 3DS purchase flow for next-action handling and recovery.
Wallets and installments
Complete the separate Apple Pay or Google Pay setup before offering a wallet at checkout. Wallet availability depends on the market and connection.
For issuer installments, offer only terms eligible for the card, acquirer, and connection. See Installments for campaign setup and how to submit the customer's selected option.
Regional and airline requirements#
Airline payments
Supply the airline data required by your flow in the authorization or capture request. For an airline_order, the required airline data must be present in at least one of those requests. Confirm the expected passenger, ticket, and itinerary information for your connection before testing.
Capture and refund limits
Capture before the authorization expires. Confirm the permitted capture window with Worldpay and DEUNA; a DEUNA batching cutoff does not extend the issuer's authorization. Refunds cannot exceed the confirmed captured amount. Follow the operating-mode rules before submitting more than one partial operation.
Local transactions in Argentina
For transactions acquired locally by Worldpay in Argentina, include the buyer's postal code, province, and country in the authorization request:
billing_address.zipcodebilling_address.state_namebilling_address.country_code
Worldpay uses this information for provincial tax withholding. If it is absent, withholding is based on the merchant's location. Send either the ISO province code or the COMARB code in billing_address.state_name, not both.
Argentina province codes
| Province code COMARB | Province code ISO | Province Name |
|---|---|---|
| 901 | AR-C | CABA |
| 909 | AR-P | Formosa |
| 919 | AR-D | San Luis |
| 908 | AR-E | Entre Rios |
| 911 | AR-L | La Pampa |
| 917 | AR-A | Salta |
| 906 | AR-H | Chaco |
| 907 | AR-U | Chubut |
| 910 | AR-Y | Jujuy |
| 920 | AR-Z | Santa Cruz |
| 903 | AR-K | Catamarca |
| 904 | AR-X | Cordoba |
| 912 | AR-F | La Rioja |
| 922 | AR-G | Santiago del Estero |
| 918 | AR-J | San Juan |
| 913 | AR-M | Mendoza |
| 914 | AR-N | Misiones |
| 915 | AR-Q | Neuquén |
| 916 | AR-R | Rio Negro |
| 923 | AR-V | Tierra del Fuego |
| 902 | AR-B | Buenos Aires |
| 921 | AR-S | Santa Fe |
| 924 | AR-T | Tucumán |
| 905 | AR-W | Corrientes |
Next steps#
- Payment strategies: configure when the connected account is used.
- 3DS purchase flow: handle browser actions, authentication results, and recovery.
- Payment status notifications: keep your backend aligned with DEUNA.