BigCommerce Implementation Overview – Paystand Help Center
Requirements to Implement
To successfully implement the Paystand BigCommerce App, you’ll need the following:
Technical Requirements:
- BigCommerce Version: Stencil theme, v2+ API support
- Paystand Account: Active account with API credentials and dashboard access
- NetSuite Account (optional): Required for ERP reconciliation
- Developer or Agency Partner: To install and configure the app (manual installation)
- Manual Installation: Paystand does not install or host your BigCommerce store
Important
- Paystand does not install or host your BigCommerce store. A developer or agency partner is required for manual setup and configuration.
Capability Matrix
| Feature | BigCommerce + Paystand App |
| Accept ACH, Bank, Credit Card | ✅ Yes |
| ERP Reconciliation | ✅ Yes (NetSuite only) |
| Save Payment Methods (Tokens) | ✅ Yes |
| Customizable Checkout UI | ✅ Yes |
| Guest Checkout Support | ✅ Yes |
| Fee and Incentive Configuration | ✅ Yes (via Paystand dashboard) |
Technical Implementation
Checkout Flow
All merchants follow the base flow below:
1. Customer Checkout Begins – A Checkout Object is created in BigCommerce (/v3/checkouts).
2. Paystand Checkout Renders – The embedded modal collects payment data and creates a Paystand Payment Object.
3. Payment Success – Paystand returns a confirmation to BigCommerce.
4. Webhook Event – Paystand sends payment confirmation to the app via /webhook/transactions.
Important considerations
Merchants using NetSuite benefit from automatic reconciliation and payment mapping between systems.
Merchants without NetSuite manage all reconciliation directly in BigCommerce.
Ensure your Paystand API credentials are live before enabling checkout in production.
Merchants Without NetSuite
BigCommerce finalizes the order locally.
The app updates the order (PUT /v2/orders/{orderId}) and marks it as Awaiting Fulfillment.
Merchants With NetSuite
BigCommerce pushes the order to NetSuite via your connector or iPaaS integration.
NetSuite then:
- Creates a Sales Order and Payment record,
- Applies the deposit automatically,
- Uses Paystand paymentId and orderId for reconciliation mapping.
ERP Integration API
For customers using NetSuite, reconciliation uses the following API endpoint:
POST URL
https://api.paystand.com/v3/netsuites/apply-payment/public
Required Fields in Request Body
{
"paymentId": "{{paymentId}}",
"transactionId": {{transactionId}},
"transactionType": "invoice" | "salesOrder"
}
- The paymentId comes from Paystand’s webhook payload.
- The transactionId is the internal NetSuite ID (Invoice or Sales Order).
- The payment amount must not exceed the invoice balance.
- The target record must exist in NetSuite before payment is cleared.
Tips
- Test API connectivity in a sandbox environment before linking live payment data to NetSuite.
- Confirm that
paymentIdandtransactionIdmatch between Paystand and NetSuite before applying payments. - Monitor webhook logs to ensure successful payment event delivery.
FAQs
Can guest users check out?
Yes. Guest users can complete checkout and are automatically assigned the default payment plan configured in your Paystand Dashboard.
Can customers store payment methods for reuse?
Yes. Tokenization is supported for faster repeat checkouts.
Are transaction fees visible in BigCommerce?
Yes. Fees and incentives configured in Paystand are displayed in the BigCommerce order record when enabled.
Do I need NetSuite to use Paystand?
No. NetSuite is optional. Without it, all order creation and reconciliation occur within BigCommerce.
Can I assign different payment rules to different customers?
Yes. Use the Paystand Dashboard to configure payment plans, including available methods, incentives, and surcharges per customer.
Does Paystand maintain my BigCommerce site?
No. You’re responsible for maintaining and hosting your BigCommerce environment. Paystand provides API credentials, documentation, and support for integration.
Table of contents
BigCommerce Implementation Overview