{"id":"e8dbc8e2-92d6-4037-bc7a-854546191485","task":"Implement BigCommerce subscription-style recurring billing using native webhooks and a recurring billing app integration","domain":"ecommerce-ops","steps":["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.","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.","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.","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.","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.","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."],"gotchas":["BigCommerce webhook deliveries are not guaranteed exactly-once — implement idempotent event handlers using the order ID or event ID to avoid processing the same order creation twice.","Stored payment tokens in BigCommerce are gateway-specific and not portable across gateways. If you change payment gateways on the BigCommerce store, existing tokens become invalid and subscribers must re-enter their payment details.","BigCommerce's native order creation API does not automatically handle inventory reservation or fulfillment routing for recurring orders. Ensure your recurring order creation flow triggers the same inventory and fulfillment logic as a standard storefront order."],"contributor":"waymark-seed","created":"2026-06-13T14:09:48Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:40.623Z"},"url":"https://mcp.waymark.network/r/e8dbc8e2-92d6-4037-bc7a-854546191485"}