I have a website in which I use Stripe and its NodeJS SDK. In particular, I use the checkout feature.
The problem is this: I have a product and I want to earn, let's say, 100€ for each sold product. In this moment this is not possible, because when the user pays, I will have stripe's fees removed from the 100€.
Is there a way to specify: "this is the price that I want to earn, without the fees, the additional fees will be paid by the user"?
Or do I have to increase manually the price and adjust it so that after the fees it will result in 100€?
It’s not possible to do that automatically, you need to manually compute the amount that includes the Stripe fee. The formula to compute that amount is explained here.
However, note that:
You cannot really know the Stripe fees in advance when using Checkout, since they will change depending on the Payment Method used (for example cards in EU have a different fee than cards in the US). You can learn more about Stripe pricing here.
And in some jurisdictions, charging processing fees to your customers is prohibited by law (as explained in the first link I shared).
So instead of customizing the price to each charge, I would recommend to directly set the price to cover your own costs of doing business (including credit card processing fees). For example, charge your customers 102€ for your 100€ product.
Related
The subscription plan
I have a subscription plan available at my app which I need to model with Stripe.
The subscription plan details are the following:
A fixed amount of $20/month or $200/year (discounted) that the user must pay.
With the previous fixed amount the user can consume 2500 units of the product per month.
If the user consume more than 2500 units in one month every additional unit has a value of $0,01.
Examples
A user choose the subscription plan with the $20/month option and in the first month he/she consumes 2520 units.
The total amount to pay for the first month of the subscription for this user is:
$20 fixed amount
20 additional units * $0,01 = $0,2
Total to pay: $20 + $0,2 = $20,2
A user choose the subscription plan with the $200/year option. In the first month he/she consumes 500 units. In the second month he/she consumes 5000 units.
For the first month this user needs to pay:
$200 because is starting the subscription
No additional units.
Total to pay: $200
For the second month this user needs to pay:
No fixed amount because the fixed yearly quantity has already been paid.
2500 additional units * $0,01 = $25
Total to pay: $25
Problems
My biggest problem modeling this with Stripe payments is that is not possible to have prices with different intervals in the same subscription.
If the user chooses the yearly fixed price is not possible to create a subscription on Stripe that has a fixed yearly pay (of $200 in this case) and a monthly graduated price (for the additional consumed units).
I have seen that the subscription upsell feature is something very similar to what a I need. But once it's activated I can't find any way on the API to enable it when the subscription is created (I'm not using checkout).
I have seen also that it's possible to create two subscriptions, one for the yearly pay and another one for the monthly units. But creating two subscriptions make everything really difficult, you need to take into account two subscription states and callbacks are more difficult this way too.
Questions
What is the best and simple way to model this subscription plan using Stripe?
Note: I'm doing a custom integration with Stripe, so the subscriptions and customer are created via API. I'm not using Stripe checkout.
My biggest problem modeling this with Stripe payments is that is not possible to have prices with different intervals in the same subscription.
Indeed, you can't combine Price objects with different intervals on a single Subscription. Otherwise, this pricing is possible by combining a flat rate fee with metered usage as outlined here.
Your best option in cases where your customers elect for the annual fixed fee is to roll with a single usage based Price and amend the initial invoice to include that a one-off Invoice Item for the annual fixed fee.
I have seen that the subscription upsell feature is something very similar to what a I need. But once it's activated I can't find any way on the API to enable it when the subscription is created (I'm not using checkout).
Subscription upsells are a Checkout only feature right now. However this is not really related to the problem you're facing (it just provides a UI for your customers to upgrade to an annual Price for the same Product).
I am creating a Stripe Connect marketplace which charges a fixed fee based on value of sales, e.g. up to £2500 of revenue (for a connected account in a calendar month) will incur a flat fee of £200 per month to the platform.
I have read the Stripe documentation but still quite unclear how I can achieve this using a Standard Connect account. I understand the concept behind adding a flat fee per transaction but my use case is based around the amount of revenue over a time period.
Any help is always appreciated.
it sounds like you want to keep track of the payments processed by your connected accounts in order to figure out what to charge them.
The best way to do this is probably to set up a Connect webhook and listen for events like charge.succeeded and keep a running total each month for each account.
You have a number of options for charging your accounts, but using Billing to create a subscription that you update as their revenue grows is probably the best experience. You could also use metered billing with pricing tiers based on the payments you track.
If you need to calculate historic revenue, you'd need to manually retrieve the payments and calculate the total for the month(s) you're interested in.
NOTE: For both the webhook events and the retrieval approaches you'd need to be aware of several different objects other than Charges that may affect revenue up or down, like PaymentIntents, Refunds, Disputes etc depending on the details of the connect account's integration.
Hope that helps!
My application allows a customer to purchase credits for later in-app use.
I want to enable customers to buy credits throughout the month, and only get billed at the end of the month.
Should I be using a Stripe Subscription at an amount that equals the price of one credit, and change the quantity according to the number of credits the customer purchased?
(After a successful invoice - I'll reset the subscription quantity to 0)
Is there a better solution? Perhaps some clever method of using Stripe Checkout?
Your proposed approach sounds reasonable.
I've not tried it but an alternative I can think of would use a free plan and the Invoice Items part of the API.
Create a free plan with amount with amount field set to 0. As far as I can see from the docs, all the subscription lifecycle webhooks should be triggered for Customers who're subscribed to the plan.
Through the month, create InvoiceItems for the Customer. According to the docs, at the end of the billing cycle, those InvoiceItems are added to the customer's invoice.
Sometimes you want to add a charge or credit to a customer but only actually charge the customer's card at the end of a regular billing cycle. This is useful for combining several charges to minimize per-transaction fees or having Stripe tabulate your usage-based billing totals.
Beyond that, you'll want to consider if you should have Stripe generate/email your invoices.
I don't think this is the way to go, because subscriptions are billed the first time among other things.
The recommanded way is: stripe doc: Place a hold on a card
summary
You first ask authorization for a certain amount (the max amount). Eg: 1000$
Your custommer buy 50 credits in the month
At the end of the month you charge the customer for 50$ (it can not be greater that the maximum you authorized in the first step)
That's all :)
According to the documentation Google Wallet seems to only support monthly recurring subscriptions.
I'd to charge users annually for the use of an application hosted on AppEngine (purely to be able to offer the user a better price and reduce administrative costs). Are there any plans to support annually recurring subscriptions?
Or is there a way to configure the current subscription system to behave as an annual subscription system?
Technically there's no way to configure an annual subscription. But I suppose you can work around it: Request an initial payment for the entire first year and then a monthly-recurring payment at a discount.
For example, suppose you offer a monthly plan that costs $100. And you want to offer an annual plan for $900 (25% discount). Instead, you may offer an initial payment of $900 followed by 36 monthly-recurring payments of $75.
What this means for your business is that once a user has paid for and used your service for an entire year then you start treating her as a "loyal customer" and let her keep paying the discount price without committing for another year.
Wallet for Digital Goods currently only supports a monthly frequency for subscriptions.
https://developers.google.com/commerce/wallet/digital/docs/jsreference#jwt
there is no official solution for an annual subscription, but you could implement a solution similar to what #oferei or #EdSF suggested in their posts.
I'm assisting in development of a backend for a painting service that works with many contractors across the US. We've been using Stripe, but the business has been paying the contractors using their bank's ACH service add-on which takes 3-5 days and has to be done manually.
Balanced seems like it's Stripe + next-day ACH payouts with a great API, automating everything. Is this an accurate description of the service? I'm confused why you'd ever use Stripe over Balanced in that case. This is assuming it's also a merchant account + payment gateway like Stripe if I'm reading correctly.
Still wrapping my head around how to best make this work. Thanks everyone.
Stripe:
Charge cards
ACH payouts
Recurring billing
Webhooks
OAuth merchant signup
2.9% + 30¢ per charge
Holds funds for 7 days before you can pay out
Charges in USD or CAD
Balanced:
Authorize and charge cards
ACH payouts
ACH debits
Fully API driven merchant signup
Escrow account
Recurring billing
Webhooks
2.9% + 30¢ per charge, 25¢ per ACH credit (volume pricing calculator)
Funds are available immediately for payouts (vs Stripe's 7 day rolling reserve)
Charges in USD
In a nutshell the fundamental difference is that Stripe focuses on bringing money in to your account, Balanced focuses on bringing money in, holding it until an order to fulfilled, and paying out to your merchants.
You can use Stripe to collect money and Balanced to pay out easily enough, the biggest problem you'll run into is that there will be a liquidity problem as you have to transfer funds from your Stripe to Balanced before you can pay out or create a float of 7 days.
Stripe is also great if you have sub-agents or affiliates that you want to have run the sale, but where you take a percentage of the total charge as well. We recently implemented this for a cause oriented site that supports the collection of donations for smaller and more personal causes. It is one of the more interesting features of the Stripe API. Sub accounts can be created on the fly and activated via a simple email validation creating a one-stop shop for configuring online affiliate programs.
Both are good for specific things, for example balanced will let you collect money from groups in a single pot (in their escrow), and then pay it out. Stripe is good for automated billing.
Stripe is a established company that has a polished interface and support. Balanced is a fly-by-night.
I have one site with Balanced and one with Stripe Connect, and this is the defining difference.
Balanced changed their API and completely broke all transactions.
They didn't even send out an email. Never happened with Stripe.
Balanced once "held up our site for review". Our marketplace went down with no notice or email. (And no explanation when I emailed them, just a response it was being held).
balanced.js can take 10-15 seconds to load, causing the page to hang (we implemented lazy loading just for balanced, but the page is not always ready when needed).
IRC support: Balanced has ~40 inactive users and ~10 users online ATM [in the middle of the U.S. night there are no user, and the inactive users have no AI personality]. Stripe has at least 100 active users, and I seem to be able to get an answer whenever I need to.
etc.
Balanced has one killer feature - your users can sign up and start selling immediately, they don't need to validate themselves to sell, only to receive money.
They are more likely to follow through if it's easy to get into the system. But the risks are real, and should not be ignored.
Also, if it matters, the fact that Stripe can accept payments in multiple currencies can be a killer feature as well.