This example app demonstrates how to integrate Stripe, the payments platform, with Convex, the backend application platform. We keep track of payments in Convex and fulfill orders when they're confirmed by Stripe.
Features:
- You can test the payment flow end to end using Stripe's test card numbers
This integration works! You can see a production deployment at this live site: https://xixixao.github.io/paymorebeseen/.
Read a deep dive into this repo in Wake up, you need to make money! (ft. Stripe) on Stack.
Run:
npm install
npm run dev
This will guide you through making a Convex project.
To test the payments flow, follow these steps:
- Sign up for Stripe for free at https://stripe.com/
- Install the stripe CLI
- Run
stripe listen --forward-to localhost:5173/stripe
- Copy the "Your webhook signing secret" from the output of the
listencommand, and set it asSTRIPE_WEBHOOKS_SECRETenvironment variable on your Convex dashboard - Copy your test secret API key from the code example on https://stripe.com/docs/checkout/quickstart and set it as
STRIPE_KEYenvironment variable on your Convex dashboard
You can then use the test credit card details to go through the payment flow, see https://stripe.com/docs/checkout/quickstart#testing
Convex is a hosted backend platform with a
built-in database that lets you write your
database schema and
server functions in
TypeScript. Server-side database
queries automatically
cache and
subscribe to data, powering a
realtime useQuery hook in our
React client. There are also
Python,
Rust,
ReactNative, and
Node clients, as well as a straightforward
HTTP API.
The database support NoSQL-style documents with relationships and custom indexes (including on fields in nested objects).
The
query and
mutation server functions have transactional,
low latency access to the database and leverage our
v8 runtime with
determinism guardrails
to provide the strongest ACID guarantees on the market:
immediate consistency,
serializable isolation, and
automatic conflict resolution via
optimistic multi-version concurrency control (OCC / MVCC).
The action server functions have
access to external APIs and enable other side-effects and non-determinism in
either our
optimized v8 runtime or a more
flexible node runtime.
Functions can run in the background via scheduling and cron jobs.
Development is cloud-first, with hot reloads for server function editing via the CLI. There is a dashbord UI to browse and edit data, edit environment variables, view logs, run server functions, and more.
There are built-in features for reactive pagination, file storage, reactive search, https endpoints (for webhooks), streaming import/export, and runtime data validation for function arguments and database data.
Everything scales automatically, and it’s free to start.