I basically want to create subscription plans where I can charge the connected accounts and give them additional benefits on the platform in return. Because the connected accounts are businesses, they are not registered as customers on the platform. Is there a proper way to do this through stripe?
Your options here basically are to either register them as Customers as well and use Subscriptions, or potentially use Account Debits and your own recurring mechanism.
Related
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.
I'm building a platform where content creators can setup a subscription service of which I'll take a fee (think Twitch.tv, Substack, OnlyFans, etc.)
Content creators will setup a Stripe Connected Account on the platform. I'll operate the Platform Account.
Customers that subscribe to a content creator might want to subscribe to others so it makes sense to keep both Customers and their PaymentMethods on the Platform Account. Customers must be able to manage all their subscriptions and have their credit card details pre-filled, if already available.
I can't, for the life of me, understand how to share these Customers and their PaymentMethods with the content creator's Connected Accounts.
I followed the clone customers across accounts guide unsuccessfully. It errors out while creating the Token, saying that the Customer must have an active payment source. I read somewhere that this guide doesn't work with PaymentMethods but I don't really know if that's true.
Then I found this other guide. It seems, though, that I would have to create a Customer, per User, per Connected Account which will make me duplicate information and make subscription management harder.
Could anyone, who has experience building a similar service, give me some pointers?
Thanks
Instead of cloning PaymentMethods to your connected accounts (for which this guide is the correct one) you could create subscriptions using destination charges. The idea being that the customers and payment methods stay on your platform account. When an invoice is paid its funds (minus an application fee set by you) are automatically transferred to the connected account.
I have multiple active subscriptions that were set up by my customers using their credit cards when signing up using intents API for SCA compliability.
Let's assume their cards expire and they want to change the default card they use on all their subscriptions. Until now this was done using the cards API by setting a default card on the customer account or simply updating all the existing subscriptions setting the card as default.
How does this work to be SCA compliant? Do I need to take my customers through a lengthy setup intent process on each of their running subscriptions individually? Or is there a way to create a single setup intent and assign that to all the running subscriptions they might have?
You can set the Customer's invoice_settings.default_payment_method and that will apply to all of the Subscriptions they have - unless you've explicitly set each Subscription's payment method (in which case you'll have to update each of those instead).
The stripe api documentation doesn't seem to cover a specific case I'm looking for:
Subscribe someone to a plan on the platform account, and automatically send a portion of their monthly dues to a second account:
I have two accounts:
Platform
Service
I have a plan, platformplan on the Platform account.
I want to subscribe someone to that plan, but send a portion of that cost to the Service account.
A similar, but not applicable request is covered by their documentation:
A serviceplan on the Service account can be subscribed to and an application fee taken via:
application_fee_percent: 10,
stripe_account: "{CONNECTED_STRIPE_ACCOUNT_ID}",
This works (and very helpfully shows the Service account the fee breakdown and total cost), but requires I have access to the Service account if I want to change the plans, which is not ideal. I am trying to set it up so I can have separate plans on the platform (which I control) connected to payable service accounts.
You can split a charge via the destination field:
destination: {
amount: 877,
account: "{CONNECTED_STRIPE_ACCOUNT_ID}",
},
but is there a way to do something similar with a subscription/plan?
The idea is to create the plan, customer and subscription on the connected account instead. This ensures that the owner of the account get their share of the funds. You would take the platform's share via an application fee. This is outlined here.
Another solution is to charge on the platform instead and after the fact, transfer funds to one (or multiple) connected accounts while linked the transfer to that billing cycle's charge. This approach is documented here.
I have a client who has content that he wants to publish on the web (and potentially for iPad). He wants the viewer to pay to subscribe for the content.
Is there a service out there I can integrate with to for handling the accounts and collecting the monthly subscription fee (using credit cards or something else)?
There are several services out there that can help you with this - Recurly (where I work), Chargify, CheddarGetter, Spreedly, etc. These services handle the recurring billing aspect, customer management, email communication, following up with failed payments, etc. You'll also need a payment gateway (to process the cards) and a merchant account (for the payment gateway to deposit the funds into).
Authorize.net and PayPal both have recurring billing features, but the logic for upgrading/downgrading accounts is not there or difficult to use, and you'll still need to handle customer communication for failed payments and other actions.
You need to use a payment gateway here, which will be responsible for handling the transaction between your site and the many different payment networks. There are a lot of operations happening in between, so you might want to check out the wikipedia article for a step by step information on that.
We personally use authorize.net in our company for many of its advantages, some of which are:
It has an API that makes it easy to integrate with any language.
It is a trusted brand already, proven by the number of merchants that use them.
It is secure.
It provides the service with a reasonable price.
Most of major payment gateway providers do support recurring billing or subscription plans, paypal,authorize.net etc, most of the time you have to log in to your account admin console and configure a plan, and send the payment plan id with the payment request to the payment gateway. some payment gateway providers, like Braintree supports to create recurring billing plans dynamically and assign users to that plan at the run time it self, how ever it's always better to go for a local payment gateway provider or a payment gateway which provides low fees, if your preferred payment gateway provider is not supporting recurring billing anther options is to store cc details on the server and and handle it your self but it's a great risk to store cc details on the server, and you will have to follow PCI standards and it's hard.