stripe-node VS stripe-cli

// File: src/pages/api/stripe/webhook.ts import Stripe from 'stripe'; import { getXataClient } from '@/xata'; import type { APIContext } from 'astro'; // Process rawBody from the request Object async function getRawBody(request: Request) { let chunks = []; let done = false; const reader = request.body.getReader(); while (!done) { const { value, done: isDone } = await reader.read(); if (value) { chunks.push(value); } done = isDone; } const bodyData = new Uint8Array(chunks.reduce((acc, chunk) => acc + chunk.length, 0)); let offset = 0; for (const chunk of chunks) { bodyData.set(chunk, offset); offset += chunk.length; } return Buffer.from(bodyData); } // Stripe API Reference // https://stripe.com/docs/webhooks#webhook-endpoint-def export async function POST({ request }: APIContext) { try { const STRIPE_SECRET_KEY = import.meta.env.STRIPE_SECRET_KEY; const STRIPE_WEBHOOK_SIG = import.meta.env.STRIPE_WEBHOOK_SIG; if (!STRIPE_SECRET_KEY || !STRIPE_WEBHOOK_SIG) return new Response(null, { status: 500 }); const stripe = new Stripe(STRIPE_SECRET_KEY, { apiVersion: '2023-10-16' }); const rawBody = await getRawBody(request); let event = JSON.parse(rawBody.toString()); const sig = request.headers.get('stripe-signature'); try { event = stripe.webhooks.constructEvent(rawBody, sig, STRIPE_WEBHOOK_SIG); } catch (err) { console.log(err.message); return new Response(`Webhook Error: ${err.message}`, { status: 400 }); } if (event.type === 'checkout.session.completed' || event.type === 'payment_intent.succeeded') { const email = event.data.object?.customer_details?.email; if (email) { const xata = getXataClient(); const existingRecord = await xata.db.user.filter({ email }).getFirst(); if (existingRecord) { await xata.db.user.update(existingRecord.id, { paid: true }); } else { await xata.db.user.create({ email, paid: true }); } return new Response('marked the user as paid', { status: 200 }); } return new Response('no email of the user is found', { status: 200 }); } return new Response(JSON.stringify(event), { status: 404 }); } catch (e) { return new Response(e.message || e.toString(), { status: 500 }); } }

Before you can start accepting payments with Stripe Checkout, you need to create a Stripe account. Visit the Stripe website and sign up for an account. Once you have created an account, you will receive an API key that you will use to authenticate your requests to the Stripe API.

Next, we will enable checkout and payment processing through Stripe. First, install the Stripe clients with the following command:

Head to Stripe and register if you haven't already. We can use the Stripe API in Test Mode to build the e-commerce app. You can add a bank account and get verified later when you're ready to start collecting real payments.

Stripe published its 2023 annual letter last week. Much like the previous edition it was filled with a lot of interesting nuggets. Stripe has a strong history of being fairly transparent with its practices. These range from engineering challenges through its blogs as well as thought leadership in the financial and entrepreneurship space. I personally like the writing style of this letter as it doesn’t seem corporate or stuffy. Instead it is filled with humorous anecdotes, quirky observations and intelligent historical narratives which make it a compelling read. You can read the letter here → Stripe Annual Letter: 2023

Stripe – payments

Imagine you want to create an API endpoint that allows users to register in your backend, while simultaneously making a payment towards Stripe. This could be for something that's a subscription-based service, where you charge people for access to something.

Our app – Upollo – connects with your app event data (like Segment) and payment data (like Stripe) to analyze your users and instantly figure out if someone is an important player in your industry. We also help you convert more users, reduce churn, and expand single seats to teams within a company. We're SOC 2 certified and we take data security very seriously.

I've always found this to be a very useful practice. Many projects have a few core files (or packages / modules / whatever) where most of the changes happen. Being able to familiarize new contributors (or old returning ones) with those quickly really helps the startup time on a project.

I've added architecture files to projects at multiple jobs now [0], [1] and they've been well received. They're not perfect, but they're better than nothing.

[0]: https://github.com/zapier/zapier-platform/pull/324

[1]: https://github.com/stripe/stripe-cli/blob/master/ARCHITECTUR...

Stripe CLI

Before getting started with this, make sure that you have the Stripe CLI installed. Click me

You'll need the Stripe CLI installed.

The easiest way is to use stripe cli. You can download it here.

​ We use CLIs to perform quick actions from the comfort of our terminals and automate recurring tasks. You might use the GitLab CLI to submit your code in a merge request, so the team can review it and include it in the next release, for example. Many other developer platforms like AWS, Stripe, Sentry, and CircleCI offer CLIs as well. ​ Connecting a CLI to your online account often involves generating API access keys in a browser, then pasting those values into the terminal. Those credentials are usually saved in a plaintext config file that gives the CLI persistent access to your account, even after reboots. But if an attacker or process gains access to your system, they have the same level of access to your account that you do. ​ We built 1Password Shell Plugins so you can securely store all of your access keys in encrypted 1Password vaults, rather than on disk. When you use a Shell Plugin for a particular service, access to the associated API keys is restricted to your specific terminal session. ​ Because they're saved in 1Password, you can securely sign in to any CLI with your fingerprint or another form of biometrics. If the service supports it, MFA codes can be filled automatically – so there’s no need to pull out your phone multiple times every day. ​ In fact, there’s no need to type anything. No plaintext, no typing passwords, no hassle – you can stay in the zone and focus on the task at hand. ​

You’re probably looking for this: https://stripe.com/docs/stripe-cli

The Stripe CLI (command line interface) and Stripe for VS Code extension are essential tools when you’re building, testing and managing your Stripe integration. In this article you’ll learn about the powerful features of the Stripe CLI and how you can leverage those features both on the command line and via the VS Code extension.

You can test locally with the stripe CLI tool https://stripe.com/docs/stripe-cli, that sends the webhook info through localhost.