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

# Elavon

Connect Elavon through Hyperswitch.

Elavon supports debit and credit card payments with refunds, mandates, and manual capture. Card payments are declared without 3DS.

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

### 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, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Mastercard, UnionPay, Visa | USA       | 157        |
| card           | Debit Card  | supported | supported | automatic, manual, sequential automatic | not supported | American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Mastercard, UnionPay, Visa | USA       | 157        |

### Authentication

Elavon requires three credentials, which Elavon provides when you set up your account with them at <https://www.elavon.com/>: **Account Id**, **User ID**, and **Pin**. All three are sent with each API request as signature-key fields. See [`ElavonAuthType`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/elavon/transformers.rs#L148-L168) in the connector source. The labels come from [`[elavon.connector_auth.SignatureKey]`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/connector_configs/toml/sandbox.toml#L6923-L6926).

{% hint style="warning" %}
Elavon rejects 3DS card payments outright. Requests with 3DS enabled fail with a "not supported" error. The capability table's "3DS: not supported" means the connector errors on 3DS attempts, not that it falls back to non-3DS.
{% endhint %}

### Before you start

Elavon is available in the control center connector list. Have the credentials shown in the Authentication section ready before configuring the connector.

### Webhooks

Webhooks are not currently supported. All three webhook handlers return `WebhooksNotImplemented`; see [`IncomingWebhook`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/elavon.rs#L565-L588).

Since there are no callbacks, track status through the sync APIs: both payment sync and refund sync are implemented for Elavon, so use the payment and refund status check APIs through Hyperswitch to confirm outcomes.

### Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch `502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5`. See [Elavon connector source](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/elavon.rs) and [Elavon transformers](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/elavon/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/elavon.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.