How can I connect an account with Stripe as Developer ?
I found that connect needs express account. Express account need US address.
First of all it is recommended you have to toggle to use view test data to work as developer. You have to use developer/test data API keys to work as a developer.
Secondly, You can use account type custom to create connected account.
Also, there is no restriction to be based in US to used connected account with this account.
Related
I was testing Stripe APIs for Connect custom accounts, but for some reason, I keep getting pending verification. I tried to follow docs step by step, and I used testing tokens for account onboarding, created Person object, and uploaded testing files that need to be verified on the dashboard. Without verification, I cannot test payouts. I must have missed extra steps, but I was not able to figure it out. Does anyone know how to make it verified for testing?
I have one more question to make sure that I am not misunderstanding the custom account. Can the platform make a custom account have a direct charge instead of a destination charge? And if possible, is liability for returns and disputes still on platform?
You can check the account's requirements.currently_due hash, it tells you what information are needed to keep the account enabled. You should also use Connect Onboarding to collect the necessary info.
Technically you can create Direct Charge on custom connect accounts. However, it's not recommended. Because:
There's no Dashboard for custom account to address disputes
There's no Dashboard for custom account to set Radar rules
Refunds for Direct Charges on connected account will results in negative balance, which platform needs to cover
I want to use Stripe Connect to provide multiparty payments, in my website.
I have a platform. User A (customer) will pay User B (which is the service provider) on the platform and as a platform, I want to get some amount percentage in the middle.
So, I'm following this guide
https://stripe.com/docs/connect/collect-then-transfer-guide
But, when it comes to testing creating those standard connected accounts, I need to fill real information like phones and emails.
However, I found this guide to fullfill my problem:
https://stripe.com/docs/connect/testing#using-oauth
But, I'm not sure how can I use this guide?
How can I create a stripe account for my user B (who will accept payment through my platform) and got that account_id in testing (and later production)?
There are multiple points to clear:
There are Standard, Express and Custom account types. There are also
3 fund flows of Direct Charge, Destination Charge, or Separate
Charges and Transfers. See comparison from Stripe Doc (this is important)
If you decide to use Standard Account, you should go with Direct
Charges
There are 2 ways to onboard a Standard Account. OAuth is a
legacy integration. Account Link is preferable.
But really, Express + Destination Charge would be easier. You should also use Account Link to create express accounts
I have a small business where 5 of my customers use docusign. They want to be able to manage their docusign accounts through our website. I have created a docusign api on my end which I tested using my own developer account using my integration and secret keys which I store on my server in the db. I now want to allow my 5 customers to use this api to control their own docusing accounts. Do they all need to have a developer account and make it go live? I'm sure there is a better way and I cant make sense of it.
Do I need to push my app to live as well and purchase an API plan from docusign?
Please help it s hard to find any resource about this.
Do they all need to have a developer account and make it go live?
No, they don't need to. They have a production account and once your app goes live they can use your app with their account. If you want them to test your app in the developer environment first - then yes, they can get a developer account (which is free) to do some testing, but not required at all.
Do I need to push my app to live as well and purchase an API plan from
docusign?
Yes, you need to make your app live so that it can be used by paying customers in production. You would need your own production account to do that. If you are an ISV/Partner - you can get a free one, otherwise you will have to pay for your plan.
Currently, I working with Stripe gateway service. In my integration use only one Dashboard Stripe Account (one Publishable key + Secret key). I intend that my system create charges in two diferrentes Dashboard Stripe Account, depending others conditions.
I have analysed the "Connected accounts" using only one Dashboard Stripe Account, but is not usefull for me. I intend that each billing company have their Dashboard Stripe Account access (without mistake).
Is there any alternative beyond create customers / payment methods in both Dashboard Stripe Accounts?
pic1:
pic2:
You can build your application to manage two separate sets of keys based on the business logic for when to use one account or the other, but outside of Connect there is no other native support for something like this from Stripe. But you can absolutely do it manually. Yes, you would need to create any customers in both accounts, but this is true in a platform-connected account arrangement, too.
Two parts to this question:
I only see docs about making Destination Charges when you're using Stripe Connect and Custom Accounts. Is it possible to do it without Connect?
If it's possible to make a destination charge with just regular (Standard?) Stripe Accounts, am I able to test it out without needing two accounts that are live?
Thanks in advance!
Destination Charges are charges made by a Connect Platform on behalf of a connected account (whether that connected account is a Standard, Express, or Custom account). There is no reason to make a Destination Charge without Connect (and indeed, no way that you could).