#nukesforbreakfast_best-practices

1 messages · Page 1 of 1 (latest)

white wigeonBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1417229617609052200

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

mental flare
#

Hello
Yes, Credit notes are the recommneded approach in this case - as far as I know

pale panther
#

Is there any reason to not credit the full amount over or under billed on the line item and create an entirely new pending line item?

mental flare
#

Not sure? Our team on discord isn't generally familiar with reconciliation process of our users as all have different preferences.

So I can't think of an immediate reason on why that's not the preferred route but I'd say if you test both in test mode then you'd likely see the difference (if any)

white wigeonBOT
pale panther
#

ok, sounds good to me.

#

BTW, I ran into an issue where the subscription schedule's API doesn't support passing the pending_invoice_item_interval argument anywhere. Is there a feature request open for adding that parameter? Right now I have to create the subscription schedule, then update the underlying subscription to set pending_invoice_item_interval to what I want.

soft plank
#

I am not seeing an existing request but I am happy to file one

pale panther
#

that would be great

soft plank
#

Filed! I actually did find an existing request when double checking and added to that

pale panther
#

do you guys provide support for private betas here or is that soley through support.stripe.com?

soft plank
#

We typically only know of things that are generally released so support.stripe.com is the best way to go there. That said, I am happy to take a quick look now before you file via support.stripe if you would like

pale panther
#

I already have a long lived thread going, but it seems to have gotten muddled and is taking a long time to get a response. If you can't help with the below then don't worry about opening another support ticket, I'll wait for them to respond to the one already there:

#

I tested the behavior in my account and noticed I'm still having an issue. I'm trying to create a single payment record and split it across multiple invoices using the amount_requested argument to the attach_payment call. However, the attempt to attach the payment to the second invoice is failing with the error:

"This PaymentRecord is already attached to in_1S74b4BtIpo4XHMmfCmXivGK, and can’t be attached to more than one invoice."

The errored request ID is req_mj26z1vdaiQ9d8

How do I attach a single payment record to multiple invoices to indicate a single out-of-band payment split over multiple invoices?

soft plank
#

I am not finding a way to do this, so I think keeping with the current thread is the best way forward. As best I can tell we don't current support splitting one payment record (or even a payment intent) across multiple invoices and I'm not seeing an obvious workaround.

white wigeonBOT
pale panther
#

Ok thanks for checking.

white wigeonBOT