GitXplorerGitXplorer
a

checkout-single-subscription

public
1 stars
0 forks
6 issues

Commits

List of commits on branch master.
Unverified
683abb287138ef9dfaaeec73a028db17bdff9a3f

Updated README

aadreyfus-stripe committed 5 years ago
Unverified
fac8d5f2e494a8f7e022cf114838d4909695e2ef

Updated python README

aadreyfus-stripe committed 5 years ago
Unverified
a01ce49113c1114b604289b886f72420e6ad4e53

Updated README

aadreyfus-stripe committed 5 years ago
Unverified
d05e2db04bc3e18330720f052f88215e279b9e78

Sample on using Checkout for subscriptions

aadreyfus-stripe committed 5 years ago
Unverified
cfe8582b4162dc42313bf38da5a8f8b12fca0b50

Updated java README

aadreyfus-stripe committed 5 years ago
Unverified
aca4006901efa7d1905f44815cb24eedaefcf061

Added dotenv package

aadreyfus-stripe committed 5 years ago

README

The README file for this repository.

Using Checkout for subscriptions

Checkout is a pre-built payment page that lets you accept cards and Apple Pay. Billing is a suite of APIs that lets you model complex subscription plans. You can combine the two products to get a subscription payment page up and running without the need of a server.

When your customer is ready to pay, use Stripe.js with the ID of your Billing Plan to redirect them to your Checkout page.

A gif of the Checkout payment page rendering

See the sample live or fork on CodeSandbox.

Features:

  • Localization in 14 different languages 🌍
  • Built-in Apple Pay support 🍎
  • Built-in dynamic 3D Secure (ready for SCA) 🔔
  • Plans to support more payment methods 🔮

For more features see the Checkout documentation.

There are two integrations: client-only and client-and-server. The client-and-server integration uses the Checkout Sessions API for additional functionality.

client-only client-and-server
🔨 Prebuilt checkout page. Create a payment page that is customizable with your business' name and logo.
🖥️ Define plans in Dashboard or via API. Create a plan with either the Stripe Dashboard or API.
🔢 Start subscription for an existing Customer. Use Customers to keep track of additional customer data.

How to run locally

This recipe includes 5 server implementations in our most popular languages.

If you want to run the recipe locally, copy the .env.example file to your own .env file in this directory:

cp .env.example .env

You will need a Stripe account with its own set of API keys.

FAQ

Q: Why did you pick these frameworks?

A: We chose the most minimal framework to convey the key Stripe calls and concepts you need to understand. These demos are meant as an educational tool that helps you roadmap how to integrate Stripe within your own system independent of the framework.

Q: Can you show me how to build X?

A: We are always looking for new recipe ideas, please email dev-samples@stripe.com with your suggestion!

Author(s)

@adreyfus-stripe