---
updatedAt: 2026-09-30T19:57:44.000Z
agentTools:
  projectIndex: https://docs.deuna.com/llms.txt
---

# EBANX 

EBANX is the simplest self-serve connector in the catalog: one credential, one field, no schedule to choose. Because EBANX handles local payment methods alongside cards, this connection is how non-card activity reaches Athia rather than sitting outside your payment picture.

**DEUNA supports both EBANX Cross-Border and EBANX Local connections.**

## What you get

The payment activity processed through your EBANX account, across the methods EBANX handles for you — so orders paid by local methods appear beside your card traffic instead of being invisible to method-mix analysis.

What this connection carries, how far back it reaches, and the amount format it delivers are confirmed with your Athia team during setup — see the limits below.

## Before you start

You need your EBANX **Integration Key**, generated in the EBANX console; see EBANX's own documentation for where it is issued. EBANX issues separate keys for test and live, and a test key produces a connection that verifies and then carries nothing you recognize.

## Credentials Athia asks for

| Field               | Required | What it is / where to find it                                                                                             |
| ------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Name**            | Yes      | Your label for this connection — include the environment and region so a test connection is never mistaken for a live one |
| **Integration Key** | Yes      | Your EBANX Integration Key for the correct environment                                                                    |

There is **no Schedule field** on this connector, and no historical time-frame option.

## Setting up the connection

1. Retrieve the Integration Key for the correct environment.
2. In **Settings → Connections**, choose **+ Add Connection** and select **EBANX**.
3. On **Configure Connector**, enter a **Name**.
4. On **Enter Credentials**, paste the **Integration Key**.
5. Choose **Verify Connection**.

The connection then shows as `ACTIVE` and the first sync starts. Watch **Last synced** on this connector — with no schedule of your own to reason about, it is your evidence that data is flowing.

## Ebanx Local 

For EBANX Local, go to **Connections**, select **EBANX Local**, and enter your integration keys: Name, currency, integration key, public integration key, and whether the flow is **Purchase** or **Two-Step Purchase (Authorization + Capture)**.

![](https://files.readme.io/2e31ad0b791c38b0c1cb2c5e0cacb2016b466720400f27b5aa71608a2b592de4-image.png)

<br />

* DEUNA supports EBANX Local in all countries where the provider is available: Brazil, Chile, Colombia, and Mexico.

## Sync cadence

There is no schedule to pick — the EBANX wizard offers no **Schedule** field, so cadence is not a setting you control here. Use **Last synced** in the Connections list to confirm the connection is current, and raise it with your Athia team if it stops advancing.

## Limits and things to know

* **Data coverage and the backfill window are confirmed during setup**, along with the amount format the connection delivers. Confirm the amount format before anyone builds a reconciliation on it.
* **No schedule and no historical time-frame control.** You cannot set cadence or a backfill boundary from the wizard.
* **One connection per environment and account.** Keep test and live separate, and name them accordingly.
* **Historical loads are a separate conversation.** For history from before go-live, export it from EBANX and route it through a file drop — see [Integrating Athia](https://docs.deuna.com/docs/athia-integration).
* **Card data is minimized.** Field-level detail on what Athia stores is in [Athia Data Dictionary](https://docs.deuna.com/docs/athia-data-dictionary).

## Troubleshooting

| What you see                           | Likely cause                            | What to do                                          |
| -------------------------------------- | --------------------------------------- | --------------------------------------------------- |
| `ACTIVE` but the data looks unfamiliar | A test-environment key was used         | Replace the connection using the live key           |
| **Last synced** stops advancing        | Key rotated or revoked in EBANX         | Generate a new key and update the connection        |
| Older history is missing               | No backfill window is configurable here | Arrange a historical file load with your Athia team |

## Related

* [Athia Connectors](https://docs.deuna.com/docs/athia-connectors) — the full connector catalog
* [Integrating Athia](https://docs.deuna.com/docs/athia-integration) — file drops, warehouse shares and the other integration paths
* [Athia Data Dictionary](https://docs.deuna.com/docs/athia-data-dictionary) — field definitions