Sandbox Test Values

Sandbox test values are used to test the client and server sides of payment processing in the Square v2 Sandbox.

Sandbox payments

Square platform clients such as the payment form and In-app Payment apps accept payment cards and return one-time use encrypted "nonces" to be submitted to Square API payment endpoints to take payments. You can avoid testing your code with a real payment card by testing in the v2 Sandbox.

Test client-side card-present logic in your payment form or In-App Payment app by using test credit card numbers to generate nonces for use with the Square API payments and card on file endpoints in the sandbox.

If you do not need to test your client-side nonce-generation logic, use the nonces provided in the Square endpoint testing section to submit payments in the sandbox with test nonces.

Client-side testing

You can use test credit cards with the payment form and In-AppPayments SDK to input card numbers that will generate a testable payment nonce.

Card present success state values

The sandbox supports a collection of credit card numbers for all Square-supported card brands for simulating the client-side of payment scenarios.

Test cards

Notes:

• You can set the card expiration date to any future month and year.

• Payments in USD (United States), CAD (Canada), or GBP (United Kingdom) also require a valid postal code.

• When testing the SCA flow with one of the European Union test cards, the Verification Code simulates the SMS verification code sent to the buyer mobile phone during an actual transaction.

Error state values

You can reproduce certain error states in the sandbox by providing special values in the Square payment form or In-App Payments SDK.

If you use one of the following values, the nonce returned will trigger an error when it is processed by the CreatePayment endpoint:

SCA testing in the payment form

To test SCA in the sandbox, you cannot use a nonce returned by the payment form in the cardNonceResponseReceived event after entering sandbox credit card numbers or personal credit card numbers. Instead, use a test nonce from the following table.

Use the SqPaymentForm.verifyBuyer function for card present and card on file (CoF) SCA challenges with the following test values:

The SCA flow requires that the buyer provides a code sent to their mobile phone in an SMS message. When testing in the sandbox use the Verification Code to simulate the code sent via SMS.

The SCA flow and these test values are not supported in the legacy sandbox.

Square API endpoint testing

Test your payments logic that uses the CreatePayment endpoint to take a payment or CreateCustomerCard endpoint to store a customer card on file.

If you are using the Square Payments API to generate payments in the sandbox, you can use one of the sandbox test nonces as the source_id in the payment request.

Note: You can also use a nonce generated with one of the test payment cards from the Client-side testing section.

Sandbox test nonces

Generating error states

You can reproduce certain error states in the Square payment and card on file endpoints by using the following test values.

Sandbox locations

Your sandbox account comes with 1 mock location per application. This location is unrelated to the production locations listed in the Square Dashboard

The sandbox location ID for a given application is listed on the Locations tab of the application control panel in the Application Dashboard. You can also fetch the location ID programmatically by calling ListLocations with a sandbox access token.

Sandbox disputes

Use these predefined payment amounts that map to a specific dispute reason. When you set one of these amounts in a CreatePayment request, Square generates a sandbox dispute with the corresponding reason.

The amounts shown are in the lowest denomination of the currency you provide in the CreatePayment request. For example, for USD, the amount is in cents.