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

# Datatrans

Datatrans connector for payment gateway.

Datatrans supports credit and debit card payments with refunds, mandates, manual capture, and optional 3DS. It covers a broad European country set and multiple currencies.

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

### Status and capabilities

**Integration status:** live

**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 | supported, optional | American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Maestro, Mastercard, UnionPay, Visa | 49        | 26         |
| card           | Debit Card  | supported | supported | automatic, manual, sequential automatic | supported, optional | American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Maestro, Mastercard, UnionPay, Visa | 49        | 26         |

### Authentication

Supply **datatrans MerchantId** and **Passcode**, the two labels the control center shows. Both are required: [`DatatransAuthType`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/datatrans/transformers.rs#L449-L460) takes them as a `BodyKey` pair and rejects any other shape, and the labels come from [`[datatrans.connector_auth.BodyKey]`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/connector_configs/toml/sandbox.toml).

The form also offers **Acquirer Bin**, **Acquirer Merchant ID**, and **Acquirer Country Code**. All three are marked optional in the connector configuration, and the Datatrans connector reads none of them, so leave them blank unless the Hyperswitch team tells you otherwise.

### Before you start

1. Obtain your **datatrans MerchantId** and **Passcode** from Datatrans.
2. Sign in to the [Hyperswitch control center](https://app.hyperswitch.io/) and open Datatrans, which is offered in the connector list.
3. Enter both credentials during connector activation.

### Webhooks

Webhooks are not supported, so there is no event list and nothing to configure. All three handlers return `WebhooksNotImplemented`: [`get_webhook_object_reference_id()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/datatrans.rs#L782-L787), [`get_webhook_event_type()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/datatrans.rs#L789-L795) and [`get_webhook_resource_object()`](https://github.com/juspay/hyperswitch/blob/502bfe8ddbe6a9a9619dc4e0b88900a780c2aac5/crates/hyperswitch_connectors/src/connectors/datatrans.rs#L797-L803).

Use payment sync and refund sync for status instead. Both are implemented, unlike the webhook handlers.

### Source reference

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