dLocal

Configure dLocal card and voucher payments with Hyperswitch.

OXXO vouchers give dLocal's payment gateway route a cash-based option beside credit and debit cards. Cards accept automatic, manual, and sequential automatic capture, while OXXO uses automatic capture. Refunds are supported for each route, and mandates are not supported.

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	not supported	supported	automatic, manual, sequential automatic	supported, optional	American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Mastercard, UnionPay, Visa	-	-
card	Debit Card	not supported	supported	automatic, manual, sequential automatic	supported, optional	American Express, Cartes Bancaires, Diners Club, Discover, Interac, JCB, Mastercard, UnionPay, Visa	-	-
voucher	OXXO	not supported	supported	automatic	not applicable	-	-	MXN

Activate dLocal with Hyperswitch

Before you start

1. Register with dLocal.

2. Sign in to the Hyperswitch control center or create your Hyperswitch account.

3. Copy your Login, Secret Key, and Trans Key from the dLocal dashboard.

4. Enable the same payment methods in dLocal and in your Hyperswitch connector configuration.

To connect dLocal to your Hyperswitch account, follow Activate a connector on Hyperswitch, then return here for what dLocal supports.

Connector-Specific Notes

Each API request is signed with HMAC-SHA256. For an empty body, Hyperswitch concatenates the login and request date with no delimiter. Otherwise it concatenates the login, request date, and request body in that order with no delimiter. It hex-encodes the signature and sends Authorization: V2-HMAC-SHA256, Signature: <hex signature>. See build_headers().

Authentication

Provide a <login>, <transaction key>, and <secret key>. The SignatureKey mapping assigns api_key to the login, key1 to the transaction key, and api_secret to the secret key. The login and transaction key are also sent separately as X-Login: <login> and X-Trans-Key: <transaction key>; the secret key is the HMAC key and is not sent as a header value. See DlocalAuthType::try_from() and build_headers().

Webhooks

Webhooks are not currently supported. Payment status updates rely on syncing with the API. The webhook implementation returns EventNotSupported and does not provide a resource object. See get_webhook_event_type().

Source reference

The connector implementation is dlocal.rs.