When invoice payment settled in BTCPay Server, sync it to Stripe (Legacy).

When an invoice payment is settled in BTCPay Server, update the transaction record in Stripe.

Try:

See all BTCPay Server + Stripe (Legacy) integrations or talk to a human

Trusted by teams already building on Knit·

4.9/5 on G2·

Google for Startups Accelerator

How Knit builds this workflow

The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.

BTCPay Server Explore BTCPay Server →

Triggers

New order

Fires when a customer places a new order in BTCPay Server.

Order status changed

Fires when an order in BTCPay Server is paid, fulfilled, refunded or disputed.

New customer

Fires when a new customer account is created in BTCPay Server.

Cart abandoned

Fires when a customer abandons their cart before completing checkout in BTCPay Server.

Actions

Create or update product

Creates or updates a product or listing in BTCPay Server.

Update order

Updates an order's status or fulfillment details in BTCPay Server.

Make a custom API request

Sends a custom API request to BTCPay Server for actions not covered by a dedicated action.

Stripe (Legacy) Explore Stripe (Legacy) →

Triggers

New customer

Fires when a new customer is created in Stripe (Legacy).

Subscription canceled

Fires when a subscription is canceled in Stripe (Legacy).

New invoice generated

Fires when a new invoice is generated in Stripe (Legacy).

Payment failed

Fires when a payment attempt fails in Stripe (Legacy).

Actions

Create customer

Creates a new customer in Stripe (Legacy).

Create subscription

Creates a new subscription in Stripe (Legacy).

Cancel subscription

Cancels an existing subscription in Stripe (Legacy).

Update customer

Updates a customer's billing details in Stripe (Legacy).

Sync recurring subscription buyers to your custom storefront When a new customer signs up in Stripe (Legacy), make a custom API request in BTCPay Server to provision their store access instantly. See details

Revoke store permissions upon subscription cancellation When a subscriber cancels their membership in Stripe (Legacy), issue a custom API request to BTCPay Server to adjust their account level. See details

Update customer records when affiliate commission is earned When an affiliate earns a commission in BTCPay Server, automatically update the associated customer profile in Stripe (Legacy) with updated reward balances. See details

See all BTCPay Server + Stripe (Legacy) integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “When invoice payment settled in BTCPay Server, sync it to Stripe (Legacy).” between BTCPay Server and Stripe (Legacy)?

Yes — describe it in the box above and Knit's Integrations Agent researches BTCPay Server and Stripe (Legacy)'s public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.

How long does it take to build?

Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.

Can new customer accounts in Stripe (Legacy) update storefront permissions in BTCPay Server?

Yes, when a customer subscribes in Stripe (Legacy), you can issue a custom API request in BTCPay Server to grant specific storefront privileges.

How does this integration handle affiliate commissions for recurring payments?

When recurring invoices are generated or payments fail in Stripe (Legacy), custom API requests can be sent to BTCPay Server to accurately adjust affiliate earnings.