Stripe

General

The `Stripe` node allows to perform various stripe operations like creating a new subscription for a customer, update their billing info and upgrade their account to a different plan. It also supports the checkout session and the billing portals.

circle-info

TO handle stripe events with signature verification the Request node must receive HTTP request in raw form ie. "Raw Body" must be set to true.

Input

CASE: Customers / Create

CASE: Customers / Retrieve

CASE: Payment Methods / Attach

CASE: Payment Methods / Detach

CASE: Payment Methods / List

CASE: Payment Methods / Retrieve

CASE: Plans / List

CASE: Subscriptions / Create

  • Subscription options: Receives an Object with the subscription options. The `String` customer_id and the Object items with the subscription data are required. Learn more on stripe.subscriptions.createarrow-up-right.

CASE: Subscriptions / Update

CASE: Billing Portal Sessions / Create

CASE: Checkout Sessions / Create

CASE: Webhooks / Construct Event

Environment variables:

  • stripe: Requires Secret Key to be set.

Output

CASE: Customers / Create

CASE: Customers / Retrieve

  • Out: Returns an Object with the customer data. When requesting the ID of a customer that has been deleted, a subset of the customer’s information will be returned. Learn more on stripe.customer.retrievearrow-up-right.

CASE: Payment Methods / Attach

CASE: Payment Methods / Detach

CASE: Payment Methods / List

CASE: Payment Methods / Retrieve

CASE: Plans / List

CASE: Subscriptions / Create

CASE: Subscriptions / Update

CASE: Billing Portal Sessions / Create

CASE: Checkout Sessions / Create

CASE: Webhooks / Construct Event

Use Cases

Creates a checkout session for updating a customer subscription plan.

  • Request (Post) ➡ Stripe (Billing portal) ➡ Response (200)

Receives a Stripe event verifies it and updates the database.

  • Request (Post) ➡ Stripe (Construct event) ➡ Database (Update) ➡ Response (200)

Last updated