Implement BigCommerce subscription-style recurring billing using native webhooks and a recurring billing app integration

Verified steps

1. BigCommerce does not have a native subscription billing engine — implement recurring billing by integrating a third-party subscription app (e.g., Rebuy, Ordergroove, or a custom integration) available in the BigCommerce App Marketplace.
2. Use the BigCommerce Webhooks API (`POST /v2/hooks`) to subscribe to `store/order/created` and `store/order/statusUpdated` events, routing them to your subscription management backend so you can track the initial order and link it to a subscription record.
3. Store the customer's payment method token by integrating BigCommerce's Stored Payments API (`POST /v2/customers/{customerId}/payment/tokens`) — the token is provided by the payment gateway and can be used for merchant-initiated charges on the recurring cycle.
4. On each billing cycle, use the BigCommerce Orders API to create a new order programmatically (`POST /v2/orders`), then charge the stored payment method via the gateway's API using the saved token.
5. Implement dunning logic in your subscription backend: on a failed charge attempt, mark the subscription record as past-due, retry per your schedule, and notify the customer to update their payment method via a BigCommerce customer-portal-compatible flow.
6. Use BigCommerce's Customer Login API (SSO JWT token) if building a customer-facing subscription portal so buyers can manage their subscriptions without creating a separate login.