The Square Sandbox consists of a free, isolated server environment, a set of Sandbox seller test accounts, and a Sandbox Seller Dashboard for each account. A Sandbox is created for you when you create your first application in the Square Developer Dashboard. The Sandbox environment separates transactions from the production environment. Sandbox values are test values and can't be used in a production environment.
Don't add any personal information (such as name, email address, phone number, and birthday) into a Sandbox environment. You can't find, delete, or export any personal data from the Square Sandbox.
Use the Square Sandbox to create transactions in the seller test account by calling Square APIs using API Explorer or your own code. You can use the Sandbox to take payments, create an inventory and subscriptions, and simulate sales and transactions using payment information specifically for use with the Sandbox.
You can access the Sandbox in several ways. You can go between the Sandbox and the production environments by selecting the appropriate URL. The base URL for calling Sandbox endpoints is
https://connect.squareupsandbox.com. When you move your application to production, you need production credentials and you need to use
https://connect.squareup.com as the base URL.
In the Developer Dashboard, after you select your application, a toggle at the top of the page lets you select either Sandbox or production environments.
If you use API Explorer, you can select the Sandbox or production environment by using the toggle at the top of the page.
The Sandbox doesn't accept valid credit cards. You must use test credit card values found in Sandbox Payments.
The default test account is a seller account in which you're automatically authorized to perform actions and access data. All your applications have been pre-authorized for all OAuth permissions. Because the default test account uses the same access token as the applications you create, you don't need to use an access token that is specific to a seller. If you create additional seller test accounts, you must use the access token assigned to that seller account.
There is a Seller Dashboard for each test account you create using the Developer Dashboard. The Seller Dashboard provides a seller view of results of the API calls and is accessed by choosing Open from the test accounts list in the Developer Dashboard.
You can use the Sandbox to:
- Test new versions of Square APIs before using them in production.
- Test using a specified API version. You specify the version of the application you run in the Sandbox.
- Test payment scenarios.
- Simplify the OAuth process so you receive authorization to make calls on a seller's test account when you set up the account.
- Run API calls for unsupported regions.
Use of the sandbox environment is free of charge. You can make an unlimited number of free sandbox API calls. There are no payment processing fees for sandbox payments given that cards aren't actually charged and payments are never actually processed by a live bank.
In the production environment, some API calls require that your application user has a subscription to the related Square software-as-a-service. All production payment processing through Square APIs have a processing fee. For information about payments pricing, see Payments Pricing with Square APIs and SDKs.
The Square Sandbox can be great for exercising test scenarios, but it does have some limitations. For example, Square hardware, such as a POS terminal, can't be used with the Sandbox.
Sandbox limitations include the following:
- Square applications (first-party applications), including Square for Restaurants, Square Point of Sale, and Square Invoices, aren't supported for testing in the Sandbox.
- Connection V1 API calls aren't supported, including the V1 Employees API and V1 Settlements API.
- The Reader SDK 1.0 and Point of Sales API aren't supported.
- The Snippets API and Sites API aren't supported.
- Settlements data isn't available.
- Customer settings aren't supported.
- Testing the Terminal API is supported, but testing on the device itself isn't.
- Gift cards generated by the Gift Cards API can't be used with Virtual Terminal in the Sandbox. In addition, physical gift cards can't be created or managed.
The Seller Dashboard, when used with a test account in the Sandbox, has limitations as well. These limitations include the following:
- Receipts aren't generated.
- Refunds can be viewed but can't be issued.
- Viewing or editing subscriptions isn't supported.
- Sending emails isn't supported.
- Viewing the booking URL isn't supported.
The Seller Dashboard doesn't support the Banking tab. As a result, Balance and App Fee Reporting are also not supported.
Create Sandbox test accounts and access the Sandbox Seller Dashboard in the Developer Dashboard.
The Developer Dashboard lets you create up to four test accounts in addition to the default Sandbox test account.
Sign in to the Developer Dashboard to create test accounts.
Choose Add to create a new Sandbox test account.
The application OAuth page lets you authorize a Sandbox test account to use your application with the permission scope you set in the authorization. In testing, you can bypass the production OAuth Authorization API call flow by using the access token generated for each Sandbox test account you create.
- Sign in to the Developer Dashboard and choose the application that you want a test account to be authorized to use.
- On the application page, you can toggle between the Sandbox and Production accounts. Choose Sandbox.
- In the left pane, choose OAuth, and then choose Authorize an Account.
- In the Authorize an Account dialog box, choose a Sandbox test account to authorize.
- Choose the permissions that you want the account to have, and then choose Save.
If you want to change the permission scope that you authorized for a Sandbox test account, you must revoke the existing authorization and create a new one.