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

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

Support teams

Product & growth

---

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