BigCommerce Integration
Connect BigCommerce to LostChurn for automatic failed payment recovery.
The BigCommerce integration is live. Install the LostChurn app from the BigCommerce App Marketplace or connect via Settings > Integrations in your LostChurn dashboard.
BigCommerce is a leading SaaS ecommerce platform that supports recurring orders and subscription billing through its native tools and third-party apps. LostChurn connects to BigCommerce via OAuth and processes webhook events to add Smart Retry Engine and dunning capabilities for failed payments.
Prerequisites
- An active BigCommerce store (any plan)
- Store Owner or Admin access to your BigCommerce Control Panel
- A LostChurn account with at least one workspace created
App Installation
BigCommerce App Marketplace
- In your BigCommerce Control Panel, navigate to Apps > Marketplace.
- Search for LostChurn in the App Marketplace.
- Click Get This App, then Install.
- BigCommerce redirects you to LostChurn to complete the OAuth authorization flow.
- Review the requested permissions and click Authorize.
- You are redirected back to your LostChurn dashboard with the BigCommerce connection confirmed.
Manual Installation
If you prefer to connect manually:
- In your LostChurn dashboard, go to Settings > Integrations and click Connect BigCommerce.
- Enter your BigCommerce Store Hash (found in your store URL:
store-{hash}.mybigcommerce.com). - Click Authorize. You are redirected to BigCommerce to grant LostChurn access.
- Review the requested permissions and click Confirm.
OAuth Setup
LostChurn requests the following OAuth scopes during installation:
| Scope | Permission | Purpose |
|---|---|---|
store_v2_orders | Read and Write | Read order data, update order status after recovery |
store_v2_customers | Read | Access customer details for dunning communications |
store_v2_transactions | Read | Read payment transaction details and decline codes |
store_v2_products | Read | Read product and subscription metadata |
store_v2_information | Read | Read store settings for timezone and currency |
OAuth tokens are securely stored and automatically refreshed. LostChurn never stores your BigCommerce password.
Webhook Configuration
During installation, LostChurn automatically registers the following webhooks with BigCommerce:
| Webhook Scope | Endpoint |
|---|---|
store/order/paymentStatusChanged | https://webhooks.lostchurn.com/v1/bigcommerce |
store/order/statusUpdated | https://webhooks.lostchurn.com/v1/bigcommerce |
store/order/created | https://webhooks.lostchurn.com/v1/bigcommerce |
store/customer/updated | https://webhooks.lostchurn.com/v1/bigcommerce |
All webhook payloads include the X-BC-Webhook-Signature header. LostChurn verifies the HMAC-SHA256 signature on every incoming request using your store's webhook secret.
Supported Events
| BigCommerce Event | LostChurn Action |
|---|---|
| Order payment failed | Creates a failed payment record, triggers retry evaluation |
| Order payment captured | Marks recovery as successful, stops active dunning |
| Order refunded | Records refund for revenue reporting |
| Order status changed to Cancelled | Records churn event, triggers reactivation campaign if configured |
| Customer payment method updated | Triggers immediate retry of pending failures on updated payment method |
API Integration
LostChurn uses the BigCommerce REST API (V2 and V3) to:
- Read order details: Fetch order metadata, line items, and payment information when a failure event is received.
- Initiate retries: Trigger payment re-attempts through the BigCommerce Payments API.
- Update order status: Mark orders as recovered or write internal notes after successful retries.
- Fetch customer data: Retrieve customer email, name, and locale for personalized dunning messages.
Payment Retry Flow
- LostChurn receives a payment failure webhook from BigCommerce.
- The decline code is extracted from the transaction record via the Transactions API.
- LostChurn determines the optimal retry strategy based on the decline code and historical data.
- At the scheduled retry time, LostChurn calls the BigCommerce Payments API to re-attempt the charge.
- On success, the order status is updated and dunning stops. On failure, the next retry is scheduled.
Verify Connection
- In your LostChurn dashboard, navigate to Settings > Integrations.
- The BigCommerce card should show a green Connected badge.
- To send a test event, create a test order in your BigCommerce store using a test payment method that simulates a decline.
- Navigate to Events in your LostChurn dashboard and confirm the failure event appears.
Provider-Specific Notes
Multi-Storefront
BigCommerce supports multiple storefronts under a single store. LostChurn processes events from all storefronts through the unified webhook system. Events are tagged with the originating storefront channel ID for filtering in analytics.
Subscription Apps
If you use a third-party subscription app on BigCommerce (such as Recharge or PayWhirl), LostChurn receives payment failure events through BigCommerce's unified order system. For deeper subscription lifecycle tracking, consider also connecting the subscription app directly if LostChurn supports it.
API Rate Limits
BigCommerce enforces API rate limits based on your plan:
- Standard: 150 requests per window
- Plus: 200 requests per window
- Pro/Enterprise: 400+ requests per window
LostChurn monitors the X-Rate-Limit-Requests-Left header and throttles requests accordingly. If you consistently approach your rate limit, contact LostChurn support to optimize request batching.
Sandbox Stores
BigCommerce sandbox stores are fully supported. LostChurn detects sandbox connections and labels events accordingly, keeping test data separate from production analytics.