Skip to content
Connection Guide

Connect Checkout.com Without Breaking the Audit Trail

Use this guide to connect Checkout.com or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryPayments / PCI
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Checkout.com and make sure the first collection lands cleanly.

  1. 1
    Create a dedicated Checkout.com secret API key and scope it to reports:view and flow:workflows.
  2. 2
    Store the API key securely and configure the merchant-specific API base URL.
  3. 3
    Validate workflow reads and report file downloads before enabling scheduled sync.
  4. 4
    Keep broader IAM and event surfaces out of scope unless the package expands.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

api_key

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.