You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/cloud-apps/stripe/index.md
+81-55Lines changed: 81 additions & 55 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,11 +44,17 @@ Collections are the groupings of resources we pull from your source. In your war
44
44
|`invoice_items`| object | Sometimes you want to add a charge or credit to a customer but only actually charge the customer's card at the end of a regular billing cycle. This is useful for combining several charges to minimize per-transaction fees or having Stripe tabulate your usage-based billing totals. For more info, see [Stripe's API docs](https://stripe.com/docs/api#invoiceitems)|
45
45
|`invoice_lines`| object | When retrieving an invoice, you'll get a lines property containing the total count of line items and the first handful of those items For more info, see [Stripe's API docs](https://stripe.com/docs/api#invoice_lines)|
46
46
|`invoices`| object | Invoices are statements of what a customer owes for a particular billing period, including subscriptions, invoice items, and any automatic proration adjustments if necessary. For more info, see [Stripe's API docs](https://stripe.com/docs/api#invoices)|
47
+
|`orders`| object ||
48
+
|`order_returns`| object ||
49
+
|`order_shipping_methods`| object ||
47
50
|`payment_intents`| object | A PaymentIntent tracks the process of collecting a payment from your customer. A PaymentIntent transitions through multiple statuse throughout its lifetime and ultimately creates at most one successful charge. For more info, see [Stripe's API docs](https://stripe.com/docs/api/payment_intents)|
48
51
|`payment_methods`| object | PaymentMethod objects represent your customer's payment instruments. They can be used with [PaymentIntents](https://stripe.com/docs/payments/payment-intents) to collect payments or saved to Customer objects to store instrument details for future payments. For more info, see [Stripe's API docs](https://stripe.com/docs/payments/payment-methods)|
49
52
| plans | object | A subscription plan contains the pricing information for different products and feature levels on your site. For more info, see [Stripe's API docs](https://stripe.com/docs/api#plans)|
50
53
| refunds | object | Refund objects allow you to refund a charge that has previously been created but not yet refunded. Funds will be refunded to the credit or debit card that was originally charged. The fees you were originally charged are also refunded. For more info, see [Stripe's API docs](https://stripe.com/docs/api#refunds)|
54
+
|`products`| object ||
55
+
|`skus`| object ||
51
56
|`subscriptions`| object | Subscriptions allow you to charge a customer's card on a recurring basis. A subscription ties a customer to a particular plan you've created. For more info, see [Stripe's API docs](https://stripe.com/docs/api#subscriptions)|
57
+
|`subscription_items`| object ||
52
58
|`transfer_reversals`| object | A previously created transfer can be reversed if it has not yet been paid out. Funds will be refunded to your available balance, and the fees you were originally charged on the transfer will be refunded. You may not reverse automatic Stripe transfers. For more info, see [Stripe's API docs](https://stripe.com/docs/api#transfer_reversals)|
53
59
|`transfers`| object | When Stripe sends you money or you initiate a transfer to a bank account, debit card, or connected Stripe account, a transfer object will be created. You can retrieve individual transfers as well as list all transfers. For more info, see [Stripe's API docs](https://stripe.com/docs/api#transfers)|
54
60
@@ -279,6 +285,46 @@ Below are tables outlining the properties included in the collections listed abo
279
285
|`type`| A string identifying the type of the source of this line item, either an `InvoiceItem` or a `Subscription`|
280
286
|`item_id`| If id is prefixed with `ii_` then this is the line item's UUID, if any |
@@ -391,58 +472,3 @@ Below are tables outlining the properties included in the collections listed abo
391
472
|`reversed`| Whether the transfer has been fully reversed. If the transfer is only partially reversed, this attribute will still be false |
392
473
|`source_transaction`| ID of the charge or payment that was used to fund the transfer. If null, the transfer was funded from the available balance |
393
474
394
-
## V2 Changelog
395
-
In September 2017, Segment will upgrade all Stripe sources to sync incrementally, using the [List Events](https://stripe.com/docs/api#list_events) endpoint to sync changes to Stripe objects. There are a few benefits to this approach…
396
-
397
-
-**Faster sync times:** for larger accounts, we've seen performance improve by 10x
398
-
-**Additional Object Properties:** Events provide additional metadata about objects, like their creation time and deletion time
399
-
-**Reduced load on the Stripe API:** Our new Stripe source helps cut down load on our partner's API, and reduces unnecessary data transfer
400
-
401
-
### How It Works
402
-
1. The Stripe Source will run a full sync of all objects, using the `List All` endpoints for `Charges`, `Customers`, `Refunds`, etc.
403
-
2. After the first sync completes, the source will automatically switch into incremental mode.
404
-
1. When the source is scheduled to run, it will query for all events since the last sync completed. An event can be an object (e.g. a customer) being `created`, `updated`, or `deleted`
405
-
2. The Segment source will materialize the event stream into the latest state of the object. So the `charges` table will always reflect the latest `charge.updated` event.
0 commit comments