Question 1

What can be written into Stripe?

Accepted Answer

Customers, invoices and subscriptions, with different freedom on each. Customers are the most open, taking create, update, and create or update. Invoices can be written but require a customer to be mapped, since an invoice cannot exist without one. Subscriptions accept updates only, which is deliberate: creating a subscription changes what somebody is billed, so that stays a decision made in Stripe rather than something a scheduled sync performs.

Question 2

How are Stripe records matched?

Accepted Answer

On the Stripe object identifier, on email, or on a metadata key, and the choice matters more than it looks. Email is not unique in Stripe, so if several customers share one the sync updates all of them, and matching subscriptions by customer identifier updates every subscription that customer has. Metadata matching runs through Stripe Search, adding a lookup per record and subject to index propagation delay. For a large table the Stripe identifier is safest and fastest.

Question 3

Where do custom fields end up?

Accepted Answer

In Stripe metadata, which is where Stripe expects data it does not model natively. Customer metadata suits customer level traits such as an internal account identifier, plan tier or health score, while subscription metadata suits attributes specific to a subscription. Individual metadata keys can be mapped rather than writing the whole object. Keep anything Stripe should enforce, such as pricing, out of it.

Question 4

Why sync a warehouse into billing?

Accepted Answer

Usually to close the identity gap. Stripe knows who pays and what they pay, while Redshift knows which account that maps to, what plan they should be on, and how the product is actually being used. Writing that context onto the customer means anyone in Stripe can see it and reconciliation stops depending on matching email addresses by hand. Reads run incrementally once a tracking field and primary key are set.

Question 5

How do I sync Redshift to Stripe?

Accepted Answer

Connect Redshift with cluster details, credentials and an S3 staging bucket, over an SSH tunnel if the cluster is private, and connect Stripe with a secret API key. The key determines whether you are working against test or live data, and the two are separate datasets, so validating mappings against a test key first is worth doing. Then model the data, choose customers, invoices or subscriptions, and map an identity field.

Connect Redshift with Stripe

Connect Redshift and Stripe with Polytomic

Metadata as the join key

Full upsert on customers

Scoped writes elsewhere

Trusted by businesses worldwide

Step-by-step integration guide

Connect Redshift in Polytomic

Connect Stripe in Polytomic

Create a sync between Redshift and Stripe

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Redshift with Stripe?