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

# D24

Configure D24 card redirect payments with Hyperswitch.

D24 routes card payments through a hosted redirect. It supports payments in Chile only, in CLP and USD. The redirect completes with automatic capture and supports refunds. Mandates are not available for this payment route.

### Status and capabilities

**Integration status:** beta

**Category:** payment gateway

**Webhook flows:** None declared in code

| Payment method | Type          | Mandates      | Refunds   | Capture methods | Countries | Currencies |
| -------------- | ------------- | ------------- | --------- | --------------- | --------- | ---------- |
| card redirect  | Card Redirect | not supported | supported | automatic       | -         | -          |

### Authentication

Provide the **API Key**, **Read-only API Key**, and **API Signature** requested by the connector configuration. These labels map to the three accepted signature-key fields in [`D24AuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/d24/transformers.rs#L74-L94) and are declared in the [`d24.connector_auth.SignatureKey` configuration](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/connector_configs/toml/sandbox.toml#L9155-L9158).

### Before you start

For D24 account setup or enablement in Hyperswitch, reach out to the Hyperswitch team on Slack or through [Juspay's contact form](https://juspay.io/contact?country=US). D24 is not available in the Hyperswitch control center.

### Webhooks

D24 webhooks are not currently supported. Use Hyperswitch's Unified Connector Service (UCS) to sync payment and refund status. D24's direct connector sync methods are not used. See [`IncomingWebhook for D24`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/d24.rs#L348-L371), the [`UCS routing configuration`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/config/development.toml#L1684), and [D24 refund routing](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/d24.rs#L339-L345).

### Source reference

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