Stripe’s embeddable Pricing Table is free, first-party, and good. If it fits, use it. It renders inside your own site from a script tag and a web component, you edit the plans in the Stripe Dashboard, and the table updates without a deploy. This page exists for the readers it does not fit, because Stripe has no reason to publish that list and we do.
The ceiling is documented in Stripe’s own Limitations section: four products per pricing interval, no usage-based pricing, and no step between the button and Checkout. The larger thing it does not do is tell your application anything. After checkout.session.completed fires, what a customer is allowed to do is still a problem you own.
| Stripe Pricing Table | SparkPay | |
|---|---|---|
| What it costs | Free. Part of your Stripe account. | Free for one app, then a monthly subscription. Stripe fees unchanged either way. |
| Where the page lives | Embedded in your own site, on your own domain | A page on SparkPay, which your site links or redirects to |
| How you add it | A script tag and a <stripe-pricing-table> web component | Register the app, import plans, link the URL. No embed code. |
| Plans it can show | Up to 4 products per interval, 3 prices each, 3 intervals total | Up to 4 plans. The same ceiling, not a better one. |
| Usage-based pricing | Not supported, per its own Limitations | Pay-as-you-go plans with per-unit rates shown on the card |
| Per-seat and tiered pricing models | Supported, including quantity selection | Not modelled. Flat subscription, one-time and pay-as-you-go only. |
| A step before checkout, such as sign-up | Not supported. The button goes straight to Checkout. | Free-tier email registration before any card is asked for |
| Does your app learn what the customer may do | No. You set up an event destination for checkout.session.completed and build fulfilment yourself. | Yes. One request returns tier, limits, trial and paywall state for an email. |
| Changing prices without a deploy | Yes, edit in the Dashboard and the table updates | Yes, edit in the dashboard and the page updates |
| Several products, several pricing pages | One table per product set, each embedded by hand in its own site | One deployment, one page per registered app, from one dashboard |
| Free trials | Yes, including trials without collecting a payment method | Yes, per-app trial length, with trial state in the status read |
| Coupons | Via Checkout and the Dashboard | Per-app codes, with a sale badge on the page when one is listed |
| Keys involved | Your publishable key sits in the embed. Revoke it and you must update the embed code. | A public app id in your client. No Stripe key in your repo. |
| Who you depend on | Stripe only | Stripe, plus SparkPay in the path |
Stripe behaviour and limits read from its Pricing Table documentation in November 2026, including the four-product cap, the absence of usage-based pricing and the shared rate limit of 50 reads a second. Stripe ships constantly, so check the current page before deciding. Neither option changes Stripe’s processing fees, which are paid the same way in both columns.
If you have one product, four plans or fewer, and you already have somewhere to put the entitlement logic. It is free, it is first-party, and it renders on your own domain, which is where a pricing page belongs for search. For a flat-rate or per-seat subscription it is the correct answer and nothing here improves on it.
If you need usage-based pricing on your main plan, or a quote-driven sales motion, both of these are the wrong shape. Stripe Billing with your own page gives you the pricing models the table does not support, at the cost of building the page.
If the gap you are feeling is not the page but everything behind it: you want one request that tells your app what tier an email is on, you want pay-as-you-go rates, you want the visitor to sign up before seeing a card form, or you have three products and do not want to do all of this three times. The trade is a dependency and a pricing page that is not on your domain.