Connect Stripe to charge your customers

Before you start

This connection uses your business’s Stripe account. It is separate from your Nod subscription and affiliate payout account. You need access to Stripe settings.

Step by step

1. Open Integrations → Stripe → Configure and copy the webhook address Nod displays for your business.
2. In Stripe’s developer area, create an event destination or webhook endpoint. Paste the complete address.
3. Configure the payment and subscription events Nod needs. Use the event list below in this guide.
4. Copy the endpoint’s signing secret, beginning with whsec_, and paste it into Nod. This is not the same as an API key.
5. To publish products and payment links from Nod, also enter your Stripe account’s secret API key in the corresponding field.
6. Save the connection and review its status. In Products, configure delivery before publishing each purchase option.
7. Review received payments in Revenue; do not record them again manually.

Do not confuse signing and API keys

The signing secret verifies notifications Stripe sends to Nod. The API key allows Nod to publish products and payment links. They go in different fields and are not interchangeable. Copy the secret for the endpoint targeting this business and check that you are using the correct Stripe environment.

Sales and delivery also depend on the associated product. Before sharing checkout, check which programs or files buyers will receive. If payment appears in Stripe but not Revenue, review the webhook destination and events. Do not repeat the charge or add a manual sale while checking whether its notification is pending.

What to expect

Stripe events can record payments and associate them with the customer and product. Purchase options published from Nod have payment links.

Troubleshooting

The endpoint needs: checkout.session.completed, checkout.session.async_payment_succeeded, invoice.paid, invoice_payment.paid, invoice.payment_failed, invoice.marked_uncollectible, payment_intent.succeeded, charge.refunded, charge.dispute.created, charge.dispute.updated, charge.dispute.closed, charge.dispute.funds_withdrawn, charge.dispute.funds_reinstated, customer.subscription.updated, and customer.subscription.deleted.

If payments are missing, inspect endpoint deliveries in Stripe and confirm that the signing secret matches that exact destination. Do not share keys or replace another system’s destination.