> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/worldpayvantiv.md).

# Worldpay Vantiv

Accept card and wallet payments through Worldpay Vantiv using merchant-scoped XML credentials.

Worldpay Vantiv is implemented separately from the Worldpay connector and uses its own routes and configuration. It supports cards and selected wallets, with refunds and mandate reuse, and both immediate and delayed capture. Disputes are supported end-to-end: fetching, syncing, acceptance, and evidence submission, with file upload and retrieval.

### Status and capabilities

**Integration status:** sandbox

**Category:** payment gateway

**Webhook flows:** None declared in code

| Payment method | Type        | Mandates  | Refunds   | Capture methods                         | 3DS            | Card networks                                                  | Countries                                         | Currencies                                        |
| -------------- | ----------- | --------- | --------- | --------------------------------------- | -------------- | -------------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------- |
| card           | Credit Card | supported | supported | automatic, manual, sequential automatic | not supported  | American Express, Diners Club, Discover, JCB, Mastercard, Visa | 133 ([full list](https://hyperswitch.io/pm-list)) | 147 ([full list](https://hyperswitch.io/pm-list)) |
| card           | Debit Card  | supported | supported | automatic, manual, sequential automatic | not supported  | American Express, Diners Club, Discover, JCB, Mastercard, Visa | 133 ([full list](https://hyperswitch.io/pm-list)) | 147 ([full list](https://hyperswitch.io/pm-list)) |
| wallet         | Apple Pay   | supported | supported | automatic, manual, sequential automatic | not applicable | -                                                              | 133 ([full list](https://hyperswitch.io/pm-list)) | 147 ([full list](https://hyperswitch.io/pm-list)) |
| wallet         | Google Pay  | supported | supported | automatic, manual, sequential automatic | not applicable | -                                                              | 133 ([full list](https://hyperswitch.io/pm-list)) | 147 ([full list](https://hyperswitch.io/pm-list)) |

### Authentication

Worldpay Vantiv requires **Username**, **Password**, and **Merchant ID**. Its shared [`build_headers()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L106-L121) override sends `Content-Type` only, so core payment and refund requests do not use the connector's Basic authorization helper. Instead, the XML request contains Username and Password in `authentication` and Merchant ID in the `merchantId` attribute; see [`CnpOnlineRequest and Authentication`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv/transformers.rs#L140-L168) and [`TryFrom<&WorldpayvantivRouterData<&PaymentsAuthorizeRouterData>> for CnpOnlineRequest`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv/transformers.rs#L779-L836).

Sync, dispute, and file paths use flow-specific headers. Those paths call [`get_auth_header()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L141-L154), which constructs `<Username>:<Password>`, Base64-encodes it, and sends `Authorization: Basic <encoded value>`; see the [`payment-sync get_headers()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L383-L391), [`refund-sync get_headers()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L900-L910), [`dispute get_headers()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L1067-L1090), and [`file-upload get_headers()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L1354-L1367) overrides. [`WorldpayvantivAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv/transformers.rs#L83-L99) maps all three credentials. The connector remains independent from Worldpay through [`ConnectorCommon for Worldpayvantiv`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L124-L139).

### Before you start

1. Register with Worldpay Vantiv at [worldpay.com](https://www.worldpay.com/en).
2. Sign in to the [Hyperswitch control center](https://app.hyperswitch.io/).
3. Obtain **Username**, **Password**, and **Merchant ID** from the Worldpay Vantiv dashboard.
4. Set the **Report Group** and **Merchant Config Currency** metadata fields on the connector account. Authorization checks the configured currency, so it must be correct.
5. If the activation flow asks you to select payment methods, choose only the methods enabled in the connector dashboard.

Follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for Worldpay Vantiv-specific behavior.

### Webhooks

Handled event wire values: **0**. Webhooks are not currently supported, so status updates rely on syncing through the API. Sync requests go to a separate reporting endpoint, `{secondary_base_url}/reports/dtrPaymentStatus/{transaction_id}`, rather than the main transaction URL; see the [`payment-sync get_url()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L398-L409) construction. [`get_webhook_object_reference_id()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L1544-L1549), [`get_webhook_event_type()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L1551-L1557), and [`get_webhook_resource_object()`](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs#L1559-L1565) each return `WebhooksNotImplemented`.

### Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch `e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0`. See [Worldpay Vantiv connector source](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv.rs) and [Worldpay Vantiv transformers](https://github.com/juspay/hyperswitch/blob/e8e30d1018b1ab5aecada04cf1b3ab63a39a68d0/crates/hyperswitch_connectors/src/connectors/worldpayvantiv/transformers.rs).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/worldpayvantiv.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.