1. Paystand Help Center
  2. NetSuite SuiteApp Integration
  3. Admin & Configuration

How to Reconnect Your NetSuite Environment to Paystand Sandbox After a Sandbox Refresh

Updated

A NetSuite sandbox refresh copies your production account into sandbox, including your Paystand connection and the Paystand fields on your subsidiaries. Follow these steps to connect the sandbox to Paystand sandbox and stop it from sending production payment links.

Before you start

  • A NetSuite administrator should complete these steps.
  • You need access to the Paystand dashboard sandbox.
  • With Paystand NetSuite bundle 2.34.59 or later, the sandbox cannot use your production Paystand connection. To get it, contact Paystand Support.

Quick flow: Verify Sandbox → Get API Values → Configure NetSuite → Generate Tokens → Complete Connection → Update Subsidiary Settings → Check Your Templates

What the bundle protects, and what you still need to do

A refresh always copies your production Paystand values into sandbox. The bundle cannot change that. From bundle 2.34.59, it does stop those values from reaching your live Paystand account in some places, but not all.

In a refreshed sandbox Reaches your live Paystand account?
Payments, refunds and Virtual Terminal started in NetSuite No. The bundle sends them to Paystand sandbox, even before you reconnect.
Autopay processed in NetSuite No. The bundle sends it to Paystand sandbox.
Pay Now links in emails and PDFs Yes, until you complete Step 6 and Step 7. NetSuite builds these links from your subsidiary and template settings, not from the Paystand connection.

Until you reconnect (Steps 2–5), actions started in NetSuite still use your production API values, so they will not work in Paystand sandbox.

Step 1 — Verify the sandbox refresh

Before starting, confirm your sandbox is ready:

  • The sandbox refresh is complete.
  • All production data has been copied to sandbox.
  • You can log into your NetSuite sandbox.

Note

Do not continue until the sandbox refresh is fully complete. Starting on an incomplete sandbox can cause configuration issues.

Step 2 — Get the API values from the Paystand dashboard

  1. Open the Paystand dashboard sandbox and log in.
  2. Go to the Integration tab.
  3. Find the API configuration values. Keep this tab open; you need them in the next step.

Paystand dashboard sandbox, Integration tab with the API configuration values

Step 3 — Enter the API values in NetSuite

  1. In NetSuite, go to Paystand → Manage → Configuration.
  2. Click Manage Connection.
  3. Copy each value from the Paystand dashboard (Step 2) into the matching field.
  4. Check that Domain is set to Sandbox.

Domain

With bundle 2.34.59 or later, Manage Connection in a NetSuite sandbox does not offer Production and opens on Sandbox. On an earlier bundle, select Sandbox yourself: choosing Production connects the sandbox to your live Paystand account.

Keep this window open. You return to it in Step 5 after you generate the access tokens.

NetSuite Manage Connection screen

Step 4 — Generate new access tokens in NetSuite

First, check the integration user's permissions:

  1. Open the employee record for the Paystand integration user.
  2. Confirm Access → Give Access is checked.
  3. Confirm the employee has the Paystand role.

NetSuite employee record for the Paystand integration user

Employee record Access tab with Give Access checked and the Paystand role

Then create the token:

  1. Go to Setup → Users/Roles → Access Tokens.

NetSuite Setup menu with Users/Roles and Access Tokens 5. Click New Access Token.

NetSuite Access Tokens page with the New Access Token button 6. 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

New Access Token form with Application Name, User and Role

  1. Copy and save the Token ID and Token Secret.

Save the tokens now

NetSuite shows the Token ID and Token Secret only once. Store them securely before you leave the page.

Token ID and Token Secret shown once after saving the access token

Step 5 — Complete the connection

  1. Switch back to the Manage Connection window you left open in Step 3.
  2. Enter the Token ID and Token Secret from Step 4.
  3. Fill in the remaining required fields.
  4. 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. The bundle does not change these fields for you, and they decide where Pay Now links in emails and PDFs point.

In NetSuite

  1. Go to Setup → Company → Subsidiaries.
  2. Open a subsidiary that uses Paystand and click Edit.
  3. In the Paystand fields, update:
Field Value
Paystand Publishable Key The sandbox publishable key from the Paystand dashboard (Step 2)
Paystand Template Domain .co (sandbox)

Subsidiary record with the Paystand Publishable Key and Paystand Template Domain fields

  1. Click Save.
  2. Repeat for every subsidiary that uses Paystand.

The publishable key and the template domain must match. If they do not, the payment link does not open.

Note

When you finish testing and reconnect to production, set these fields back to your production publishable key and .com.

Step 7 — Check email and PDF templates for a fixed address

Some email and PDF templates have the Paystand checkout address typed in, for example https://checkout-v5.paystand.com/, instead of using Paystand Template Domain. Those links point to production no matter what Step 6 sets.

In NetSuite

  1. Open each email template and Advanced PDF template that has a Pay Now link.
  2. Look at the link address. If it contains paystand.com, change it to paystand.co in sandbox.
  3. Save the template.

When you return to production, change these templates back to paystand.com.

Existing invoices still carry production links

Updating the subsidiary does not change emails or PDFs that were already sent. Links in emails sent from production before the refresh still point to production.

You have two options:

  • Create new invoices in sandbox (recommended). Their emails and PDFs use the sandbox key and domain.
  • Reuse an existing invoice. Resend the invoice email from sandbox so NetSuite builds a fresh link. Do not use the old email or the old link.

Why One Click Payment raises the risk

A production link opened from sandbox goes to your live checkout. With One Click Payment on, it can take a real payment.

One Click Payment What happens when a production link is opened
On Your customer's saved bank account or card is already selected. One click on Pay takes a real payment.
Off Your customer must enter a payment method. A sandbox test card does not work on the live checkout, so the payment fails.

Treat any production link found in sandbox as unsafe to open, especially when One Click Payment is on.

Best practices after a sandbox refresh

  • Update Paystand Publishable Key and Paystand Template Domain on every Paystand subsidiary before anyone sends or tests a payment request.
  • Check email and PDF templates for a typed-in paystand.com address.
  • Create new invoices for testing instead of reusing invoices copied from production.
  • Do not forward or open payment links from emails sent before the refresh.
  • Repeat this whole process after every sandbox refresh.
  • Never enter sandbox values in your production NetSuite account.
  • Before you start, check that user roles and permissions in sandbox match production.
Was this article helpful?
0 out of 0 found this helpful