Skip to content

Integrating Worldpay (FIS)

Auth: OAuth 2.0 (client credentials) · Partner program: not required · Setup time: about 20 minutes · Last verified: 2026-05-15

Enterprise EMEA + global card gateway under FIS. Two API surfaces co-exist:

  1. Worldpay Access REST API — modern JSON. What this adapter uses.
  2. Worldpay Corporate Gateway (SOAP) — legacy XML over POST. Used by long-running merchants on Worldpay Business Gateway. Not supported by this adapter.

Either:

  • HTTP Basic (username + password from the Worldpay portal), or
  • OAuth 2.0 client-credentials (Worldpay for Platforms; partner-program-gated).

The adapter accepts either set on the Connect Link form; submit one or the other.

  • Versioned media type. Every request asks for application/vnd.worldpay.payments-v7+json. Bump in constants.ts after re-testing.
  • Try host (try.access.worldpay.com) is the developer playground — sandbox-of-the-sandbox. Use it for early integration; flip to access-uat.worldpay.com for full UAT, then access.worldpay.com for live.
  • outcome ≠ lastEvent. Worldpay reports a high-level outcome plus a stream of state-transition events. The adapter maps outcome first, falling back to lastEvent for derived state.

Configure notifications under Webhooks in the Access dashboard. HMAC-SHA-256 of the raw body keyed with the webhook secret; the signature ships in Worldpay-Webhook-Signature as v1=….