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

Features

Worldpay (VAP) supports the following features:
  • Delayed capture - Authorize a payment and capture it at a later time
  • Partial capture - Capture a portion of the authorized amount
  • Partial refunds - Refund a portion of the captured amount
  • Refunds - Refund a captured payment
  • Void - Cancel an authorized transaction before capture
  • Zero auth - Verify a card without charging it
  • Digital wallets - Support for Apple Pay, Google Pay, and other wallet integrations
  • Network tokens - Network tokenization is enabled by default
  • 3-D Secure - Pass-through 3DS authentication

Supported countries

Worldpay (VAP) supports transactions from buyers in the following countries:
Country codeCountry code
CAUS

Supported currencies

Worldpay (VAP) supports processing payments in the following currencies:
Currency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency code
AEDAFNALLAMDAOAARSAUDAWGAZNBAM
BBDBDTBGNBHDBIFBMDBNDBOBBRLBSD
BTNBWPBYNBZDCADCDFCHFCLPCNYCOP
CRCCUPCVECZKDJFDKKDOPDZDEGPERN
ETBEURFJDFKPGBPGELGHSGIPGMDGNF
GTQGYDHKDHNLHTGHUFIDRILSINRIQD
IRRISKJMDJODJPYKESKGSKHRKMFKPW
KRWKWDKYDKZTLAKLBPLKRLRDLSLLYD
MADMDLMGAMKDMMKMNTMOPMRUMURMVR
MWKMXNMYRMZNNADNGNNIONOKNPRNZD
OMRPABPENPGKPHPPKRPLNPYGQARRON
RSDRUBRWFSARSBDSCRSDGSEKSGDSHP
SLESOSSRDSSPSTNSYPSZLTHBTJSTMT
TNDTOPTRYTTDTWDTZSUAHUGXUSDUYU
UZSVESVNDVUVWSTXAFXCDXCGXOFXPF
YERZARZMW

Limitations

The following features are not supported by this connector:
  • Delete token - Deleting stored payment tokens is not supported
  • Over capture - Capturing more than the authorized amount is not supported
  • Partial authorization - Partial authorization is not supported
  • Payment method tokenization - Storing payment methods outside of transactions using a separate tokenization flow
  • Settlement reporting - Automatic settlement reporting is not supported
  • Transaction sync - Transaction status synchronization is not supported

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 - Native SDKs for iOS, Android, React Native, and other platforms
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.