#oscadev_best-practices

1 messages ¡ Page 1 of 1 (latest)

jovial flintBOT
#

👋 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/1363948558939721899

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

swift sleet
#

Hello
Give me a moment to take a look

worthy finch
#

I guess then, a follow up question is, is there a way to not have to expand "payments"? We dont intend to allow partial payments (ie each weekly payment must be paid in full)

#

Like when I subscripe to an iPhone app, it just takes what is due all together, not in pieces of partial payments

swift sleet
#

is there a way to not have to expand "payments"?
Unfortunately, no. The latest API version does not have a root level parameter that can be used for this.

worthy finch
#

ok, so I can do math on the "payments", or I can make an API call to Invoice Payment. Thanks!

#

all the docs and chatGTP answers I could find were telling me to use the "charge" id, on the invoice object, but there was no such thing. Thanks