> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/finance-and-accounting/chargedesk.md).

# Chargedesk

Connect Chargedesk to Coupler.io to pull charges, customers, subscriptions, and products into Google Sheets or data warehouses with automatic refreshes.

Chargedesk is a payment management platform that centralizes billing operations across multiple payment gateways like Stripe, PayPal, Braintree, and others. It gives support and finance teams a unified view of charges, subscriptions, customers, and products without needing to switch between payment processors.

Connecting Chargedesk to Coupler.io lets you pull your billing data into spreadsheets, dashboards, or data warehouses — and keep it automatically refreshed.

**Why connect Chargedesk to Coupler.io?**

* Export charges, customers, subscriptions, and products into Google Sheets, Excel, BigQuery, or Looker Studio
* Combine Chargedesk data with your CRM or marketing data using Join or Append transformations
* Send billing snapshots to AI tools like ChatGPT, Claude, or Gemini for revenue analysis
* Automate recurring exports so your reports are always up to date

## Prerequisites

* A Chargedesk account with API access
* Your Chargedesk API key (found in your Chargedesk account settings under **API / Webhooks**)

## Quick start

{% hint style="success" %}
If you want a combined view of revenue trends, start with the **Charges** and **Subscriptions** entities in a single data flow and use the Append or Join transformation to merge them.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Go to your Coupler.io workspace and click **Add data flow**. Search for **Chargedesk** and select it as your source.
{% endstep %}

{% step %}
**Enter your Chargedesk API key.** In the source settings, paste your API key into the API key field. You can find this key in Chargedesk under **Settings → API / Webhooks**.
{% endstep %}

{% step %}
**Select an entity.** Choose which data you want to pull: Charges, Customers, Subscriptions, or Products. You can add more sources to the same data flow later.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to specify how far back the sync should go. This controls the earliest records that will be included.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your Chargedesk data will appear in your chosen destination.
{% endstep %}
{% endstepper %}

## Chargedesk data overview

Chargedesk exposes four main entities through Coupler.io. Each maps to a core part of your billing operation — transactions, customers, recurring plans, and product catalog.

## Entities

| Entity        | Description                                                       |
| ------------- | ----------------------------------------------------------------- |
| Charges       | All payment attempts and their outcomes across connected gateways |
| Customers     | Profiles of everyone who has been charged or subscribed           |
| Subscriptions | Active, canceled, and past recurring billing agreements           |
| Products      | Products and pricing tiers set up in Chargedesk                   |

***

#### Charges fields

| Field        | Description                                            |
| ------------ | ------------------------------------------------------ |
| charge\_id   | Unique identifier for the charge                       |
| amount       | Transaction amount                                     |
| currency     | Currency code (e.g., USD, EUR)                         |
| status       | Charge outcome: succeeded, failed, refunded, disputed  |
| gateway      | Payment gateway used (Stripe, PayPal, Braintree, etc.) |
| customer\_id | Linked customer identifier                             |
| created\_at  | Timestamp of the charge                                |
| description  | Charge description or product label                    |
| refunded     | Whether the charge was refunded                        |
| dispute      | Whether the charge is under dispute                    |

#### Customers fields

| Field          | Description                               |
| -------------- | ----------------------------------------- |
| customer\_id   | Unique customer identifier                |
| name           | Customer full name                        |
| email          | Customer email address                    |
| created\_at    | Date the customer record was created      |
| gateway        | Gateway associated with the customer      |
| total\_charges | Number of charges linked to the customer  |
| total\_spend   | Cumulative amount charged to the customer |

#### Subscriptions fields

| Field               | Description                                          |
| ------------------- | ---------------------------------------------------- |
| subscription\_id    | Unique subscription identifier                       |
| customer\_id        | Linked customer identifier                           |
| status              | Current state: active, canceled, past\_due, trialing |
| plan\_name          | Name of the subscribed plan                          |
| amount              | Recurring billing amount                             |
| currency            | Currency code                                        |
| billing\_interval   | Billing frequency (monthly, yearly, etc.)            |
| started\_at         | Subscription start date                              |
| canceled\_at        | Cancellation date if applicable                      |
| next\_billing\_date | Upcoming renewal date                                |

#### Products fields

| Field             | Description                       |
| ----------------- | --------------------------------- |
| product\_id       | Unique product identifier         |
| name              | Product name                      |
| description       | Product description               |
| price             | Default price                     |
| currency          | Currency code                     |
| billing\_interval | Billing frequency for the product |
| created\_at       | Date the product was created      |

***

## Common field combinations

* **Charges + Customers** — Join on `customer_id` to see how much each customer has spent and their charge history
* **Subscriptions + Customers** — Join on `customer_id` to track which customers are on which plans and identify churn risk
* **Charges + Subscriptions** — Append or Join to build a full revenue picture that covers both one-time and recurring revenue
* **Charges grouped by gateway** — Aggregate charges by `gateway` to compare performance across payment processors

***

## Use cases by role

{% tabs %}
{% tab title="Finance teams" %}

* Export all charges into Google Sheets or Excel for monthly revenue reconciliation
* Use the Aggregate transformation to calculate MRR and ARR from the Subscriptions entity
* Monitor failed and disputed charges by filtering the Charges entity by `status`
* Send subscription data to BigQuery for long-term retention and trend analysis
  {% endtab %}

{% tab title="Support teams" %}

* Pull customer and charge data into a shared Google Sheet so support agents can quickly look up billing history
* Track customers with `past_due` subscriptions to prioritize outreach
* Use the Join transformation to combine customer profiles with their full charge history in one view
  {% endtab %}

{% tab title="Product & growth" %}

* Analyze product adoption by exporting Products and Subscriptions, then joining on plan details
* Send subscription and churn data to ChatGPT or Claude for AI-assisted cohort analysis
* Use Looker Studio with Charges data to build a live revenue dashboard
  {% endtab %}
  {% endtabs %}

***

## Platform-specific notes

* Chargedesk aggregates data from multiple gateways, so the `gateway` field is important for filtering and segmenting records correctly
* The `start_date` parameter controls how far back historical data is synced — setting this too far back on large accounts can increase initial sync time
* Charge statuses and subscription states reflect what Chargedesk has received from the underlying gateway; small delays between gateway events and Chargedesk records are normal
* Customer and subscription records are linked via `customer_id` — this is the key field to use for Join transformations across entities

## Chargedesk common issues

### Connection issues

<details>

<summary>The API key is not accepted</summary>

Double-check that you copied the full API key from Chargedesk without any leading or trailing spaces. You can find it under **Settings → API / Webhooks** in your Chargedesk account. Also confirm that API access is enabled for your Chargedesk plan — some lower-tier plans restrict API usage.

</details>

<details>

<summary>The data flow fails immediately after setup</summary>

This usually means the API key does not have sufficient permissions or belongs to a user role with restricted access. Try generating a new API key under an admin account and use that instead.

</details>

### Missing data

<details>

<summary>Historical charges are missing from my export</summary>

This is almost always caused by the **Start date** setting. If the start date is set too recently, older records will not be included. Go back to the source settings and use the date picker to move the start date further back, then re-run the data flow.

</details>

<details>

<summary>Some customers or subscriptions are missing</summary>

Chargedesk only surfaces records that exist within its own database — if a customer or subscription was created in a gateway but not synced to Chargedesk, it will not appear. Check your Chargedesk dashboard to confirm the records are visible there first. If they are visible in Chargedesk but missing in Coupler.io, try re-running the data flow.

</details>

<details>

<summary>Refunded or disputed charges are not showing up</summary>

Refunds and disputes update the `status` and `refunded` / `dispute` fields on existing charge records rather than creating new rows. If you are filtering by status, make sure your filter includes these values.

</details>

### Permission errors

<details>

<summary>"Unauthorized" or "403" error during sync</summary>

This means the API key is valid but the associated account does not have permission to access the requested entity. Check your Chargedesk account role and confirm you have access to Charges, Customers, Subscriptions, and Products. If your account uses team permissions, ask your Chargedesk admin to grant API access.

</details>

### Data discrepancies

<details>

<summary>Amounts in Coupler.io don't match what I see in my payment gateway</summary>

Chargedesk pulls data from your gateway and may have a short sync delay before new transactions appear. Additionally, currency conversion or gateway fees are not applied by Chargedesk — the amounts reflect the raw transaction values. For exact reconciliation, always compare against the gateway's own reports.

</details>

<details>

<summary>Subscription status looks outdated</summary>

Subscription statuses in Chargedesk depend on webhook events from your payment gateway. If a webhook was missed or delayed, the status in Chargedesk (and therefore in Coupler.io) may lag behind the actual state. Check your gateway's webhook delivery logs to confirm events are reaching Chargedesk.

</details>

### Rate limits

<details>

<summary>Sync is slow or times out on large accounts</summary>

Chargedesk's API has rate limits that can slow down syncs on accounts with a large volume of charges or customers. If you are hitting slowdowns, try narrowing the **Start date** to reduce the volume of records fetched in each run. For very large datasets, consider splitting entities into separate data flows.

</details>

## Chargedesk FAQ

<details>

<summary>Which payment gateways does Chargedesk support?</summary>

Chargedesk connects to Stripe, PayPal, Braintree, Authorize.Net, Recurly, WooCommerce, and several others. All charges visible in your Chargedesk account — regardless of which gateway processed them — will be available through Coupler.io. Use the `gateway` field to filter by processor.

</details>

<details>

<summary>Can I pull data from multiple Chargedesk accounts into one destination?</summary>

Yes. Add multiple sources within the same data flow — one per Chargedesk account — and use the Append transformation to combine them into a single table in your destination. This is useful if you manage billing for multiple brands or regions under separate Chargedesk accounts.

</details>

<details>

<summary>How do I calculate MRR from Chargedesk data?</summary>

Use the Subscriptions entity and filter for `status = active`. Then use Coupler.io's Aggregate transformation to sum the `amount` field, grouped by `billing_interval`. For monthly plans, that sum is your MRR directly. For annual plans, divide by 12 before adding to your MRR figure.

</details>

<details>

<summary>Can I use Chargedesk data with AI tools?</summary>

Yes. When choosing a destination in Coupler.io, you can select AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, or OpenClaw. This lets you send your charges, subscriptions, or customer data directly to an AI assistant for analysis, anomaly detection, or report generation.

</details>

<details>

<summary>What does the start date control, and can I change it after setup?</summary>

The start date determines the earliest record that will be included in your sync. You can change it at any time by editing the source settings in your data flow. After changing it, run the data flow manually to pull in the updated date range.

</details>

<details>

<summary>Why are some charges showing a "failed" status in my export?</summary>

Failed charges are legitimate records — Chargedesk captures all payment attempts, including unsuccessful ones. This is actually useful for tracking failed payment rates by gateway or customer. If you only want successful transactions, filter the Charges entity by `status = succeeded` in your destination or using Coupler.io's filter settings.

</details>

<details>

<summary>How do I track churn using Chargedesk data?</summary>

Use the Subscriptions entity and filter for `status = canceled`. You can also calculate churn rate by joining Subscriptions with Customers and aggregating cancellations by month using the `canceled_at` field. Send this to Looker Studio or Google Sheets for a visual churn trend.

</details>

{% hint style="info" %}
For a full list of available fields per entity, see [Data Overview](#chargedesk-data-overview). If your sync is returning unexpected results, check [Common Issues](#chargedesk-common-issues) for troubleshooting steps.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/finance-and-accounting/chargedesk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
