Netsuite Reconciliation for Magento

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

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

Merchants typically implement this flow using their preferred integration platform (iPaaS) such as Boomi, Celigo, Mulesoft, or Workato.
These middleware tools handle the data mapping and process orchestration — while Paystand provides the API endpoint that performs the actual reconciliation in NetSuite

API Endpoint

POST 
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 Magento
 "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 Paystand account used for reconciliation matches the account processing Magento payments — otherwise, ID mapping may fail due to account conflicts.
Alert icon

Important

  • Paystand provides the reconciliation API endpoint only — merchants must use an integration platform (iPaaS) to handle orchestration and mapping.
  • The NetSuite record must exist before reconciliation is applied; otherwise, the API call will fail.

Implementation Notes

Example iPaaS Flow:

1. Magento captures a payment and creates a Paystand paymentId.

2. iPaaS fetches the Paystand payment data via API or webhook.

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

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

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

Tips icon

Tips

  • Test the reconciliation flow in a sandbox environment before pushing to production.
  • Validate that paymentId and transactionId correspond to the same merchant account to prevent ID mismatch errors.
  • Log all API responses in your iPaaS platform to simplify troubleshooting and audit tracking.
Was this article helpful?
0 out of 0 found this helpful