Checkout.com

Checkout.com is a self-serve connector and the strongest cost source in the catalog. It draws on two things at once: payment details from the gateway, and reconciliation reports that decompose what each transaction actually cost you. Enable the reports first, or you get the payments half and none of the cost half.

What you get

Payments and their actions with outcomes, disputes, payouts, and reconciliation detail covering fees and FX. Field-level definitions live in Athia Data Dictionary.

Strongest for fee decomposition. Of all the card providers, Checkout.com breaks cost down furthest — interchange, scheme fees, gateway fees, network-token fees, chargeback fees and FX all arrive separately, which is what makes true cost per approved order possible rather than estimated.

Weakest for consistency of units. Payments come in minor units, reconciliation reports in decimals.

Before you start

1. Enable reconciliation reports on the Checkout.com side. Until they are switched on, cost data will not appear however the credential is scoped.

2. Create the Access key pair. In the Hub, go to Developers → Keys → Create a new key. The credential is an Access key ID plus an Access key secret; Athia needs both.

3. Select Custom Scopes and the full scope set. Enable at minimum the gateway, vault and reports scope families. gateway:payment-details (payment and action detail) and reports:read (reconciliation reports) must be included, but they are not the complete list — that pair does not cover the balance, payout and financial-action report data Athia ingests, and a narrow scope set produces HTTP 401 errors rather than partial data.

4. Select the entity the key covers. The Entity Id is what separates one entity's connection from another's.

5. Choose the environment explicitly. A Test account maps to Sandbox; a Live account maps to Production. A key from the wrong environment verifies and then carries nothing you recognize.

Credentials Athia asks for

Setting up the connection

1. Enable reconciliation reports, set Allow any processing channel to ON, and create the Access key pair with Custom Scopes and the full scope set, for the right entity and environment.
2. In Settings → Connections, choose + Add Connection and select Checkout.com.
3. On Configure Connector, enter a Name and pick a Schedule.
4. On Enter Credentials, enter the Access Key Id, Access Key Secret and Entity Id.
5. Choose Verify Connection.

The connection then shows as ACTIVE and the first sync starts. If you operate several entities, create one connection per entity — Entity Id is what separates them.

Register the Athia webhook

Payment and dispute events reach Athia in real time through a Checkout.com workflow.

1. In the connection wizard, copy the Athia Webhook Destination URL.
2. In the Hub, go to Settings → Workflows → Create Workflow.
3. Select the events payment_captured, payment_approved and dispute_created.
4. Add a webhook action and paste the Athia Webhook Destination URL.
5. Configure the signature header, then test, save and enable the workflow.

Sync cadence

This connection has two clocks: payment details update as transactions happen, while reconciliation reports follow Checkout.com's slower reporting cycle. Cost data will not get fresher than that cycle whatever schedule you choose.

Limits and things to know

• Mixed amount units. Payments API amounts are minor units (divide by 100); reconciliation report amounts are decimal. Athia normalizes on ingest, but check which source a figure came from before concluding it is wrong.
• Reports must be enabled first, or the fee decomposition this connector is best at is not there.
• The full scope set is needed. Create the key with Custom Scopes covering at least the gateway, vault and reports families. gateway:payment-details and reports:read alone do not cover balance, payout and financial-action report data, and a narrow scope set returns HTTP 401 rather than partial data.
• Card data is minimized.

Troubleshooting

Related

Other providers and ingestion paths are listed in Athia Connectors. For file drops and warehouse-to-warehouse alternatives to a direct connector, see Integrating Athia.