Skip to content


Payments overview

Our article will cover some foundational understanding of online payment processing. This is a good start, if you're new to the payment industry.


API principles

Before you start integrating, you should make yourself familiar with our API Principles. This page outlines the standards to work with our APIs. Our design is RESTful meaning our APIs are structured around resources and use standard HTTP methods (GET, POST, PUT, DELETE) to interact with those resources.

After reading this, you should have a good understanding of versioning, non-breaking definitions and best practices allowing your integration to be resilient.

Integration options

We offer four different ways to take payments depending on the control over the payment flow you want to have:

  1. Plugins
    Our pre-built no-code option to add payment processing capabilities to your website.

  2. Hosted Payment Pages
    Our low-code redirect integration taking the PCI compliance burden off you.

  3. Payments API
    Our medium-code direct integration with the option of using an SDK to lower PCI compliance burden. This API is an orchestration service combining some of our modular APIs.

  4. Modular APIs
    Our high-code direct integration giving you full control over your payment flow by sending individual requests to our APIs. You also have th option to use an SDK to lower the PCI compliance burden.

To get a more detailed understanding and make the right choice for your business, take a look at our capability comparison.

Prerequisites and best practice

  • Credentials

    To authenticate your merchant details, when sending a request to our APIs, you must supply credentials. If you haven't got these already, you can contact your Implementation Manager.

  • DNS Whitelisting

    Whitelist the following URLs:

    • https://try.access.worldpay.com/
    • https://access.worldpay.com/

    Please ensure you use DNS whitelisting not explicit IP whitelisting as we might change our IP addresses.

  • WP-CorrelationId logging

    We return a WP-CorrelationId in the headers of service responses. We highly recommend you log this as we can use it to examine individual requests.

  • Security

    Familiarize yourself with our security best practices.

Testing and go live

Before you're going live you should test your integration. Each service has their own testing mechanism and magic values. You navigate to the respective test pages here.



Got a question not covered here? Ask our AI search in the top right corner.