When you perform a sandbox refresh in NetSuite, the integration tokens between Paystand and NetSuite are reset, disconnecting your sandbox environment. Follow these 6 steps to restore the connection.
| Quick flow: Verify Sandbox → Get API Values → Configure NetSuite → Generate Tokens → Complete Connection → Update Subsidiary Settings |
Step 1 — Verify the Sandbox Refresh
Before starting, confirm your sandbox is ready:
- Sandbox refresh has been completed
- All production data has been successfully copied to sandbox
- You can log into your NetSuite sandbox without issues
| Note: Do not proceed until the sandbox refresh is fully complete. Starting the reconnection process on an incomplete sandbox may cause configuration issues. |
Step 2 — Get the API Values from the Paystand Dashboard
- Open the Paystand Dashboard Sandbox and log in.
- Navigate to the Integration tab.
- Locate the API configuration values — keep this tab open, you will need these values in the next step.
Step 3 — Enter the API Values in NetSuite
- In NetSuite, go to Paystand > Manage > Configuration.
- Click Manage Connection.
- Copy each value from the Paystand Dashboard (Step 2) into the corresponding fields in Manage Configuration.
| Important: Make sure to select Sandbox as the domain. Using the wrong domain will connect to your production environment instead. |
| Keep this window open. You will return to it in Step 5 to complete the connection after generating the access tokens. |
Step 4 — Generate New Access Tokens in NetSuite
First, verify employee permissions:
1. Go to the Employee Record for the Paystand integration user and ensure the role associated with the Paystand integration has the necessary permissions.
2. Confirm the following permissions are set:
Access > Give Access checkbox is checked
Role > Employee has a Paystand Role assigned
Then generate the token:
3. Navigate to Setup > Users/Roles > Access Tokens
4. Click on New Access Token
5. Select the following and click Save:
| Field | Value |
|---|---|
| Application Name | Paystand Integration |
| User | The NetSuite user assigned to the integration |
| Role | The role configured for the Paystand integration |
6. Copy and save the following — they will only be shown once:
- Token ID
- Token Secret
| Important: Store these values securely. NetSuite will not display them again after you leave this page. |
Step 5 — Complete the Connection in Paystand
- Switch back to the Manage Connection window you left open in Step 3 — do not navigate to it again from scratch.
- Enter the Token ID and Token Secret generated in Step 4.
- Fill in all remaining required fields.
- Click Save and Connect.
Step 6 — Update Subsidiary Settings to Point to Sandbox
This step ensures that email templates always point to the correct Paystand domain and publishable key for the sandbox environment. Without this update, email templates may continue referencing your production environment after the refresh.
- In NetSuite, go to Setup > Company > Subsidiaries.
- Open the subsidiary you want to update and click Edit.
- Locate the Paystand fields on the right side of the record and update the following:
| Field | Value |
|---|---|
| Paystand Publishable Key | Enter the sandbox Publishable Key from the Paystand Dashboard (Step 2) |
| Paystand Template Domain | Update to .co (sandbox domain) |
- Click Save.
| Note: When reconnecting to production after your sandbox testing is complete, remember to revert these fields back to your production Publishable Key and domain (.com). |
Important Considerations
| Regular Updates | Repeat this entire process every time you perform a sandbox refresh in NetSuite. |
| Environment Labels | Always confirm you are in the sandbox environment — never apply sandbox tokens to production. |
| Permissions | Verify that user roles and permissions in the sandbox match those in production before starting. |
By following these steps, you can seamlessly reconnect your NetSuite sandbox environment to Paystand after a refresh, ensuring continued integration and functionality during your testing and development processes.