When you collect a transaction fee on top of a charge made for your user (using Stripe Connect), an application fee object is created in your account. For more information, see Stripe’s API docs Funds will be refunded to the Stripe account that the fee was originally collected from.

For more information, see Stripe’s API docsĪpplication Fee Refund objects allow you to refund an application fee that has previously been created but not yet refunded. You can retrieve it to see properties on the account like its current e-mail address or if the account is enabled yet to make live charges.

This is an object representing your Stripe account. In your warehouse, each collection gets its own table. CollectionsĬollections are the groupings of resources that Segment pulls from your source. Depending on your Warehouses plan, Segment pushes the Source data to your warehouse on the interval associated with your billing plan. Sources will sync with Segment every three hours. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. The source syncs and warehouse syncs are independent processes. For example, if subscription_status goes from active to inactive between syncs, on its next sync that ticket’s status is inactive. Segment’s sync component uses an upsert API, so the data in your warehouse loaded using sync reflects the latest state of the corresponding resource in Stripe. The objects are written into a separate schema, corresponding to the source instance’s schema name you designated upon creation (for example, stripe_prod.charges). In the initial sync, Segment grabs all the Stripe objects (and their corresponding properties) according to the Collections Table below. The Stripe source is built with a sync component, which means Segment make requests to the Stripe API on your behalf on a three hour interval to pull the latest data into Segment.

Click Connect, and authenticate with Stripe’s OAuth.

The nickname can be whatever you like, but Segment recommends using a name that reflects the source itself and distinguishes amongst your environments. The schema name is the namespace you query against in your warehouse. The nickname is used to designate the source in the Segment interface, and Segment creates a related schema name.

Give the Source a nickname and click Add Source.

In Segment go to Connections and click Add Source.

Stripe builds economic infrastructure for the internet, that enables businesses of every size to accept payments and manage their businesses online. Data from this source can only be exported directly to a warehouse, but it can then be used for further analysis. This means that it sends information (traits) about a thing that exists and persists over time, such as a person or company, and which can be updated over time.

Stripe webook for charge submitted