#marinadinerly_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/1221889757341286431
๐ 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.
- marinadinerly_code, 4 days ago, 40 messages
Okay what are you trying to pass here?
What do you mean?
Can you share the API request ID for this request?
IT's easier to review than C# code
One second
That is the only request ID we are getting when testing this on the test environment but we spoke to support and they couldn't see that on their system Request-Id=req_xBIhXmbSO5afcA Date=2024-03-23T14:49:00
Let me take a look
It is creating a customer but doesn't seem to be able to hit the Payment API properly
Okay I can see it
You are making a direct change and then trying to specify a transfer destination
Which is set to your own account
That's backwards
The error message points this out:
error: {
message: "The 'transfer_data[destination]' param cannot be set to your own account.",
so we should specify a transfer destination first?
WHat kind of charge are you trying to make? Direct or Destination?
Destination charge
You are currently mixing up your syntax between both Direct Charges and Destination Charges. You should review the syntax for Destination Charges here: https://docs.stripe.com/connect/destination-charges
Should I reach back out again when this is fixed
When I go through the code and remove any direct charges code?
Yep we're happy to consult if you have questions about the destination charge flow or if you run in to any problems while trying to make this change
Also can I explain I thing the developer has mixed both charges due to the on_behalf_of code not being support in the ASP.NET 4.5 framework we are working on, do you guys know any way we can combat this?
Happy to help but I don't quite understand what is happening. Can you give me a bit more detail on how this mixup is happening?
I wish I could, the developer is not here at the moment and has asked me to reach out. I have sent out the information you guys have sent us about the direct charges and destination charges, I have asked him to completely remove any code for direct charges and ensure we are only doing destination charges so we can get that sorted, then I will come back with the dev and have a look at the on_behalf_of code when we are sure that our destination charges are okay. Let me know if this makes sense and if I am going about it the right way?
Yep that makes sense to me. And it actually looks like we added support for the on_behalf_of parameter for PaymentIntents before the library required .NET 4.6.1 so you may be able to upgrade to a version of the library that supports that parameter
And even if not I think we have a way to pass additional parameters that the SDK doesn't directly support. I will see if I can find info on that and send it here
Yes please as this is the issue we are currently facing, we are using destination charges already with about 30 restaurant partners, these docs I have sent are just a bit messed up cause we are trying to make the on_behalf_of code work. If you can find anything on that you will be a life saver.
Here we go:
https://github.com/stripe/stripe-dotnet/tree/master?tab=readme-ov-file#parameters
So if the Stripe.net version you are using does not support on_behalf_of, you can set it with the AddExtraParam mehod. That method was added five years ago so as long as you are using a more recent version than that, you should be able to pass this parameter when creating your destination charges
Stripe.net is a sync/async .NET 4.6.1+ client, and a portable class library for stripe.com. - stripe/stripe-dotnet
Awesome thank you so much for that. I have shared it with our devs and will reach out tomorrow with any questions they might have guys. I guess there is no way to keep this channel open so we don't have to rexplain to the new guys the whole process from the beggining right?
This thread will be closed by then but if you explain that you are trying to create these Destination + OBO charges in .NET that should be plenty of context for whoever is on the server at the time