Interacting with the Stripe API or consuming Stripe webhooks in your NestJS applications is now easy as pie 🥧
-
💉 Injectable Stripe client for interacting with the Stripe API in Controllers and Providers
-
🎉 Optionally exposes an API endpoint from your NestJS application at to be used for webhook event processing from Stripe. Defaults to
/stripe/webhook/but can be easily configured -
🔒 Automatically validates that the event payload was actually sent from Stripe using the configured webhook signing secret
-
🕵️ Discovers providers from your application decorated with
StripeWebhookHandlerand routes incoming events to them -
🧭 Route events to logical services easily simply by providing the Stripe webhook event type
npm install ---save @golevelup/nestjs-stripe
or
yarn add @golevelup/nestjs-stripe
Also include the stripe peer dependency
npm install ---save stripe
or
yarn add stripe
Import and add StripeModule to the imports section of the consuming module (most likely AppModule). Your Stripe API key is required, and you can optionally include a webhook configuration if you plan on consuming Stripe webhook events inside your app.
import { StripeModule } from '@golevelup/nestjs-stripe';
@Module({
imports: [
StripeModule.forRoot(StripeModule, {
apiKey: '123',
webhookConfig: {
stripeWebhookSecret: 'abc',
},
}),
],
})
export class AppModule {
// ...
}The Stripe Module supports both the forRoot and forRootAsync patterns for configuration, so you can easily retrieve the necessary config values from a ConfigService or other provider.
The module exposes two injectable providers with accompanying decorators for your convenience. These can be provided to the constructors of controllers and other providers:
// injects the instantiated Stripe client which can be used to make API calls
@InjectStripeClient() stripeClient: Stripe// injects the module configuration
@InjectStripeModuleConfig() config: StripeModuleConfigThis module will automatically add a new API endpoint to your NestJS application for processing webhooks. By default, the route for this endpoint will be stripe/webhook but you can modify this to use a different prefix using the controllerPrefix property of the webhookConfig when importing the module.
If you would like your NestJS application to be able to process incoming webhooks, it is essential that Stripe has access to the raw request payload.
By default, NestJS is configured to use JSON body parsing middleware which will transform the request before it can be validated by the Stripe library. The easiest solution is to also include the @golevelup/nestjs-webhooks package and follow the steps for setting up simple body parsing.
Simply provide either stripe/webhook or the API route you chose when configuring the module. For example:
export class AppModule implements NestModule {
configure(consumer: MiddlewareConsumer) {
applyRawBodyOnlyTo(consumer, {
method: RequestMethod.ALL,
path: 'stripe/webhook',
});
}
}Failure to give Stripe access to the raw body will result in nasty runtime errors when events are sent to your endpoint
Exposing provider/service methods to be used for processing Stripe events is easy! Simply use the provided decorator and indiciate the event type that the handler should receive.
Review the Stripe documentation for more information about the types of events available.
@Injectable()
class PaymentCreatedService {
@StripeWebhookHandler('payment_intent.created')
handlePaymentIntentCreated(evt: StripeEvent) {
// execute your custom business logic
}
}Follow the instructions from the Stripe Documentation for remaining integration steps such as testing your integration with the CLI before you go live and properly configuring the endpoint from the Stripe dashboard so that the correct events are sent to your NestJS app.
Contributions welcome! Read the contribution guidelines first.