For the complete documentation index, see llms.txt. This page is also available as Markdown.

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, 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)

Enter these through the connector configuration form in the control center. The E-Order Token uses Hyperswitch's header-key authentication — see CalidaAuthType and the auth header construction 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. Open the connector configuration form and provide the fields named in Authentication.

  3. 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 and status mapping in the connector source.

Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch ec9d1d22bf0257b7de4d4d8bbba4e27fd520bdf7. See Calida connector source and Calida transformers.

Last updated

Was this helpful?