Athia Connectors

A Connection reads data from a provider you already use, on a credential you issue and can revoke at any time. Once it is live, Athia keeps a current picture of what you charged, what was approved or declined, what was refunded or disputed, and what the provider settled and charged you for.

How this path works

You issue a read-only credential in the provider's own console and paste it into Athia. Athia polls on a schedule you set on most connectors, from every 1 minute up to every 24 hours, and each Connection reports its status and last-synced time.

That interval is a ceiling on how often Athia asks, not a promise about how current the answer is: the provider decides what its API and reports expose and how far back they reach, and the data type decides the rest. See Cadence and historical reach belong to the provider below.

On this path Athia reads provider data only, and no connector can authorize, capture, refund or void a payment. Where Athia runs on DEUNA orchestration, agents do act inside the payment flow. The credential is read-only, except on the Stripe and Braintree connectors — see Setting up a connection below for the exact scopes.

Seven connectors are self-serve; the rest are set up with the Athia team. The catalog below gives each connector, its setup path and its manual.

Payment connectors

Anti-fraud connectors

Sift, Kount, Chargeblast and Cybersource Fraud add the fraud and dispute signals behind each decision. All four are set up with the Athia team. Start in the connector catalog: select the source you want, and your Athia team configures the connection with you.

Fraud-engine declines never reach a processor, so they sit outside acceptance rate. Connecting a fraud source is what separates "our rules blocked it" from "the issuer declined it".

Chargeblast carries dispute and chargeback alerting signals only, not full decision data.

Cost data

Fee data reaches Athia through an in-product CSV upload against an Athia-provided template, covering card and non-card payment fees, so routing recommendations can account for what each route costs. For the template, the column definitions and the upload steps, see Cost Data Uploads.

How a connection stays current

Most connectors combine two mechanisms. Athia polls the provider on the Schedule you set, and the provider pushes events to an Athia Webhook Destination URL that you copy from the connection wizard and register in the provider's console. Webhooks are what make status changes near-real-time; polling is what fills in reports and settlement.

Each connector's manual gives the exact console path for the webhook and the events to select.

Three providers work differently.

Setting up a connection

These steps are generic across the self-serve connectors.

1. In your provider's console, create a read-only API credential scoped to reporting and transaction read.
2. In Athia, go to Settings → Connections → Add Connection and select the provider.
3. Configuration — name the connection and set the Schedule. EBANX, PPRO, Worldpay and Amex have no Schedule field.
4. Credentials — paste the credential.
5. Verify — click Verify Connection. The connection moves to ACTIVE and the first sync starts.

Credential requirements differ materially between providers — scopes, key types, environments and console paths are not the same twice. Open the connector's manual from the table above for the exact fields before you start.

Two providers are exceptions to step 1: Stripe's Webhook Endpoints scope and Braintree's report-creation and webhook-management role rights are write-capable, and Athia uses them only to create the reports and webhook endpoints it then reads. No connector credential carries permission to authorize, capture, refund or void a payment.

Operational reference

• Status — ACTIVE, PAUSED or ERROR. The Connections list shows the last successful sync per connection.
• Scope — create one connection per provider account or MID, each with its own credential, and name it so the source is obvious later.
• Amount formats — minor units on Stripe, PPRO and the Checkout.com Payments API; decimal on Adyen, Braintree, PayPal Direct and Checkout.com reconciliation reports. To convert a minor-unit amount, scale it by the currency's ISO 4217 exponent rather than always dividing by 100: the exponent is 2 for USD, BRL and MXN, but 0 for CLP, COP and JPY, which have no minor unit and are already whole amounts. Athia normalizes amounts on ingest, so this matters when you reconcile Athia against a raw provider export.
• History — Stripe caps historical sync at one year. PPRO is forward-only with no historical replay, so connect it early. For anything older than a connector will replay, load the period as files — see Integrating Athia.

Cadence and historical reach belong to the provider

Two things decide how fresh your data can be and how far back it reaches, and neither of them is a setting inside Athia. The first is what the provider supports: its API, its report schedule, how much history it will return, and whether it pushes events at all. The second is the nature of the data itself. Authorizations, declines and captures are produced as they happen, so they can be near real time wherever the provider pushes or exposes them. Settlement, payout, fee and interchange data does not exist until the provider closes a batch, runs a reconciliation cycle or issues a statement, so it arrives daily, weekly or monthly by nature — some scheme and network fee data is monthly by design.

The Schedule you pick — Every 1 Minute, 5 Minutes, 15 Minutes, 30 Minutes, 1 Hour, 2 Hours, 3 Hours, 6 Hours, 8 Hours, 12 Hours or 24 Hours — is therefore a ceiling on how often Athia asks, not a floor on how fresh the answer is. Asking faster than the source produces data adds load and no information. EBANX, PPRO, Worldpay and Amex have no Schedule field at all; for Worldpay and Amex, delivery follows the provider's own daily file schedule, so there is no interval to choose.

What each provider actually supports, and how far back it reaches, is in that provider's manual.

If your provider is not listed

Send the same data as files over SFTP or S3, or from your warehouse. See Integrating Athia.

Troubleshooting