NetSuite Reconciliation for BigCommerce

The NetSuite Reconciliation for BigCommerce feature enables merchants to connect and reconcile Paystand payments from BigCommerce with their corresponding NetSuite records.

This reconciliation ensures that every payment captured in BigCommerce is properly linked to the correct Invoice or Sales Order in NetSuite, supporting accurate accounting and financial reporting.

Merchants typically implement this connection through an integration platform (iPaaS) such as Boomi, Celigo, MuleSoft, or Workato.
These middleware tools manage data mapping and process orchestration, while Paystand provides the API endpoint that performs the actual reconciliation in NetSuite.

API endpoint

POST URL

https://api.paystand.com/v3/netsuites/apply-payment/public

This endpoint connects an existing Paystand payment record to a NetSuite transaction (Invoice or Sales Order).
It must be invoked by your iPaaS or middleware once both the payment and the NetSuite transaction are created.

Headers

{
  "Accept": "application/json",
  "Content-Type": "application/json",
  "Cache-Control": "no-cache",
  "x-publishable-key": "{{publishableKey}}",
  "Cookie": "connect.sid={{sessionId}}"
}

Body

{
  "paymentId": "{{paymentId}}",          // string, Paystand payment ID from BigCommerce
  "transactionId": {{transactionId}},    // number, NetSuite internal ID for the invoice or order
  "transactionType": "{{transactionType}}" // string, 'invoice' or 'salesOrder'
}

Requirements

• The NetSuite payment record must exist before funds clear

• The payment amount cannot exceed the NetSuite Invoice or Sales Order total

• The x-publishable-key and connect.sid values must be securely configured within your iPaaS environment

• Ensure the same Paystand account is used for both processing and reconciliation to avoid ID-mapping conflicts


Important
• Paystand provides the reconciliation API endpoint only — merchants must use an integration platform (iPaaS) to build and automate the reconciliation logic.
• The NetSuite record must exist before reconciliation; otherwise, the API call will fail.

Implementation notes

Merchants must use an integration layer to implement this reconciliation.
Paystand does not provide or manage middleware logic; it only exposes the API endpoint used to complete the process.

Example iPaaS flow:

1. BigCommerce captures a payment and a Paystand paymentId is created

2. The iPaaS retrieves the Paystand payment data via API or webhook

3. The iPaaS fetches the corresponding NetSuite transaction ID (Invoice or Sales Order)

4. The iPaaS calls POST /v3/netsuites/apply-payment/public to link both records

5. NetSuite displays the Paystand payment as a Payment record or Customer Deposit, completing reconciliation

Tips

• Test the reconciliation workflow in a sandbox environment before going live.
• Confirm that paymentId and transactionId match the same merchant account to prevent mapping errors.
• Log all API calls and responses in your iPaaS system to simplify troubleshooting and reconciliation audits.