#gringo_code
1 messages ยท Page 1 of 1 (latest)
๐ 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/1359510149915607271
๐ 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.
- gringo_connect-subscriptions-migration, 1 day ago, 89 messages
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
req_r5HwYmlPX5AChQ
thanks
can you try passing transfer_data[amount_percent] as an empty string
otherwise it won't be removed
it didn't work either
request ID please
no you need to send "" empty string
OK
will try
message: 'Invalid decimal: ',
param: 'transfer_data[amount_percent]',
body.transfer_data = {
destination: 'acct_1PufKUP43Xs4ABvw',
amount_percent: ""
}
req_EAccT1VsSNabLH
Hi there ๐ jumping in as my teammte needs to step away soon. I'm taking a closer look at that request.
ok, I did what he said, for removing application_fee_percent works, but to removing amount_percent don't
I see, and just making sure I'm understanding the situation correctly. You're able to accomplish what you're hoping, but right now it's taking two requests instead of one? One request to unset transfer_data.amount_percent, then a second request to set application_fee_percent. Am I understanding correctly?
exactly
I tried send "" and undefined on transfer_data.amount_percent
but neither worked
Gotcha, but only when trying to do both at the same time?
I'm going to work on reproducing on my side, and then raise this to the appropriate team for further investigation as long as I'm able to see this behavior as well.
yes, only if I try to do both
but when I tried to do both on reverse it worked (remobing applicationfee and adding amount_percent) I did this test to test again
Gotcha, thank you for that clarificatiion. I'll investigate this further and get it to the right team to continue that investigation. Thanks for taking the time to raise this to us!
No, it should accept an empty string the way the rest of our parameters do. Undefined values are typically dropped by our SDK and not included in the requests it generates.
yes, but in this case it doesn't work
I believe the reason is that because it's an object
if I send transfer_data: "" probably will clean
sending a new object on transfer_data was supposed to rewrite
Can you share the ID of a request where you were able to successfully unset transfer_data.amount_percent? I'm not able to reproduce that so far and want to compare what I'm doing to the requests you made that successfully unset that parameter.
here: req_HA57l0axwRS0ZH
sorry for the delay
{
"on_behalf_of": "acct_1PufKUP43Xs4ABvw",
"transfer_data": {
"destination": "acct_1PufKUP43Xs4ABvw"
}
}
Ah, you just omitted it, interesting. Did you see that actually change the value on the Subscription object? That's a bit unexpected to me.
yes, because it override the previous transfer_data
and after this I did other request to add the percentage_fee
and it works
req_oMePJjQeHiDQxT
but if you try it together, don't
Gotcha, thanks for the clarification. That's unexpected behavior for our API and I'll get that flagged to the right team.