hex.amundo | Stripe Developers | Page 1

granite horizonBOT Jun 28, 2023, 9:44 AM

#

lilac gate Jun 28, 2023, 9:44 AM

#

Hi! Let me help you with this.

#

Could you please share the Subscription ID?

craggy willow Jun 28, 2023, 9:46 AM

#

sure, just one moment

#

sub_1NM9aHIDKv8AAGGkLRvTT75Q

#

When I created the subscription schedule (sub_sched_1NM9WtIDKv8AAGGkllQCQnAs) I added a bit of metadata to the Subscription Schedule Phase Item Options. This metadata correlates back to specific records that I will need to track individual transactional history for. I had been hoping to use the subscription item, but that seems to not be expandable in the API and doesn't seem to be persisted beyond the current subscription (as subscription schedules update subscriptions, the subscription items seem to be deleted).

lilac gate Jun 28, 2023, 9:58 AM

#

Sorry for delay, I'm still looking.

craggy willow Jun 28, 2023, 9:58 AM

#

sure, no rush 🙂

lilac gate Jun 28, 2023, 9:59 AM

#

If the metadata is Subscription-specific, I would recommend storing it on the top level object.

craggy willow Jun 28, 2023, 10:02 AM

#

well, it is specific to the items of the subscription... If I have one instance of "product A" and then another instance of "product A" on the subscription schedule phase (and obv. the subscription and then invoice) I need the metadata to determine which instance of "product A" correlates to a person. Think of the subscription as payment for a class (Product A would be the name of the class) and the items of the subscription would be enrollments into the class (so I need to track if one canceled but the other didn't, etc.)

#

If this isn't a thing that is possible (which I'm thinking not), then I will proceed with my phase item price to invoice line match up, because the phase data does persist my metadata on a line-by-line basis

lilac gate Jun 28, 2023, 10:06 AM

#

I wouldn't rely on the line_item metadata for Subscription Schedules. Could you share more about your use case? Maybe there's a better solution. Is the same person paying who's attending the class?

craggy willow Jun 28, 2023, 10:07 AM

#

no, this would be more like a parent paying for their kids to attend.

#

honestly, if the subscription items were persistent and expandable, this issue would go away because I could just grab the invoices of the subscription and match up on metadata.

#

Thanks for your help, and time, I appreciate it 🙂

lilac gate Jun 28, 2023, 10:14 AM

#

I would map the data to specific attendants in your database instead, and then just change the quantity in the Invoice.
Actually in your case I feel it makes more sense to generate Invoices yourself instead of using Subscription Schedules. But I will need more context to advice better.

#

Happy to help!

craggy willow Jun 28, 2023, 10:15 AM

#

We're in agreement that this approach is cumbersome. "I am working within the confines of my engagement" 😂

lilac gate Jun 28, 2023, 10:20 AM

#

You mean the database approach?

craggy willow Jun 28, 2023, 10:22 AM

#

no, I mean the way I have to do this... I was all "use webhooks and database for speed and efficiency" and they're like "no."

lilac gate Jun 28, 2023, 10:25 AM

#

By "they" you mean your team?

craggy willow Jun 28, 2023, 10:26 AM

#

my client

lilac gate Jun 28, 2023, 10:27 AM

#

Oh, yeah, I understand.

#hex.amundo