QuickBooks Payments test cards

Use these details to try payments in a QuickBooks Payments sandbox (test) account. They work only in the sandbox: never use them in live, and never put real card or bank details into a sandbox.

You need a QuickBooks Online sandbox company, which you create on the Intuit Developer portal. For ACH, the payment amount sets the result.

• The card number must be one of Intuit’s test numbers, with an expiry date in the future. The sandbox doesn’t check the CVC or the billing address, so the Require address (AVS) setting on the QuickBooks Payments connection here makes no difference to the result (Practice processing payments with mock data).
• Card errors are set by the cardholder name, for example emulate=10401 for a decline (Practice processing payments with mock data). The checkout has no separate cardholder name for QuickBooks Payments: we send the customer’s first and last name, then a comma and the customer’s account code (which we set), for example emulate=10401, <account code>. Enter the trigger as the customer’s first name and leave the last name empty (or the other way round): if both are filled in, Intuit receives both and the trigger won’t match. We always add the comma, and you can’t leave out the account code, so the name Intuit receives is never exactly emulate=10401. Intuit’s page doesn’t say whether a longer name still matches, and our own tests don’t cover these triggers.
• A card payment here is captured straight away, and sandbox charges settle at once, so voiding it gives error 10405: try a refund instead (Practice processing payments with mock data).
• For ACH, switch on Enable ACH in the QuickBooks Payments connection settings here (it only appears when the account currency is USD), and enable ACH on the QuickBooks Payments account too. Then the amount sets the result: type it in dollars and cents, for example 3.33 for a decline or 5.55 for a success (Practice processing payments with mock data). We show an ACH payment as pending first, and update it when QuickBooks Payments reports the outcome.

The sandbox checks the card number against these test numbers and the expiry date against today’s date, so use an expiry date in the future. It doesn’t check the CVC or the billing address.

Use one of these as the cardholder name: in the checkout, enter it as the customer’s first name and leave the last name empty (see How to choose a test result).

Sandbox card payments settle immediately, so you can try refunds but not voids. Intuit says voiding a card payment in a sandbox company returns error 10405. Our own tests with Intuit’s sandbox void an authorisation that hasn’t been captured, and that void succeeds.

The sandbox doesn’t check the address (AVS) or the CVC, so these checks can’t be tested in it.

Use this bank account. The payment amount sets the result.

Intuit’s page says 5.55 returns succeeded. In our own tests with Intuit’s sandbox, a 5.55 ACH payment comes back pending when it is created.

Once the sandbox company has a successful 5.55 ACH payment, the refund amount sets the refund’s result in the same way: 1.11 and 2.22 give pending, 3.33 and 4.44 give declined, and 5.55 gives succeeded.