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

# Calida

Connect Calida through Hyperswitch.

Calida gives merchants an alternative payment method integration in Hyperswitch. It declares wallet support in the capability block below, with method-specific capture, refund, mandate, region, and currency details there. Use the status and webhook declaration in that block when deciding whether to enable it.

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

### Status and capabilities

**Integration status:** live

**Category:** alternative payment method

**Webhook flows:** payments

| Payment method | Type     | Mandates      | Refunds       | Capture methods | Countries | Currencies |
| -------------- | -------- | ------------- | ------------- | --------------- | --------- | ---------- |
| wallet         | Bluecode | not supported | not supported | automatic       | 30        | EUR        |

### Authentication

Calida provides three values when you set up your account with them — contact Calida or visit <https://www.calida.com> to get started:

| Field                       | Hyperswitch configuration | Description                                                                                               |
| --------------------------- | ------------------------- | --------------------------------------------------------------------------------------------------------- |
| **E-Order Token**           | Connector API key         | API token issued by Calida, sent as an `Authorization: token <E-Order Token>` header on every API request |
| **Shop Name**               | Connector metadata        | Your Calida shop identifier, sent as `shop_name` in each payment creation request                         |
| **Source verification key** | Webhook secret            | Secret used to verify incoming Calida webhooks (see [Webhooks](#webhooks))                                |

Enter these through the connector configuration form in the control center. The E-Order Token uses Hyperswitch's header-key authentication — see [`CalidaAuthType`](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/calida/transformers.rs#L158-L172) and the [auth header construction](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/calida.rs#L123-L134) in the connector source.

### Before you start

1. Set up a Calida account at <https://www.calida.com/> to obtain the E-Order Token, Shop Name, and Source verification key.
2. Sign in to the [Hyperswitch control center](https://app.hyperswitch.io/).
3. Open the connector configuration form and provide the fields named in Authentication.
4. Use the configured base URL for the environment you are enabling.

### Webhooks

Calida sends payment webhooks. Hyperswitch verifies each webhook using **HMAC-SHA512**: the signature arrives in the `x-eorder-webhook-signature` header (hex-encoded) and is computed over the **sorted, minified JSON** of the webhook body — not the raw request body. The HMAC secret is the **Source verification key** you configured in the connector webhook details.

Webhook statuses map to Hyperswitch payment states as follows:

| Calida status       | Hyperswitch state           |
| ------------------- | --------------------------- |
| `COMPLETED`         | Charged (payment succeeded) |
| `FAILED`            | Failure                     |
| `MANUAL_PROCESSING` | Pending                     |
| `PENDING`           | Authentication pending      |
| `PAYMENT_INITIATED` | Authentication pending      |

See [webhook verification](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/calida.rs#L621-L682) and [status mapping](https://github.com/juspay/hyperswitch/blob/ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7/crates/hyperswitch_connectors/src/connectors/calida/transformers.rs#L174-L185) in the connector source.

### Source reference

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