#oscar-customerbalance-connect
minor flare
Hey @honest stirrup you just shared your real API key, please make sure to roll this key ASAP: https://stripe.com/docs/keys#rolling-keys
For that code to work all the objects have to exist on the same Stripe account. You can not pass the id of a Customer cus_123 from the platform if you are passing a connected account id in the Stripe-Account header, that won't work
honest stirrup
I am passing the correct key, so how do I implement bank transfer payments and connected accounts using payment intents
minor flare
1/ I know you pass the right API key. What I said is that you leaked it here, it's a public forum, anyone can see your message, you need to roll your API key immediately
2/ You're using Direct Charges which is the flow described in details in our docs here: https://stripe.com/docs/connect/direct-charges
For that flow to work you can not pass the Customer id from the platform, that is impossible. You need a real and separate Customer object on the connected account
oscar-customerbalance-connect
honest stirrup
ok, i change mi API Key
Currently, I am conducting tests before starting the integration, which is why I am using direct charges. It is only because I am unsure of the correct path. I am looking to implement bank transfer payments and connected accounts, so that it is similar to what we already have for card payments and resembles something like this:
The image corresponds to a test payment with a connected account using a credit card.
minor flare
that picture is not in English so it's hard to say for sure but to me this looks like a Destination Charge. As the developer, it is crucial that you understand your overall integration path, how you use Stripe Connect, which flow of funds you've selected, etc.
Looking at the account id you mentioned earlier, it's an Express account and so you should almost always use Destination Charges in that case
so really the earlier code example you gave you should not have pass the Stripe-Account header at all
honest stirrup
So, to summarize, would I have to review bank transfer payments and direct charges using Connect as separate flows?
sacred fieldBOT
minor flare
@honest stirrup not really what I said or meant unfortunately no
Right now you have a Stripe Connect integration with Express accounts and you seem to use Destination Charges for card payments. So you should stick with that for bank transfers/customer balance flows. There's no reason for you to use the Stripe-Account header in this flow
honest stirrup
Alright, I understand. It seems I needed to explain that I am new to the development team of the company. The implementation is in the application's code, and I am conducting my tests solely with Postman using various endpoints I find in the documentation, trying to intuit how the flow would be. I will have to review the integration in the application's code to see how the API calls are made in that flow. Just to confirm, is the way it is implemented for cards similar to the customer balance?
inland flax
Hello! No, the Customer Balance is a separate concept and works very differently: https://stripe.com/docs/invoicing/customer/balance
Unless you're referring to something else?
honest stirrup
Earlier, I was explaining to koopajah that I am seeking to implement bank transfer payments and connected accounts. Currently, we have implemented the card payment flow, where the transfer goes to one of our test connected accounts. I need to achieve something similar for bank transfers and payments with OXXO. I have already performed separate requests for bank transfers and OXXO payments using Payment Intents in POSTMAN. However, I also want these charges to be directed to a connected account, just like how it is currently set up for card payments.