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.

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

Retrieve the Integration Key for the correct environment.
In Settings → Connections, choose + Add Connection and select EBANX.
On Configure Connector, enter a Name.
On Enter Credentials, paste the Integration Key.
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.

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.
Card data is minimized. Field-level detail on what Athia stores is in 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

Athia Connectors — the full connector catalog
Integrating Athia — file drops, warehouse shares and the other integration paths
Athia Data Dictionary — field definitions