Data Overview

Coupler.io gives you access to 30 Stripe entities covering the full payment lifecycle — from the moment a customer is created through charges, invoices, payouts, and disputes. This page explains what data is available and how to make the most of it.

Entities at a glance

Entity	Best used for
Balance transactions	Reconciling all money movement in your account
Charges	Analyzing payment success rates and volumes
Customers	Building customer lists and segmenting by behavior
Disputes	Tracking chargeback rates and outcomes
Invoices	Revenue reporting and AR aging
Invoice items	Detailed line-item revenue breakdown
Payment intents	Funnel analysis from intent to successful payment
Payouts	Reconciling Stripe payouts with bank statements
Refunds	Monitoring refund rates by product or period
Subscriptions	MRR, churn, and subscription lifecycle reporting
Subscriptions with line items	Detailed MRR breakdown by plan and add-on
Plans / Prices / Products	Catalog reporting and pricing analysis
Events	Audit trail and webhook-equivalent event history
Connected accounts	Platform-level reporting across multiple merchants
Application fees	Platform revenue from connected accounts
Transfers	Tracking fund flows to connected accounts
Quotes	Sales pipeline and proposal tracking
Promotion codes / Coupons	Discount usage and effectiveness reporting
Issuing transactions	Spend tracking for issued cards
Tax rates	Compliance and tax reporting
Top-ups	Manual balance management tracking

Key fields by entity

Charges

Field	Description
id	Unique charge identifier
amount	Charge amount in the smallest currency unit (e.g., cents)
amount_captured	Amount actually captured
amount_refunded	Total amount refunded
currency	Three-letter ISO currency code
status	succeeded, pending, or failed
customer	ID of the associated customer
payment_intent	Linked payment intent ID
created	Unix timestamp of charge creation
description	Charge description
failure_code	Reason for failure if status is failed
dispute	Dispute ID if a dispute exists

Subscriptions

Field	Description
id	Subscription ID
status	active, canceled, trialing, past_due, unpaid, paused
customer	Associated customer ID
current_period_start	Start of the current billing period
current_period_end	End of the current billing period
canceled_at	Timestamp of cancellation, if applicable
trial_start / trial_end	Trial period boundaries
items	Line items (use Subscriptions with line items for expanded detail)

Balance transactions

Field	Description
id	Transaction ID
amount	Gross transaction amount
fee	Stripe fee deducted
net	Net amount after fees
type	Transaction type (charge, payout, refund, etc.)
source	ID of the source object (e.g., charge or payout)
available_on	Date funds become available in your balance
currency	Currency of the transaction

Invoices

Field	Description
id	Invoice ID
customer	Customer ID
amount_due	Total amount due
amount_paid	Amount already paid
status	draft, open, paid, void, uncollectible
due_date	Invoice due date
subscription	Linked subscription ID
period_start / period_end	Billing period covered

Payouts

Field	Description
id	Payout ID
amount	Payout amount
arrival_date	Expected bank arrival date
status	paid, pending, in_transit, canceled, failed
destination	Bank account or card receiving the payout
description	Payout description

Useful entity combinations

• Payouts + Balance transactions — Use the Join transformation to match each payout with its underlying transactions. This is the most reliable way to reconcile what landed in your bank with individual charges and fees.

• Subscriptions + Customers — Join on the customer field to add customer metadata (email, name, location) to your subscription records for CRM-style reporting.

• Charges + Refunds — Append or join to calculate net revenue after refunds per period.

• Invoices + Invoice items — Combine for a full line-item breakdown of billed revenue.

Use cases by role

Finance teams

• Reconcile Stripe payouts against bank statements using Balance transactions

• Build an AR aging report from Invoices filtered by status = open

• Track net revenue by period using Charges minus Refunds

• Export Tax rates and Invoice items for VAT or sales tax compliance reporting

Growth & Marketing

SaaS & Product teams

Platform operators

Platform-specific notes

• All amounts in Stripe are in the smallest currency unit (e.g., cents for USD). Divide by 100 to get the display amount in your spreadsheet or BI tool.

• Timestamps are returned in UTC. If you need a different timezone (e.g., PST), you'll need to apply a conversion formula in your destination.

• The Quotes entity does not support date range filtering — Created after and Created before are not available for that entity.

• For Balance transactions, you can filter by transaction type (e.g., Charge, Payout, Refund) to pull only the subset you need.

• For Events, use the event type filter with a wildcard (e.g., customer.*) to pull a category of events without specifying each one individually.

• The Subscriptions entity defaults to returning only active subscriptions. To include canceled or other statuses, set the Status parameter explicitly.