coinbeastcrypto-account-support | Stripe Developers | Page 1

willow saddleBOT Oct 13, 2023, 5:32 PM

#

wicked matrix Oct 13, 2023, 5:33 PM

#

Unfortunately there isn't a way to "convert" an existing express account to a standard one - I believe you'd need to create a new standard one for them

#

You can try asking support to see if there's anything internal that can be done to solve for it though (but no guarantees)

willow saddleBOT Oct 13, 2023, 5:33 PM

#

coinbeastcrypto-account-support

#

@zenith whale :question: Have a non-technical question, account issue, or need one-on-one support? We wish we could help, but this community is focused on developers and technical discussions. Our support team will be able to assist you better than we can: https://support.stripe.com/contact

Stripe: Help & Support

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

zenith whale Oct 13, 2023, 5:34 PM

#

Ok so I have a more dev-specific question now

#

So if I set them up as a new account, we've previously implemented the ability to generate pproduct and payment links based on the actions users take in our custom invoicing web app

#

Will we need to make any code changes to account for a Standard account vs. Express account?

wicked matrix Oct 13, 2023, 5:38 PM

#

Can you give a bit more detail about "the ability to generate product and payment links based on..."

#

Are you just talking about creating Payment Links for your connected accounts throught the API?

zenith whale Oct 13, 2023, 5:38 PM

#

correct

#

My customers use my web app to generate invoices to their customers. When they do so, I create a product via the API and a payment link containing that product via the API

#

want to ensure that I do not need to implement any changes there considering they will now be setup as a Standard account vs. an Express account

wicked matrix Oct 13, 2023, 5:40 PM

#

Well the biggest consideration is more about what kind of charge flow you want to use - typically with express accounts you want to use destination charges or separate charges and transfers

#

whereas with standard accounts you want to use direct charges

#

What are you planning on using with these new standard accounts, and what were you using in the past for your express acounts?

zenith whale Oct 13, 2023, 5:42 PM

#

Ok, one moment, let me check to see which charge flow we're currently using

#

I believe we are currently using destination charges

#

but not sure where exactly to confirm this

#

Whenever fees are assessed on a transaction, we eat those fees vs. our connect customer

#

Idealy this would just remain the same even with standard accounts

#

is that an option?

wicked matrix Oct 13, 2023, 5:50 PM

#

You could do destination charges with standard accuonts, but it's not really something we recommend for a variety of reasons

#

One reason is that payment liability gets a bit weird. With destination charges chargeback responsibility falls on the platform (not on the connected account). But Standard accounts have a lot more control over their accounts so you can't prevent them from manually paying out their funds, and you also can't use tools like accuont debits to claw back funds from them

zenith whale Oct 13, 2023, 5:57 PM

#

Ok got it. So if were to create a link for my customer to onboard as a Standard account now, will that be direct charges by default?

#

And will there be any code changes necessary on my end

wicked matrix Oct 13, 2023, 5:59 PM

#

Switching to direct charges would need to some code changes

#

Direct charges require all requests to be made directly on the connected account (using the Stripe-Account header)

zenith whale Oct 13, 2023, 6:00 PM

#

even the requests to generate products and generate payment links?

#

it would be setup directly on the connected account instead of using the on_behalf_of parameter?

wicked matrix Oct 13, 2023, 6:02 PM

#

Yes, it would all have to be on the connected account and it's different than using on_behalf_of

#

Backing up for a minute - is there a specific reason you're switching over to standard accounts?

zenith whale Oct 13, 2023, 6:03 PM

#

Got it

#

Our reason for switching is that our customer often asks us to compile reports for them to that they can understand which payouts connect to which payments

#

which is burdensome overhead for us, so we'd rather than have a standard account so that they have dashboard access

#

and can see this themselves

#

whereas the express dashboard is too limited vs standard

#

So, if we wanted to do Standard + Destination Charges (assuming we don't mind taking on the risk of payment liability you outlined earlier),
If we simply create a new standard account for our existing customer and make no code changes, the payment links we generate will be destionation charges? and no additional code changes needed?

wicked matrix Oct 13, 2023, 6:06 PM

#

Yes, if you made no code changes they would be destination charges

#

I still would really strongly urge you not to move onto standard accounts w/ destination charges

#

It's not just the liability that's an issue - things like pricing can change if you have a custom pricing agreement, and while reporting may seem easier it'll also be a more confusing experience for your users

#

Your user will log into the stripe dashboard and see information on payouts/transactions, but they'll see not customers, none of the original charges, etc because that all lives on the platform

zenith whale Oct 13, 2023, 6:12 PM

#

Is there a better way to help my customer easily see which of their end customers' payments ladder up to a payout?

#

(Other than continuing to tie this together manually)

wicked matrix Oct 13, 2023, 6:13 PM

#

Do you do automatic payouts or manual ones?

zenith whale Oct 13, 2023, 6:14 PM

#

Auto

#

And also just to double click on that, Standard + Destination would not provide my customer this info, but would Standard + Direct provide them this info? (Then I would just need to make the code changes for Direct?)

wicked matrix Oct 13, 2023, 6:25 PM

#

Standard + destination would give them access to a part of the dashboard that would show them their own payouts and show them which transactions were included in those transfers, but the way destination charges work those would look like transfers from the platform -> connected accuont. They wouldn't have specific information about the original charge on the platform

zenith whale Oct 13, 2023, 6:26 PM

#

got it, but Standard + Direct you're saying would give them the full picture?

wicked matrix Oct 13, 2023, 6:29 PM

#

Correct (but would require a fair amount of integration changes on your end)

zenith whale Oct 13, 2023, 6:30 PM

#

Got it and just to recap those integration changes so that I can confirm with my CTO,

-The request when we generate the product via API
-The request when we generate the payment link via API
Anything else?

wicked matrix Oct 13, 2023, 6:32 PM

#

If you're using webhooks then you'd need to make changes there as well

#

and if you have any kinds of reconcilliation happening on your platform account you'll need to change that to look at charges on your connected accuonts instead

#

There's likely more, but it's hard to be specific w/o knowing what you're doing

zenith whale Oct 13, 2023, 6:34 PM

#

ok let me quickly ask if there's any other requests we're making

#

should hopefully have an answer back in a minute or two from my CTO

wicked matrix Oct 13, 2023, 6:35 PM

#

👍

#coinbeastcrypto-account-support