next-stripe
next-stripe copied to clipboard
ynnoj
Simplified server-side Stripe workflows in Next.js
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [@babel/cli](https://babel.dev/docs/en/next/babel-cli) ([source](https://redirect.github.com/babel/babel/tree/HEAD/packages/babel-cli)) | [`7.12.10` -> `7.25.7`](https://renovatebot.com/diffs/npm/@babel%2fcli/7.12.10/7.25.7) | [](https://docs.renovatebot.com/merge-confidence/) |...
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot] avatar"){kind=avatar}
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more. ## Awaiting Schedule These updates are awaiting their schedule. Click on a checkbox to...
Would be great if you could also provide support for `retrieveCheckoutSession` & `customers` ```js const session = await stripe.checkout.sessions.retrieve(req.query.session_id); const customer = await stripe.customers.retrieve(session.customer); ```
Currently, the readme only talks about create sessions, intents, etc, but not how to make the redirection and handle the success. In case of redirect, there is `session.url` and also...
It would be good to provide a set of serializers inside options that each method uses to return. Here's what I'm currently thinking... ```js import NextStripe from 'next-stripe' export default...
1. Implemented all code into Typescript 2. Added `Next.Js` as Dependency and `prettier, @types/react and @types/react-dom` as Dev Dependency 3. Root `client.js` and `index.js` changed a little bit. 4. Added...
Pass through the [Stripe types](https://github.com/stripe/stripe-node/tree/master/types) but restrict them based on #17
Another common use case for Next.js API Routes is to receive and action Stripe events. It is recommended by Stripe that you [verify these events](https://stripe.com/docs/webhooks/signatures). The library could export a...
Setting a customer ID when creating a Checkout session or a portal link requires you to make sure the user is authenticated in a server-side context (e.g. see https://stripe.com/docs/billing/subscriptions/integrating-customer-portal#redirect) ...
Certain parameters should not be accessible on the client as they could be abused by a bad actor: For Checkout session creation, do NOT allow usage of: - `customer` (see...