#artdudejoe
1 messages · Page 1 of 1 (latest)
Hey @hasty trench !
Hi 👋
Can you share an example request ID?
And on_behalf_of will only change the merchant of record.
What's the diff btw merchant of record and the actual account?
But since these don't appear to be Direct Charges they will always exist on the Platform Account
So PaymentIntent is not a "Direct Charge"?
You can make a Payment Intent in a variety of charge types. Are you familiar with the different types of charges in Stripe Connect
I am not
Okay well there is a good doc to start with.
What kind of Account Types are you dealing with?
card type
really only cards in the US
I see ['stripe_account' => '{{CONNECTED_STRIPE_ACCOUNT_ID}}']); is this the difference?
Rather than 'on_behalf_of'?
No, sorry what type of Connect Accounts are you using?
In that case you should be using Direct Charges
Which would live on the Connect Account
I honestly don't see any difference between what I am doing with paymentIntent and this except I replace on_behalf_of with stripe_account. Am I right?
On the refund I see charge instead of payment_intent with stripe_account
How/where you specify the account is a critical factor for how all of this behaves.
It sounds to me like you need to spend some time reading the doc I provided along with all the related child docs. There are some gotchas in there that it will be important for you to understand
But with Standard Connect Accounts we highly recommend using Direct Charges
I've been reading these docs for months now and I've apparently not found a complete solution. For example setupIntent vs paymentIntent vs charges. Server vs JS vs no-code etc. Is there any way you can point at the gotchas just so I know?
Wow, that's a lot of unrelated things.
Setup Intent - collect payment method details to charge later
Payment Intent - charge an amount
JS can exist on the Server (Node) and the client
The gotchas I was referring to have to do with what Charge type & Account you choose
And how that impacts where records are stored, how you make charges, and how you can reconcile revenue
RIGHT! I am needing both in person (with or without terminals -- a whole different struggle) and saved payment methods/setup. All in a Connect environment for hundreds of SAAS customers.
All in a custom server based solution that I am adding to an existing scheduling solution.
10's of thousands of Stripe Customers
Okay well this forum is best for helping people with specific questions about specific APIs. These questions are all a bit nebulous and hard to parse
I feel your pain.
Let me test a bunch more to see if I can't get these payments to show up in the right places using the strategies you pointed to.
Stripe does a whole lot more than all the extra-specifics that I need so that has been confusing. Especially after writing for Authorize Net for 15 years.
One last (well two) question: If I may?
- when you say "Charge Type" you mean ['card'] vs others, right?
No
I'm referring to the charge types doc I provided above
Ok. Very cool.
- when you say "Account type" you mean "Standard" vs "Express" or "Custom"?
- Yes
YAY. I got something right today!
FYI we refer to ["card"] type stuff as Payment Methods
Nomenclature. yep
Yeah, it helps with clarity when asking questions
I am a hack without any training beyond a couple books and tons of online resources that happens to have built full featured online apps that seem to be very useful. Learning more as we speak.
As another who self-taught programming, web dev and the like my recommendation would be to build a really simple, dumbed down test integration (using a personal account and test API keys).
You can get a much better insight into how the APIs behave and work together
Yep. Sandboxing is my friend.
I've already deleted the whole test data set several times.
I just noticed last week that these payments were in the wrong place.
By "wrong place" you mean on the Platform?
If you read the third column in the table about the different charges, it helps explain why different charges live on different accounts
Yes, not in the Connect account but in the Platform Account.
For Destination charges, the customers interact with the Platform (like Uber or Lyft). In that case it makes sense that the payments are on the platform not the connect account (individual drivers)
Okay. So if I let them live initially on the Platform account but want to distribute balance (after your fees and mine eventually) how do I do THAT? Because maybe I process these payments on the Platform Account and then do payouts based on on_behalf_of
That would depend on the type of charge
I can see that
But if you read the docs for each charge type it lays out the funds flow very clearly
For instance, for Destination charges: https://stripe.com/docs/connect/destination-charges#flow-of-funds-app-fee
and you don't do payouts based on on_behalf_of. Use the transfer_data parameter
Found https://stripe.com/docs/connect/charges for the distinctions
Right, that's the doc I linked earlier.
There are separate related pages that detail exactly how the call the APIs for each type of charge
Yep, that's why the docs get so nested