Common Issues

Connection issues

I can't connect an additional Stripe account

Coupler.io supports multiple Stripe credentials, but each account must be authorized separately. When adding a second account, make sure you're logged into the correct Stripe account in your browser before clicking Connect — otherwise OAuth may reuse the first account's session.

If the connection still fails, try opening an incognito window, log into the correct Stripe account, and then complete the OAuth flow from there.

The Stripe API request keeps failing

This usually means Stripe returned an error on its end. Check the error message in the data flow log — common causes include an expired or revoked OAuth token, or a permissions issue with the connected account.

Try disconnecting and reconnecting your Stripe credential in Coupler.io. If the error persists, check the Stripe Dashboard to confirm your account is in good standing and that API access is enabled.

Missing data

My Stripe subscriptions data is incomplete or missing records

The Subscriptions entity returns only active subscriptions by default. If you need canceled, trialing, past_due, or all statuses, set the Status parameter to the value you need — or leave it blank/set it to "all" to retrieve every status.

Also check your date range filters. If you've set a "Created after" date, subscriptions created before that date won't appear even if they're still active.

The Charges entity isn't pulling all my data

First, confirm your Created after and Created before date range covers the period you expect. Remember that Stripe timestamps are in UTC — if you're in a different timezone, your date boundaries may be cutting off records at the edges.

If the date range looks correct, check whether you have a large volume of charges. Very large datasets can cause timeouts (see Rate limits section below).

Products or Prices data doesn't match what I see in the Stripe Dashboard

The Products entity in Coupler.io reflects what's returned by the Stripe API, which may differ slightly from the Dashboard view if you have archived products. Archived products may not appear by default — check if there's a status filter applied or if you need to use the Advanced filters field to include archived records.

Permission errors

I'm getting a permissions error when connecting Stripe

You need admin or developer access in Stripe to authorize the OAuth connection. Restricted keys or team members with limited roles may not be able to grant the required read permissions.

Ask your Stripe account owner to complete the OAuth authorization, or ask them to upgrade your role in Stripe before you try again.

Connected accounts data is empty or returning an error

The Connected accounts entity requires that your Stripe account is set up as a platform using Stripe Connect. Standard merchant accounts won't have connected accounts data. If you're a platform, confirm that your OAuth token was granted with the read_only scope at the platform level, not just a connected account level.

Data discrepancies

Amounts in Coupler.io don't match what I see in the Stripe Dashboard

Stripe returns all monetary amounts in the smallest currency unit — cents for USD, pence for GBP, etc. The number 5000 in Coupler.io means $50.00, not $5,000. Divide the amount column by 100 in your destination to get the correct display value.

My payout amounts don't match individual transactions

A single payout covers many underlying balance transactions. To reconcile them, use a data flow that includes both the Payouts and Balance transactions entities, then use the Join transformation on the payout ID. This gives you a row-level breakdown of exactly which charges, fees, and refunds make up each payout.

Rate limits and timeouts

My data flow times out when pulling Invoices, Charges, or Subscriptions

This is the most common issue for accounts with large transaction volumes. Stripe's API paginates large datasets, and pulling hundreds of thousands of records in one run can exceed the timeout limit.

The best fix is to use the Created after and Created before date pickers to narrow the date range. Instead of pulling all-time data in one run, pull data in smaller windows — for example, the last 90 days — and use incremental runs going forward.