Skip to main content
This integration is currently in beta and the exact mapping of fields might still change.

Configuration

Settlement reporting for Checkout.com uses the SettlementBreakdown report, which Gr4vy retrieves automatically through the Checkout.com Reporting API (REST). Unlike some other integrations, you do not need to set up SFTP access; Gr4vy fetches the report using the API credentials you already configured on the connector. To enable settlement reporting, go to the “Connections” tab, select the Checkout.com connector, and then open the “Settlement” tab. Enable settlement reporting on this tab.

Enabling the report generated webhook

Report ingestion is triggered by Checkout.com’s report_generated webhook: each time Checkout.com issues a SettlementBreakdown report, it notifies Gr4vy, which then fetches and ingests the corresponding SettlementBreakdown report. Enable this webhook in the Checkout.com Dashboard:
  1. In the Gr4vy dashboard, go to Connections, select your Checkout.com connection, open the Synchronization tab and copy the webhook URL. This is the same endpoint used for your Checkout.com transaction webhooks.
  2. In the Checkout.com Dashboard, go to Developers -> Webhooks.
  3. Edit the existing webhook configuration that points to Gr4vy. If you have not registered it yet, first complete the Checkout.com webhook setup, including saving its signature key in your Gr4vy connection.
  4. Confirm that the Endpoint URL matches the Gr4vy webhook URL and uses HTTPS.
  5. Enable Report -> Report generated while preserving the existing payment event selections.
  6. Select Save changes.
The report_generated webhook is delivered to the same endpoint as your Checkout.com transaction webhooks, so any security header already configured for the connector applies to it as well.

Fields mapping

Below is the mapping of Checkout.com’s settlement report to the consolidated settlement report. This data is pulled from the Checkout.com SettlementBreakdown report.

Journal type mapping

Fields marked as not being a Checkout.com field are populated from internal data and not from the imported payment service report.