Worldpay, Integrated Properly Into Your Checkout

Worldpay's current developer platform is Access Worldpay, and the products relevant to most checkout work are:

• Payments API for authorisation, settlement and payment creation
• 3DS Actions API for authentication challenges and liability shift
• Manage Payments API for refunds, cancellations and post-authorisation actions
• Checkout SDK for capturing card details client side so the sensitive data stays out of your server and your PCI scope stays manageable
• Tokens, both Worldpay tokens and network tokens, for repeat and stored card payments
• Reporting and events, including webhooks, so your systems react to payment events instead of polling

Worldpay also applies risk assessment through FraudSight before authorisation, which is worth designing around rather than treating as an unexpected decline.

If you are on an older Worldpay integration rather than Access Worldpay, tell us during discovery. Migration is a normal piece of work but it changes the scope, and it is better priced upfront than discovered later.

Strong Customer Authentication is a regulatory requirement for most online card payments to UK and European customers. In practice it means 3DS, and 3DS done badly is one of the most common causes of lost conversion at checkout.

Two things matter. First, that the challenge is triggered when it needs to be and skipped when an exemption legitimately applies, because challenging every transaction costs you sales. Second, that the customer coming back from a challenge lands in the right place with their basket intact.

On PCI, the practical goal for most merchants is to keep card data out of your own systems entirely. Using Worldpay's client side capture rather than posting card numbers through your server is what keeps your compliance burden proportionate. We default to that unless there is a specific reason not to.

• WooCommerce including subscriptions, custom order flows and non-standard product types
• Shopify where the checkout permits it, and Shopify Plus where more control is available
• Laravel applications and bespoke checkouts, including portals, booking systems and SaaS billing
• Headless builds where the front end and the payment logic sit apart
• Existing sites that already have Worldpay but are losing transactions or failing SCA

We also handle the connection between payments and everything downstream, so authorisations, refunds and chargebacks reach your accounting system rather than being reconciled by hand each month.

If you bill on a schedule, the integration is more involved than a single purchase. Worldpay supports subscription, instalment and unscheduled merchant-initiated transactions, each with different authentication expectations.

The parts that need deliberate design are card storage and tokenisation, retry behaviour when a renewal fails, handling expired and replaced cards, and giving customers a way to update payment details without cancelling. Get retries wrong and you either churn customers who would have paid, or you hammer a card and trigger the issuer.

1. Discovery. We confirm your platform, your Worldpay account and product set, your currencies and whether recurring billing is in scope.
2. Design. We define the payment flow, the authentication strategy, failure behaviour and what reaches your finance system.
3. Development. We build in Worldpay's test environment against real card scenarios.
4. Testing. Successful payments, declines, abandoned 3DS challenges, timeouts, partial refunds and duplicate submissions.
5. Deployment. We go live carefully, usually with live transaction monitoring for the first period.
6. Support. We monitor, patch and adapt as your requirements and Worldpay's platform change.