> 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/fiserv.md).

# Fiserv

Accept card and wallet payments.

<div align="left"><img src="https://hyperswitch.io/icons/homePageIcons/logos/fiservLogo.svg" alt=""></div>

Fiserv operates as a payment gateway. Its declared card and wallet methods support refunds but not mandates; 3DS is not supported for card payments and does not apply to wallets. Payments can use automatic, manual, or sequential automatic capture, while incoming webhooks are not implemented in this connector.

### 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 | not supported | supported | automatic, sequential automatic, manual | not supported  | American Express, Discover, Interac, JCB, Mastercard, UnionPay, Visa | 27        | 156        |
| card           | Debit Card  | not supported | supported | automatic, sequential automatic, manual | not supported  | American Express, Discover, Interac, JCB, Mastercard, UnionPay, Visa | 27        | 156        |
| wallet         | Apple Pay   | not supported | supported | automatic, sequential automatic, manual | not applicable | -                                                                    | 85        | 22         |
| wallet         | Google Pay  | not supported | supported | automatic, sequential automatic, manual | not applicable | -                                                                    | 11        | 10         |
| wallet         | PayPal      | not supported | supported | automatic, sequential automatic, manual | not applicable | -                                                                    | 20        | 15         |

### Authentication

Supply an API Key, API Secret, and Merchant ID in the connector configuration. Hyperswitch uses the API Secret to compute a fresh HMAC-SHA256 authorization signature for each request, and sends the signature with the API key, client request ID, timestamp, and HMAC token type. See [`FiservAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/2ef1f9ee5bdf65356c3169f4f5db67fa1d4de7bc/crates/hyperswitch_connectors/src/connectors/fiserv/transformers.rs#L733-L749) and [`generate_authorization_signature()`](https://github.com/juspay/hyperswitch/blob/2ef1f9ee5bdf65356c3169f4f5db67fa1d4de7bc/crates/hyperswitch_connectors/src/connectors/fiserv.rs#L67-L127).

### Before you start

1. Register with Fiserv at [fiserv.com](https://www.fiserv.com/).
2. Create or sign in to your account in the [Hyperswitch control center](https://app.hyperswitch.io/).
3. In the Fiserv dashboard, open **Credentials** to find the API Key, API Secret, and Merchant ID.
4. Enable the same payment methods in Fiserv that you plan to select in Hyperswitch.
5. Have the credentials listed in [Authentication](#authentication) ready.

To connect Fiserv to your Hyperswitch account, follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for what Fiserv supports.

### Webhooks

Fiserv webhooks are not currently processed by this connector. Do not configure Fiserv webhooks as the source of status updates in Hyperswitch. The incoming webhook implementation returns `EventNotSupported` and `WebhooksNotImplemented`; see [`get_webhook_event_type()`](https://github.com/juspay/hyperswitch/blob/2ef1f9ee5bdf65356c3169f4f5db67fa1d4de7bc/crates/hyperswitch_connectors/src/connectors/fiserv.rs#L910-L934).

### Source reference

[Fiserv connector implementation](https://github.com/juspay/hyperswitch/blob/2ef1f9ee5bdf65356c3169f4f5db67fa1d4de7bc/crates/hyperswitch_connectors/src/connectors/fiserv.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/fiserv.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.