#jacobsimon

1 messages · Page 1 of 1 (latest)

slate valeBOT
buoyant bridge
#

Hi there

#

Yeah this data is in the Checkout Session object line_items

#

I'm not sure if this is in the Sigma schema

#

But you can get this data by listing Checkout Sessions and expanding line_items

#

Mostly I would encourage you to ingest this data each time a Session is completed and store it in your own database

rare terrace
#

Gotcha, yeah we do store a mirror of our catalog and transactions on our side but it's not exactly 1-1 / doesn't reflect our recurring purchases so it's only half the picture so to speak.

#

Is the sigma schema published anywhere btw?

#

Thanks for the speedy reply

#

As a stopgap right now we are also storing a description on the "payment_intent.description" field to help us filter payments, but it's not great because it wouldn't support checkout sessions with >1 product and won't help retroactively

wispy siren
#

And is line_items different from invoice_line_items? I found that unless the checkout included a subscription (which would have an invoice), the one-off line item charges do not appear in the invoice_line_items table since there is no associated invoice.

buoyant bridge
#

Let me check on where the public Sigma schema is

#

Definitely wouldn't rely on the description field -- you want the line_items which will be present for both one-off and recurring Sessions

wispy siren
#

Got it - we're currently using Stitch to pipe the Stripe data into our warehouse, but I don't see the line_items table here nor in Sigma. Do you know if the line_items table is accessible via the Stipe data pipeline?

buoyant bridge
#

I'm not sure about the data pipeline stuff as I just focus on the API

wispy siren
#

Ah ok, thanks! And yeah, based on that link, you're right - it does not look like line_items is part of the Stripe schema.