What we do
Tools
Industries
Department
How we workLet's talk →
Home/Worldpay/Worldpay Developer API
Worldpay

Which Worldpay Developer API Your Account Actually Uses

If your account was set up for Access Worldpay, you call JSON REST APIs at try.access.worldpay.com while you build and access.worldpay.com when you go live, with Basic auth and a WP-Api-Version header. Accounts boarded on older or regional Worldpay gateways use different APIs and different credentials, so confirm which one is yours before you write code. Worldpay is now part of Global Payments, and the developer docs still live at docs.worldpay.com.

Calling Access Worldpay

Hosts: https://try.access.worldpay.com for testing, https://access.worldpay.com for live traffic.

Auth and headers: HTTP Basic with your base64-encoded username and password, Content-Type: application/json, and WP-Api-Version (the Payments API reference shows 2024-06-01).

First call: POST /api/payments starts a payment. 3DS, a FraudSight risk check, auto settlement and tokens are features you switch on in that request.

Access Worldpay or an older Worldpay gateway

Access Worldpay

JSON REST APIs with a Try environment

  • Payments, Card Payments, Payment Queries, Tokens, 3DS, FraudSight and Hosted Payment Pages, plus payouts and FX.
  • Checkout SDKs for web and native apps, and plugins for Shopify and Salesforce.
  • Events webhooks for payment, payout and chargeback status.
Other Worldpay APIs

Separate gateways, separate reference docs

  • The WPG API, Worldpay's long-running payments gateway, with its own reference in the API directory.
  • cnpAPI, the XML API for US card-not-present payments.
  • The Payrix API, used by software platforms that board their own merchants, covered on Worldpay for Platforms.

Your onboarding paperwork or Worldpay contact settles which side you're on. Access tutorials won't work with WPG or cnpAPI credentials.

A first Access Worldpay payment in Try, then live

  1. 1

    Get Try credentials from Worldpay

    Worldpay issues the username and password for the Try environment. The Postman collection in the docs needs them too, which makes it a quick way to confirm the credentials work before your own code does.

  2. 2

    Send a payment request

    Post to /api/payments on the Try host with the Basic auth header, the JSON content type and a pinned WP-Api-Version. Turn on only the features you need, such as 3DS or FraudSight.

    Watch for: pin the version header in one place in your code, so a later upgrade is one change and one round of testing.

  3. 3

    Force each outcome with magic values

    Put AUTHORISED or REFUSED in paymentInstrument.cardHolderName with a test card such as Visa 4000000000002701. Visa 4000000000002503 triggers a 3DS challenge.

    Watch for: the cardholder name picks the outcome and the card number picks the scheme and 3DS flow, so test refusals and challenges separately.

  4. 4

    Have the Events URL added

    Your Worldpay Implementation Manager adds your webhook URL and turns events on or off. It has to be HTTPS with a certificate from a trusted authority, signed with SHA-256 or stronger.

    Watch for: reply 200 within 10 seconds. Worldpay retries at intervals growing from 30 seconds to 2 hours for up to a week, and an event left unacknowledged can hold up the ones queued behind it.

  5. 5

    Open the firewall, verify, then switch hosts

    Allow Worldpay's full list of webhook IP addresses for each environment, and check each event with the HMAC signature or the certificate before acting on it. Then point the same code at access.worldpay.com with live credentials.

After the 200: where Worldpay payment results go missing

Orders marked paid on the first response alone

How you'll know: An order shows paid, but a later payment event or a chargeback never reaches it.

Fix: Treat the API response as the first word, not the last. n-frames builds the Events handler that updates the order, invoice or account on every payment event that follows.

Events blocked before they reach your code

How you'll know: Payments succeed in Try, yet your logs show no webhooks.

Fix: Check the firewall allows every Worldpay webhook IP for that environment, and that the certificate chain is SHA-256 or better.

A slow handler that delays everything

How you'll know: Events arrive in bursts, hours after the payments they describe.

Fix: Acknowledge with a 200 first and do the work afterwards from a queue, so you stay inside the 10-second window.

Refusals that nobody acts on

How you'll know: A refused payment sits in the dashboard while the customer believes the order went through.

Fix: Send each refusal to whatever acts on it: a retry, a note to the customer, or a task for the person who calls them.

Worldpay developer questions, old names included

Does Worldpay have a public API?

Yes, several. Access Worldpay is the family of JSON REST APIs documented at docs.worldpay.com, covering card and alternative payments, tokens, 3DS, fraud checks, payouts and payment queries. Store owners using Worldpay's plugins or hosted checkout through a Worldpay eCommerce account will find that setup on Worldpay eCommerce.

Is there a Worldpay sandbox for testing?

Yes. Access Worldpay calls it the Try environment, at try.access.worldpay.com. Each API has a testing page listing magic values, such as cardholder names that force an authorization or a refusal, and test cards that trigger a 3DS challenge.

Does Worldpay support ACH payments?

Worldpay processes ACH bank payments for US merchants, called eCheck in its US cnpAPI. ACH approval normally runs separately from card acceptance, so confirm with Worldpay that your account and API are enabled for it.

Can I integrate Worldpay myself without a developer?

For taking the payment, often yes: Worldpay has plugins for Shopify and Salesforce, and Hosted Payment Pages need far less code than a direct API build. Getting results into your order system, CRM or books without someone checking the dashboard still needs code. That follow-through is the piece n-frames writes.

Is RBS WorldPay the same company as Worldpay?

Yes, earlier in its history. RBS WorldPay was the name under the Royal Bank of Scotland. After several owners, Worldpay became part of Global Payments in January 2026. Old guides and some plugins still say RBS WorldPay, but today's APIs and dashboards run under the Worldpay name.

Who wires Worldpay payment events into our order system?

Your own developers can, from the Events docs. n-frames does it as a project: the webhook handler with signature checks, the order and invoice updates, and the routing of refusals and chargebacks to the people who handle them.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.