Skip to main content
Talk to an expert
Worldpay logo

Worldpay payment integration for ecommerce

Payment authorisation, capture and refunds governed end-to-end iWeb connects Worldpay into your commerce and ERP estate with clear responsibility for auth timing, refund workflow, chargeback investigation and settlement reconciliation. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: payment connector, checkout plugin, app, extension.

WorldpayiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Worldpay integration gives you.

Payment failures visible and owned

Authorisation failures, 3DS timeouts and capture rejections are logged with clear action: retry, escalate to customer service, or contact cardholder. No silent payment failures.

Refunds and chargebacks reconcile to orders

Full and partial refunds initiated from customer service or returns workflows are recorded correctly in the ERP as credit notes. Chargebacks are matched to original orders and investigated in a named queue.

Tokenised cards work across the estate

Saved cards reused after replatform, subscription renewal and device change without unexpected re-auth prompts or approval-rate regressions.

Bank reconciliation runs cleanly

Daily settlement files from Worldpay match captured transactions in the ERP. Unmatched or late items surface as exceptions for finance investigation.

3DS and SCA compliance is measurable

You know your approval rate, liability shift rate and exemption usage by region. Fraud rules and step-up auth are monitored against policy and benchmarks.

02 · When it's worth it

Where a Worldpay integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Authorisation, capture and settlement routing through Worldpay
Refund and chargeback management from commerce and customer service
Payment reconciliation against ERP ledgers and bank statements
Tokenisation and saved-card handling across replatforms
Split payment and deferred capture for high-value orders
3DS / SCA compliance and MFA workflow integration
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Capture timing mismatch

Worldpay by default captures immediately on authorisation. If your order flow requires deferred capture (e.g., after picking or for dropship orders), the timing between commerce and ERP must be explicitly designed and monitored.

3DS and SCA handling variability

3D Secure and Strong Customer Authentication rules vary by card, issuer and region. Platform defaults may not match your liability and approval targets; fraud velocity rules and exemption handling need review against your risk appetite.

Tokenisation and payment method limits

Saved-card handling and re-use across replatforms, device changes and subscription renewal is not automatic. Token lifecycle, expiry and fallback to new auth must be coded into the flow.

Refund and chargeback responsibility gaps

Worldpay processes refunds but does not auto-reverse order state or trigger credit notes in the ERP. The commerce platform and customer service must own the workflow that initiates refunds and records them accurately.

Settlement and reconciliation lag

Captures and settlements are not instant. Refunds, chargebacks and interchange adjustments appear in batches and may lag several days. Reconciliation schedules and exception investigation ownership must be pre-agreed.

04 · The real work

Refund and chargeback handling usually exposes the clearest ownership gaps: who initiates, who investigates, and who owns the credit note in the ledger if systems disagree on what happened.

05 · Where it sits

Where this integration sits in your estate.

Worldpay holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Works across the whole stack. Connect Worldpay to your storefront, ERP and everything between.

System of record
Source / owner
Worldpay
Payment processor and transaction authority
  • Card authorisation and approval decisions
  • Transaction tokenisation and secure storage
  • Capture, refund and settlement batching
  • 3DS and SCA compliance enforcement
  • Chargeback notification and dispute management
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Checkout experience and payment method presentation
  • Order confirmation and customer communication
  • Refund request initiation and investigation
  • Saved-card customer preference and consent
  • Payment method and billing address validation
Connected neighbours
Integration layer
ERP
Receives settlement records and matched receipts; records refunds as credit notes; reconciles bank deposits daily.
Integration layer
OMS
Holds order state and triggers capture timing; initiates refunds based on return authorisation or customer service decision.
Integration layer
WMS / 3PL
Dispatch confirmation may trigger capture (post-picking model); returns trigger refund initiation.
Integration layer
Customer service platform
Initiates refunds, investigates chargebacks, and responds to customer disputes with transaction and order evidence.
Integration layer
Business intelligence
Consumes payment metrics (approval rates, fraud indicators, settlement lag) for finance and risk reporting.
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • ERP (finance ledger, credit limits, bank reconciliation)
  • OMS (order routing, split shipment, returns)
  • WMS / 3PL (fulfilment and dispatch confirmation)
  • Customer service platform (refund and chargeback investigation)
  • Tax and compliance system (PCI DSS, regional regulatory rules)
  • Business intelligence (payment analytics, approval rates, fraud trends)
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into WORLDPAY & ERP
←From WORLDPAY & COMMERCE AND ERP
↔BOTH WAYS
Payment intent and customer data: Cart total, customer account, saved-card tokens and 3DS preference flow from the storefront to Worldpay
The payment platform initiates authorisation and returns a transaction ID and status.
Authorisation and capture state: Transaction outcome, approval code, tokenised card reference and liability shift (3DS result) flow back to the commerce platform
This drives whether the order is confirmed or declined and what the customer sees.
Capture and settlement records: Confirmed payment state, transaction ID and settled amount flow to the ERP as a matched receipt against the sales order
This allows finance to reconcile and invoice.
Refund and chargeback events: Full and partial refund requests from customer service or returns workflows, and chargeback notifications from Worldpay, flow back into order management and ERP credit notes.
Reconciliation and exception handling: Daily settlement files from Worldpay feed into ERP bank reconciliation
Payment failures, timeouts, and 3DS exceptions generate alerts and queue entries that require investigation.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Payment flow design and testing

    We map authorisation, capture, tokenisation and 3DS handling end-to-end from cart to settlement. We test fallback scenarios, timeout handling and idempotency to ensure resilience.

  2. 02
    Exception queue and alerting

    We build alert and dead-letter queues for failed authorisations, capture rejections, 3DS timeout, tokenisation mismatches and reconciliation gaps. Each exception is logged with customer and order context.

  3. 03
    Refund and chargeback workflow

    We connect Worldpay refund and chargeback events back to order management and ERP, triggering credit notes and case records so customer service and finance have visibility.

  4. 04
    Reconciliation and settlement monitoring

    We build reconciliation schedules that pull daily settlement files from Worldpay, match them against captured transactions in the ERP, and flag unmatched amounts and late items.

  5. 05
    Replatform and upgrades

    We plan token migration, PCI compliance scope, and payment flow cutover so you replatform without losing saved cards or breaking approval rates. We test fallback and rollback paths.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataPayment methods enabled
Source / ownerWorldpay
Maintained byFinance and Payments team
NotesCard types, wallet options, 3DS rules and fraud velocity thresholds are configured in Worldpay and must match commerce platform checkout settings.
DataAuthorisation, capture, refund and chargeback state
Source / ownerWorldpay
Maintained byPayments team
NotesTransaction outcome, approval codes and settlement status live in Worldpay; the commerce platform and ERP receive state changes via API and webhook.
DataTokenisation and saved-card lifecycle
Source / ownerWorldpay
Maintained byPayments team
NotesCard tokens are issued and stored by Worldpay; the commerce platform must manage customer consent, token reference and fallback to new auth on token expiry.
DataSettlement and reconciliation records
Source / ownerWorldpay and ERP
Maintained byFinance team
NotesWorldpay provides settlement files; the ERP matches them against captured sales orders and records matched receipts and unmatched exceptions.
DataRefund and chargeback investigation workflow
Source / ownerOrder management and ERP
Maintained byCustomer service and Finance team
NotesWorldpay notifies of the event; the commerce order and ERP credit note must be updated and the investigation tracked in a named exception queue.
Data3DS and SCA compliance audit trail
Source / ownerWorldpay
Maintained byCompliance and Payments team
Notes3DS authentication results, liability shift and exemption decisions are logged by Worldpay; regular audit queries validate compliance against PCI DSS and regional regulation.
10 · Experienced integrator

Payment integration at scale

iWeb has integrated Worldpay into commerce estates of all sizes, from small retailers to large omnichannel operations. We understand how payment state drives order lifecycle, how refunds reconcile to finance, and how 3DS and tokenisation work across replatforms.

We design auth-to-capture-to-settlement flows that respect order state, refund windows and ERP reconciliation schedules.
We know how to handle deferred capture, split payments, and edge cases (auth expiry, mid-flight refunds, late chargebacks) without losing money or creating reconciliation drift.
We build exception queues and monitoring so payment failures, tokenisation mismatches and chargeback leakage surface to the team before they hit the bottom line.
We understand how Worldpay sits alongside your OMS, WMS and customer service systems so refunds, returns and disputes flow back cleanly and are investigated in a named queue.
We plan token cutover and replatform strategy so you migrate off an old payment processor without forcing customers to re-enter cards or losing saved-card recovery rates.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Test authorisation timeout and retry logic; confirm idempotency key prevents duplicate charges on retry.
Verify capture timing matches order state (immediate vs deferred) and that captures succeed within Worldpay's window.
Test refund initiation from commerce and ERP; confirm settlement file deducts refund and ERP records matching credit note.
Confirm 3DS challenge flow triggers correctly, liability shift status is logged, and failed auth does not create zombie orders.
Verify tokenisation: saved cards reuse without re-auth, token expiry triggers fallback to new auth, and replatform migration preserves tokens.
Test chargeback notification arrival and confirm order, customer and finance records are updated with investigation queue entry.
Confirm daily settlement reconciliation: settlement file matches captured amounts, unmatched items surface as exceptions, and bank deposit matches ERP receipt.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Auth-to-capture timing breaks order promise

Authorisation holds may expire, or capture delays may miss merchant-imposed windows. If the commerce platform does not communicate capture timing to Worldpay clearly, orders fail silently and customers chase refunds.

3DS exemption drift and fraud liability shift

Worldpay fraud rules and 3DS exemption grants change without notice. If your commerce platform is not configured to re-evaluate exemption eligibility, you may lose liability shift and approval rates may drop unexpectedly.

Tokenisation breakage on replatform

Saved cards stored in old platform formats do not migrate cleanly to new payment APIs. Customers get unexpected re-auth prompts, cart recovery fails, and subscription renewals are missed.

Refunds not reconciled to credit notes

Worldpay processes a refund, but the ERP is not notified. Finance sees a bank credit but no matching credit note, breaking month-end reconciliation and overstating receivables.

Chargebacks lost between systems

Worldpay receives a chargeback notification but the alert does not reach customer service or order management. The team does not see the dispute, does not investigate, and the chargeback goes uncontested.

Settlement mismatch and cash timing

Worldpay settlement amount differs from captured transactions due to refunds, chargebacks or interchange fees. If the ERP was reconciled on capture date, the reconciliation drifts and cash forecast is wrong.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Worldpay integrations.

How are authorisation and capture separated in the flow?

By default, Worldpay authorises and captures immediately when the order is placed. If you need deferred capture (e.g., after picking or fraud review), the commerce platform must request auth-only and then call capture later. iWeb designs and monitors the timing so refunds can be processed before capture if needed.

What happens if Worldpay is down during checkout?

The commerce platform should queue the payment intent and retry at scheduled intervals (e.g., every 30 seconds for 10 minutes). If the retry window expires, the order is flagged for manual review. iWeb sets up retry logic, observability and escalation so checkout timeout does not kill the sale.

How do refunds reconcile to the ERP?

Refunds initiated via Worldpay or the commerce platform generate a transaction in Worldpay. The settlement file includes the refund amount. iWeb maps the refund event to a credit note in the ERP and matches it to the original sales invoice so finance can reconcile.

How is 3DS handled and what happens if the customer fails authentication?

Worldpay initiates 3DS based on card type, amount, issuer and your configured rules. If the cardholder fails authentication, the transaction is declined. The commerce platform must offer a fallback payment method. iWeb logs the 3DS result, liability shift status and decline reason so you can analyse approval rates and risk.

What happens to saved cards during a replatform?

Cards stored in the old platform's payment tokenisation system do not automatically transfer to the new system. Customers must re-enter their card or you must migrate tokens via Worldpay's secure token migration service. iWeb plans token cutover so saved-card customers are not forced to re-auth unexpectedly.

How are chargebacks tracked and who investigates them?

Worldpay notifies you of a chargeback via API and settlement file deduction. iWeb connects this to the original order so customer service can investigate the dispute (e.g., product damage, unauthorised transaction). A credit note is recorded and the outcome is tracked.

What is the difference between a refund and a chargeback?

A refund is initiated by you (via Worldpay or the commerce platform) when a customer requests their money back or returns goods. A chargeback is initiated by the customer's card issuer when the customer disputes the transaction directly with their bank. Chargebacks are costlier and require evidence to contest.

How does Worldpay settlement reconcile to the bank statement?

Worldpay batches captures and refunds, then settles (deposits net amount) to your bank account daily or per your contract. The settlement file from Worldpay lists each transaction. iWeb maps the settlement file to captured sales orders and refunds so the ERP bank-reconciliation process matches the deposit.

What happens if a refund request is made after Worldpay has already settled?

Worldpay can still process a refund after settlement; the refund is deducted from the next settlement batch. The ERP must record the refund transaction and credit note in the correct period so accounts are not overstated.

Can Worldpay payments be made idempotent so duplicate requests do not double-charge?

Yes. Worldpay supports idempotency keys so the same payment intent, if retried, is recognised and only charged once. iWeb ensures the commerce platform and order management send consistent idempotency keys on retry so network timeouts do not create duplicate transactions.

How is PCI DSS compliance handled when integrating with Worldpay?

Your commerce platform should never store full card data; instead, Worldpay tokenises the card and returns a reference. iWeb ensures the integration uses Worldpay's hosted payment forms or tokenisation API so your PCI scope is minimised and audit burden is lower.

What monitoring and alerting should be in place for payment failures?

iWeb sets up real-time alerts for authorisation failures, capture rejections, 3DS timeout, tokenisation mismatches and reconciliation gaps. Each alert includes customer, order and payment context so the team can investigate quickly. Escalation paths are defined so critical failures reach the payments team within minutes.

How do split payments or deferred captures work with Worldpay?

Worldpay supports split authorisation (e.g., one auth for two fulfilment locations) and partial capture. iWeb designs the order routing and capture workflow so each split is tracked, captured separately if needed, and reconciled to the correct cost centre or warehouse.

What happens if a customer disputes a transaction months later?

The customer can file a chargeback up to 180 days (or longer per card scheme rules) after the transaction. Worldpay notifies you and debits your account. iWeb ensures you have order, invoice and dispatch records tied to the transaction ID so you can contest the chargeback with evidence.

Next step

Have a Worldpay integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →