#Dooing-connect
1 messages · Page 1 of 1 (latest)
Futher: Doc says - With Standard accounts, the user is responsible for fraud and disputes.
Who's the user in this context? Me? My Api? My customer?
We recommend using Standard or Express. Custom accounts require a lot more work to get started.
Is it possible to change this - at a later time e.g. in 1-3 years - to the "custom" account, when I want to implement a nice customer
dashboard with my own look and feel - without having to re-impement and or migrate everything?
You can change at any time, however this will require some work and migration on your end. You cannot convert an account from one type to another, so you would have to create brand new accounts.
Futher: Doc says - With Standard accounts, the user is responsible for fraud and disputes.
Who's the user in this context? Me? My Api? My customer?
Here the user is the merchant owning the standard account.
so that would be me, right?
No, when using connect there are 3 main parties:
- the platform account: you
- the connected account(s), either Standard, Express, or Custom: the merchants
- and the end users buying the things you sell
ah.
If you are using Express accounts, the platform is responsible for fraud and refunds. It you are using Standard accounts, then it's the merchants.
Well, in my case, since I am using an affiliate system for my customers, the merchants in your terminology are just regular customer refering other regular customers
--
Frauds - well it would be me, transfering money to my customer (merchants) So I dont see how they could be responsible for any fraud or refunds. They would just receive money when my business rules say so.
In that case Express seems like the way to go.
Use Express accounts when you - Want to use destination charges or separate charges and transfers
Use Standard accounts when you - Want to use direct charges
destination charges, separate charges, direct charges.
What are these?
No idea. I want to either "just in time" send affiliate related money to the credit card
of my customer, or maybe once / month.
The different types of charges are explained here: https://stripe.com/docs/connect/charges
so for credit card payment, instantly or once per month, I would choose which of the 3?'
Can you describe the flow of money in your setup, between the platform, connected accounts, and end-users?
sure. So I have an email marketing Saas. Customers sign up for monthly subscriptions. For each customer, I want to give them an affiliate ID. They can add this ID to a sign up link, and whoever signs up for a paid account, should be linked to this affiliate id. Each period, when the affiliated (new) customer pays me (via stripe) I want to send 30% of the paid amount to my other customer that has already a subscription account on stripe. Fees and any costs would be handled fully by me. Not strictly necessary, but of course it would be nice if the affiliate customer had a way to login to stripe, to check that they money I send them is actually correct.
Or here is my "pseudo algorithm' I just wrote for myself:
When a customer is created, store an affiliate ID with the customer.
Whenever a customer is charged (webhook)
Is the customer younger than 2 years, and does he have an affiliate id?
If yes, get the affiliated customer.
Send 30% of the amount charged to the affiliated customer via stripe api.
Do you want to send the fee automatically as soon as the payment is done, or do you want to send the fee manually based on your own logic?
And can a single customer have multiple affiliate IDs?
I am unsure. But I would need to check if the customer related to the payment is younger then 2 years, otherwise I would not do a payment - so I assume I would need some logic on my end.
Yes. In that case you probably need separate charge and transfer, where you control exactly when and how much to send. The other options would automatically send the fee as soon as the payment is made.
But two things:
- I would recommend to carefully read the documentation about the difference between each charge types to make sure this works for your use case https://stripe.com/docs/connect/charges
- And if you have more questions about this, I would recommend asking Stripe support directly (here we focus mainly on technical questions about the API) https://support.stripe.com/?contact=true