#RaviM
1 messages · Page 1 of 1 (latest)
pi_3N8PcbCzmmNEKqHf1iHe7L3m
This doesn't seem to be a Connect payment
i am honestly new, can you help in identifying the connect payment by providing some identifiers ?
What are you trying to do?
Ok to give you some backgrounds we were unable to transfer funds to connected stripe accounts (Outside of US) as we are using standard stripe connect accounts, so after different discussion we decided to upgrade to express stripe accounts.
So am upgrading our service to use stripe express connect account’s using Oauth ( already using with O-auth for standard accounts). I’ve tried and tested it in test env’s and able to create express accounts successfully and the overall flow was working.
How are you creating charges?
But i cant test that wether we will be able to send funds internationally in lower env so just wanted to make sure that apart for upgrading the base URL and enabling Oauth for express in platform setting, is there anything else i need to change
For express accounts it's best to use destination charges: https://stripe.com/docs/connect/destination-charges
What do you mean by "upgrading the base URL"?
thats what i am seeking, is it done at the code level or Configuration level ?
I'm sorry, but I don't follow at all. Where did you get these steps from?
can you please just let me know that charges are to be configured at code level or its something we configure in stripe account ??
may be i'll be able to phrase my question a bit better
charges are to be configured
What do you mean by this?
Do you mean whether payments are created with code?
If you're asking how to specify where to direct the transfers for connect payments, it's done via transfer_data.destination parameter when you create a PaymentIntent: https://stripe.com/docs/connect/destination-charges
cool, yeah it started making sense to me know, we are making destination charges
However, this PI isn't a destination charge.
Please, let me know if you have any other questions.