Does stripe allow to charge multiple customers in on api call? - stripe-payments

I want to create a job that runs once a month and charges customers for different fees.
Is it possible to charge multiple customers in one api call ?
If not, what is the rate limit of the api ?

There is no way to charge multiple customers in one API call. You'd need to create one charge for each customer. As for the rate limit of the API, it's not published officially and you'd need to contact Stripe's support directly about this here.

Related

I want to deduct payment on the basis of request used in previously subscribed subscription when user upgrades in stripe?

I am working on stripe subscriptions and have 2 packages basic(400 requests)/month and premium(800 requests)/month and charges 10$ and 20$ respectively. when a user upgrades a subscription, I want to charge a user on the basis of request used. but stripe provides prorated approach and without prorated approach. in prorated approach it calculates payment on the basis of time spent in previously subscribed subscription and remaining time in newly subscribed subscription. but I want to calculate amount to be deducted from my own calculation because it might be possible that the user used only 2 requests in the first 15 days and then upgraded the package. however, I can use usage based pricing model but in this case I have to tell stripe each time that the user requested so increment the count and also stripe has rate limiting per second. how can I achieve it? thanks
I have tried to implement it with stripe schedules
Your best bet is the Usage based pricing model indeed. Read its Doc carefully or the Pricing Model Doc. Avoid Proration in your case, and make sure to report usage to Stripe.
Rate limiting is a different problem and you would need to deal with it regardless of APIs you are calling.

how do you use stripe connect to pay sellers

for example, the price of the products will vary and will be stored in the database (mongoDB), so is it possible to take the payment from the customer and then give 20% to my account and 80% to the seller. (my app uses nodejs and an express server with mongoDB)
There isn't enough information to provide a detailed answer, but here is some advice.
There are three different types of charges when working with connected accounts, and the documentation for each type explains how to collect application fees:
Direct charges: https://stripe.com/docs/connect/direct-charges#collecting-fees
Destination charges: https://stripe.com/docs/connect/destination-charges#application-fee or https://stripe.com/docs/connect/destination-charges#transfer-amount
Separate charges and transfers: https://stripe.com/docs/connect/charges-transfers#collecting-fees
The above processes rely on an amount being provided to collect application fees, so you'll likely need to calculate what 20% of the transaction is on your server and then pass that information into the Stripe flow.
The flow also changes a bit if you're working with Subscriptions instead of one-time payments. You'd use the application_fee_percent parameter:
https://stripe.com/docs/api/subscriptions/create#create_subscription-application_fee_percent

Is there a way to bulk process customer data in Stripe?

I have a long list of old customers (>10K) in Stripe for which I would like to give a new trial period. Is there a way to bulk process those or we have to do that manually one by one?
I guess this depends entirely on what exactly you mean by 'new trial'. Do these customers have pre-existing Stripe subscriptions?
There's really no way to do this via the dashboard. However if there are no pre-existing subscriptions, you could programmatically create subscriptions for each customer object accordingly. You can specify the trial period on the price or on a per subscription basis.
As there are no batch endpoints for these operations, please be wary of the rate limiting if working with the API in this way

Should my customers purchase an API plan if I am a partner?

I have a simple question. We are a CRM and are integrating with Docusign. So, whenever our customers want to send an envelope, they can send it from the CRM.
Do our customers have to purchase a separate API plan with Docusign?
From what I have read through, that is not the case but API limit of 1000 API calls per hour apply.
Can anyone confirm this?
You'll want to talk to your Account Manager for specific recommendations, or the Sales team if you don't have one.
As a general matter, you would need to own an API plan as the integration's owner but your customers could use your integration on any DocuSign account that has the appropriate level of features/functionality.

Stripe payment splitting api

i need bit clarification and guidance from exports about splitting stripe payment between multiple sellers.
I am building e-commerce systen and integrated stripe as a payment method for customers and it is working fine. Now I don't want to pay to manually to my sellers registered on my platform. I want to split the payment between several accounts if possible.
Lets say my platform is charging 10% as commission to the sellers and the customer is buying to different items from 2 different seller that worth $1000 than I want to split the payment as follow internally
me $100
seller 1:$450
seller 2:$450
Any help or guidance will be appreciated thanks
Stripe as such does not provide the splitting mechanism. But using Stripe Connect you can do it.
In Stripe connect there is one main account called platform account and can have multiple secondary accounts connected to it. So in your case, your seller will connect with your platform account.
Now for every charge you can split the amount among the seller and platform using application_fee parameter in charge object.
But this method has one problem also
If the customer is purchasing from multiple sellers than you have to charge the customer many times(as no. of the seller). So in case of multiple items from different sellers I have used transfer API to transfer the amount to seller instead of multiple charging to customer
In my system, I also face the same problem and after a lot of research, I found this way working for me.

Resources