stripe-node VS stripe-android

// 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 haven't seen excitement around any product and ecosystem launched since 2018 except flutter and Firebase."

Hard disagree, lol. Android Jetpack was launched in 2018. It was basically the second generation of Android development, it was a proper "tech stack" instead of everyone cobbling together third party libraries. Architectures switched over to the one true MVVM, instead of being this mess of MVC, MVP, etc.

Jetpack Compose is pretty amazing, it cut down our LOC by about half because we don't need adapters for every list. Kotlin coroutines & flow is nice. You get reactive programming, no more complex nested if/else conditions. We're not using Fragments or Activities much now either, navigation is via Compose, meaning DI is less necessary. So builds can be much faster too with a 2023 stack, and you can get UI changes rendered in the emulator immediately without even needing to update the build.

Here's a modern stack I made, should be able to spin up an app in an hour, and it shouldn't be too hard to read the code: https://github.com/smuzani/android-minimalist-template

Or if you want something production, Stripe's code is one of my favorites: https://github.com/stripe/stripe-android

Jetpack has some dark moments though, but that's a story for another day.

Ha! I hope not! You can look up my name as a maintainer in the android SDK here: https://github.com/stripe/stripe-android/blob/master/.github/CODEOWNERS and my linkedin here: https://www.linkedin.com/in/jaynewstrom/

Stripe Android SDK: Android SDK versions 20.7.0-20.11.0 were released this month and contain updates and fixes for functionality related to PaymentSheet and Identity.

Stripe Android SDK v20.6.2: Android SDK version 20.6.2 contains several bug fixes for Payments, reduces the size of StripeCardScan, and adds new rememberFinancialConnections features for Financial Connections.

Hi everyone - I'm on the Stripe Mobile SDK team and would love this community's feedback on what you would love to see us improve, namely in stripe-android. Would love to hear things that would make you say "Finally!", would have saved you several hours/days, or even little annoyances. No idea is too farfetched!

The Stripe Android SDK now supports SetupIntents with Google Pay. Use the multipayment UI to gain these features in v17.1.2.

Stripe Android SDK version 17.0.0 and 17.1.0: Android version 17.0.0 introduces GooglePayLauncher and GooglePayPaymentMethodLauncher to simplify Google Pay integration, and version 17.1.0 adds support for WeChat pay. Read more in the release notes.

Android SDK update: The latest version of the Stripe Android SDK (16.5.0) now supports Kotlin coroutines.

Thank you to our top open-source contributors this month: joeltaylor, ybiquitous, gogainda (stripe-ruby); masterjus (stripe-php); westy92, msternow (stripe-android); ees37 (stripe-go); Fonata (stripe-cli); rdsedmundo (stripe-node); hibariya (stripe-samples); risentveber, vinistock, jaredbeck, ryanwilsonperkin, anandvc, RyanBrushett, paracycle (sorbet).

Open-source 3DS2 SDK: We’ve open-sourced our 3DS2 SDK for iOS and Android under the MIT license.