#BrianC
1 messages · Page 1 of 1 (latest)
Hello
Taking a look
So looks like that Customer exists on your Platform, not your Connected Account
So you are attempting a Direct Charge on your Connected Account which means the Customer must also have been created on your Connected Account as well
If you are trying to create a Charge on_behalf_of the Connected Account then you still should be creating the Charge in your platform, meaning you should not be passing the Stripe Account Header when you create the Charge request
OK. As I mentioned previously, it was working fine up until Dec (the last time we processed charges like this) however the customer has been collected is how we have been doing it so perhaps I am mistaken about the on behalf of. I get mixed up with the terminology,. I will find a previous transaction of the same nature to compare. Has anything changed with regards to how these are processed?
Nope nothing has changed on our end with regards to this.
This really has to be a change on your end with where the Charge is being created (platform vs. Connected Account)
The way this business is setup. our clients create a connected Express account and we collect pledges from customers and charge at a later date, our platform gets a fee and they are paid the rest. Is that called on behalf of? Just so I get it straight to communicate.
on_behalf_of is specifically a parameter that you use when you create a PaymentIntent (https://stripe.com/docs/api/payment_intents/create#create_payment_intent-on_behalf_of) or Charge. It allows you to actually create the PaymentIntent/Charge on your platform but have the end-customer see that they are paying the Connected Account.
This is used with destination charges: https://stripe.com/docs/connect/destination-charges
I can see that you were doing this in your Platform account as of Dec 15th
But it seems that recently your integration changed to using the Charges API
Hmmm. We literally haven't touched the code on this site in over a year.
Is this something to be concerned about? How is that changed other than our code?
This really only can change from your code. It looks like your account is doing a completely different thing than it was as of before Dec 15th and that only can be controlled via your code
So something really did have to change on your end
I mean you are using a completely different API endpoint to start with. Like before you were creating PaymentIntents (ex: https://dashboard.stripe.com/logs/req_Jnhocnd9WPJRlf) but now you are using the Charges API (ex: https://dashboard.stripe.com/logs/req_upEjFcCzMNnXxs)
Yes, that actually is intentional. I should rephrase that some of the charges are charged immediately and some are charged at a later date. I guess I'm confused as to why customers stopped being created on the connected account and are now being created on our master account. That is what is strange. That did not happen in the past. Literally nothing has changed, unless we were hacked which seems like a strange thing to change. I'll look into it some more. Is there an easy way to transfer customers over to a connected account and make the charges there?
Yeah this still indicates something had to have changed on your end. You can't copy Customer objects, you would re-create those on Connected Accounts if necessary. You can clone PaymentMethods from your Platform --> Connected Account if you need to.
I would recommend backing up though and understanding the desired flow you want though
And figuring out what did change
OK. Thanks for your help