Skip to main content
Worldpay (VAP) is a payment gateway providing secure card processing solutions primarily for merchants in North America. Worldpay (VAP) offers comprehensive payment processing capabilities with extensive currency support.

​
Setup

Contact your Worldpay (VAP) account manager to obtain your credentials and set up your account.

​
Connector configuration

After setting up your Worldpay (VAP) account, you can configure the connector in Gr4vy using one of the following methods:
  • Flow - Configure payment routing rules through your Gr4vy dashboard
  • API integration - Specify the payment_service_id when creating transactions to explicitly route payments to this connector

​
Credentials

Configure the following credentials in the Gr4vy dashboard, which are obtained from your Worldpay (VAP) account manager:
  • Username - Your Worldpay (VAP) username for API access
  • Password - Your Worldpay (VAP) password for authentication
  • Merchant ID - Your Worldpay (VAP) merchant identifier
  • Default Report Group - The default report group value used for every Worldpay (VAP) API request. See the Worldpay (VAP) docs for more information on how report groups work
  • Use sandbox (optional) - When enabled in the sandbox environment, uses the Worldpay sandbox instead of pre-production. This setting is ignored in production
If Worldpay asks for the IP addresses that connect to it, contact support for your instance’s IP addresses. Each instance has its own addresses for each environment.

​
Mail Order Telephone Order (MOTO)

Worldpay (VAP) differentiates telephone from mail orders with different values for order source. Gr4vy maps all MOTO transactions to telephone.

​
Capabilities

This connector doesn’t support the Mastercard Transaction Link Identifier (TLID) yet. Worldpay plans to add support in its April 2027 release.

​
Supported countries

​
Supported currencies

​
Integration

To accept card payments with Worldpay (VAP), use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:
  • Embed - A pre-built, customizable payment form that handles the complete payment flow
  • Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
  • Mobile SDKs - Embed SDKs for iOS, Android, and React Native
These methods handle card data collection and tokenization. Once the card details are collected and tokenized, create a transaction through the Gr4vy API, which routes the payment to your configured Worldpay (VAP) connection based on your Flow rules or explicit payment_service_id parameter.

​
Testing

Worldpay (VAP) offers two test environments. By default, a Worldpay (VAP) connection in a Gr4vy sandbox environment sends requests to Worldpay’s Pre-Live environment. Enable Use sandbox on the connection to send requests to Worldpay’s Sandbox simulator instead. See Certification and Testing Environments for details on both.

​
Sandbox

The Sandbox is a stateless simulator for functional testing. For card authorizations and sales, the last three digits of the card number set the response code that the simulator returns. For Apple Pay and Google Pay, the last three digits of the amount set the response code. See Testing Response Reason Codes and Messages for the values to use.

​
Pre-Live

Pre-Live is where Worldpay runs its certification tests. Worldpay publishes the test scenarios and the data each one expects:

​
Response and validation errors

Worldpay (VAP) returns two kinds of errors:
  • Payment transaction response codes describe the outcome of a transaction, such as a decline. See Payment Transaction Response Codes.
  • XML validation errors mean Worldpay rejected the request before processing it. Gr4vy returns these as an invalid_service_request error and includes Worldpay’s message, which names the field that failed validation. See XML Validation Error Messages.