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
Do this before anyone sends or tests a payment in the refreshed sandbox. Update both fields below on every subsidiary that uses Paystand. Paystand Publishable Key and Paystand Template Domain must match. If they do not, the key will not work, and the sandbox can still generate live production payment links.
- In NetSuite, go to Setup > Company > Subsidiaries.
- Open each subsidiary that uses Paystand and click Edit. Repeat these updates on every one.
- 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). |
Existing Invoices Still Carry Production Links
Updating Paystand Publishable Key and Paystand Template Domain does not change invoices that already exist. Their payment links were built in production, and those links are copied into sandbox as they are.
You have two options:
- Create new invoices in sandbox (recommended). New invoices build their links with the sandbox key and domain.
- Reuse an existing invoice. Resend the invoice email from sandbox so the email template builds a fresh link. Do not use the old email or the old link.
Why One Click Payment Raises the Risk
A production link in sandbox is mostly harmless unless One Click Payment is turned on. With One Click Payment on, opening that link can process a real payment.
| One Click Payment | What happens when a production link is opened |
|---|---|
| Enabled | The previously used payment method is preloaded, so live checkout is ready to take the payment immediately. |
| Disabled | The payer must enter a payment method. A sandbox test card is recognized by the production checkout, and the payment fails right away. |
Treat any production link found in sandbox as unsafe to open, especially if One Click Payment is on.
Best Practices After a Sandbox Refresh
- Update Paystand Publishable Key and Paystand Template Domain before anyone sends or tests a payment request.
- Repeat the update on every subsidiary that uses Paystand.
- Create new invoices for testing instead of reusing invoices copied from production.
- If you must reuse an existing invoice, resend its email from sandbox so the link is rebuilt with the sandbox key and domain.
- Do not forward or open payment links from emails that were sent before the refresh.
- Pay special attention if One Click Payment is enabled. A production link can run a live payment.
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. |
| Old Payment Links | Do not open or forward links from emails sent before the refresh. Create a new invoice, or resend the email from sandbox. |
| 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.