---
title: Testing
slug: getting-started/testing
description: Ensure your Invoiced setup is flawless with our Testing Guide. It provides essential steps for thoroughly testing your account settings, workflows, and integrations before going live, guaranteeing a smooth operational transition.
docTags: 
createdAt: 2021-10-01T15:24:53.000Z
---

Our sandbox environment provides a sandbox to implement Invoiced, perform quality assurance (QA), and develop integrations.

## Sandbox

You can sign up for a free sandbox account at [https://sandbox.invoiced.com/signup](https://sandbox.invoiced.com/signup).&#x20;

In the sandbox you will be able to test out workflows and integrations you are building on Invoiced. The sandbox is identical to our production environment with the exception that it **does not perform any live charges** to credit cards or bank accounts. Sandbox accounts are entirely separate from your production account in order to keep testing isolated.

### Data Storage and Rate Limiting

**You should not depend on any data stored in the sandbox.** Test data is not guaranteed to be retained, and we might periodically clean out old test data to preserve system resources. Generally this would happen after data has been stale for months.

The sandbox is intented to allow you to build and test without restrictions, however, we could enforce rate limiting or data caps to prevent abuse. In normal scenarios you should never bump into these.

### Clearing data

You can clear all the data in your test account in **Settings** → **Developers** with the **Delete all test data** button. This will clear out data such as customers, invoices, and subscriptions while retaining your settings.

### Payments

When using test mode for payments, you can use the payment information below to simulate payments in various scenarios.

### Credit Card

| Brand                | Number                |
| -------------------- | --------------------- |
| Visa                 | `4242 4242 4242 4242` |
| Visa                 | `4111 1111 1111 1111` |
| Visa (debit)         | `4000 0566 5566 5556` |
| MasterCard           | `5454 5454 5454 5454` |
| MasterCard           | `2223 0031 2200 3222` |
| MasterCard (debit)   | `5200 8282 8282 8210` |
| MasterCard (prepaid) | `5105 1051 0510 5100` |
| American Express     | `3782 822463 10005`   |
| Discover             | `6011 1111 1111 1117` |
| Diners Club          | `3056 9300 0902 0004` |
| Diners Club          | `3056 9309 0259 04`   |
| JCB                  | `3530 1113 3330 0000` |
| UnionPay             | `6200 0000 0000 0005` |

### Credit Card Failures

| Brand | Number                | Description                    |
| ----- | --------------------- | ------------------------------ |
| Visa  | `4000 0000 0000 0069` | Declined charge                |
| Visa  | `4000 0000 0000 0127` | Vaulting or charging will fail |

### ACH

Any valid account and routing number will produce a successful charge.

| Routing Number | Account Number |
| -------------- | -------------- |
| `110000000`    | `123456789`    |

### Deposit Verification Amounts

If you are testing the micro-deposit verification flow you can use `$0.35` and `$0.45` as the amounts. Any other amounts will fail.

### ACH Failures

| Routing Number | Account Number | Description                    |
| -------------- | -------------- | ------------------------------ |
| `123123123`    | `123123456`    | Declined charge                |
| `123123123`    | `123123893`    | Pending charge, will succeed   |
| `123123123`    | `000222222227` | Pending charge, will fail      |
| `123123123`    | `000111111116` | Vaulting or charging will fail |

### SEPA

| IBAN                     | Description       |
| ------------------------ | ----------------- |
| `DE89370400440532013000` | Successful charge |
| `DE62370400440532013001` | Failed charge     |

### API

In order to access the sandbox through the API you must use the `api.sandbox.invoiced.com` endpoint. All of our official client libraries have support for the sandbox built in. You simply pass in your sandbox API key and `true` as the second argument when instantiating a new API client, i.e. `Invoiced::Client.new("{YOUR_SANDBOX_API_KEY}", true)`.

