1. Guides
2. Get started

Moov has pre-populated your test account with sample business details and accounts. You aren't required to enter anything for your test account to receive the verified status. In test mode, requirements for all capabilities have been satisfied, so they are automatically enabled for you. You'll have full access to the following capabilities:

• Transfers
• Wallet
• Send funds
• Collect funds

While you don't need to request capabilities for test mode, for production mode, you'll need to request capabilities. You can do this at the same time you create your account, or request additional capabilities later.

Switch to test mode

After you've completed your business profile and Moov has approved your production account, you can switch between production and test mode in the Moov Dashboard by using the Account dropdown in the upper left hand corner.

Invite team members

While in test mode, you can invite team members to your test account. Inviting team members to your test account does not enable them to use your production account. If you'd also like to invite team members to your production account, you will need to do that separately in production mode.

API keys

You will need to create an API key specific to the test account. We suggest naming the API key something that will help you remember that it's for testing purposes.

You can use localhost, ngrok, Netlify, or Vercel domains for these keys.

Transfers

Transfers in test mode won't move any real money. For the timing of transfers in test mode, note that:

• Wallet to wallet transfers complete almost instantly
• ACH transfers in test mode will complete in about an hour (see the processing speed guide for production mode)

If you would like to see how Moov handles failures in production, view the transfer failures guide.

American Express transfers need to be a minimum of $1. In production mode, American Express transfers less than $1 will result in an error.

Test mode data

To simulate card transfers, disputes, ACH returns, RTP failures, bank account verification, and other transfer scenarios, use the test cards, amounts, and routing numbers in the test mode data reference.

Link cards & card acceptance

See the postal and CVV sections below for additional test verification scenarios. Also note that test cards will expire once your chosen expiration date passes.

Name verification

The card link POST endpoint and PATCH endpoint offer an optional verifyName field, which uses Visa's ANI verification as a check against the supplied holderName. Use the following combinations of correct and incorrect names in the holderName field to test results.

Correct name: Alex Nora Irwin

If ANI is not supported, you'll receive unavailable for all results.

Postal code verification

CVV verification

Push & pull from card

The expiration date can be any future date. CVV can be any 3 numbers for Visa and Mastercard. Since push and pull card transfers require verifications, test cards always return a successful match for CVV, postal code, and (if requested) name verification, regardless of the values provided. To test negative verification results, use the test values in the CVV verification, postal code verification, and name verification sections.

Tap to Pay

Test mode allows you to verify your Tap to Pay integration on iOS and Android before processing live payments. The terminal configuration fetched from the Moov API determines whether the SDK operates in test or production mode. When using a test configuration, the SDK simulates card tap scenarios using these test cards:

When testing Tap to Pay on mobile with test cards, you don't need to enter a CVV, expiration date, or postal code. For platform-specific details, refer to the SDK documentation:

• Tap to Pay on iPhone
• Tap to Pay on Android

Declined card transfers

RTP

To simulate an RTP transfer in test mode, create a transfer with moov-wallet as the source payment method and rtp-credit as the destination. The rtp-credit payment method only appears for bank accounts with routing numbers that are RTP eligible.

Use 021000021 as an RTP-enabled routing number in test mode.

You can simulate RTP failures and rejections by using these specific transfer amounts. These amounts result in real time failures and the linked bank account entering an errored state.

If you would prefer to use the API to simulate a failure, you can trigger the RTP failure in test mode by entering any of the return amount codes as the value. For example, to simulate an invalid account, enter 7203 as the value.

{
  "amount": {
    "currency": "USD",
    "value": 7203
  },
  "facilitatorFee": {
    "total": 0
  }
}

ACH returns

You can simulate a few ACH return scenarios during different transfer stages. Trigger ACH returns in test mode by entering any of the return amount codes listed below as the value when creating a transfer. For example, to simulate insufficient funds, enter 5501 as the value.

{
  "amount": {
    "currency": "USD",
    "value": 5501
  },
  "facilitatorFee": {
    "total": 0
  }
}

A return is only triggered if the transfer type (for example, wallet-to-bank) is applicable to the particular return scenario and amount entered. For example, an R01 in test mode always occurs on the debit leg, after the transfer stage of debit origination. Accordingly, an R01 return cannot be triggered on a wallet-to-bank transfer, as that transfer type only consists of a credit leg. Creating a return scenario that does not apply to a corresponding transfer type results in a regular test transfer, not a test return.

Once you have created a transfer with an appropriate return code, Moov updates the transfer to failed or reversed based on the transfer stage (see ACH returns and exceptions for more information). The bank account status is also updated accordingly.

Disputes

Dispute evidence

Bank accounts

To simulate an instant micro-deposit verification in test mode, enter 0001 as the instant verification code.

To simulate traditional micro-deposit verification in test mode, enter 0 for both amounts: [0,0], and the bank account verification will succeed. If you input any other amount, the bank account verification won't complete.

Plaid

To test linking bank accounts with Plaid, pass env: "sandbox" into the payload in the Moov.js initialization. You can pass any token as the processor token and Moov links default account data:

  RoutingNumber: "011401533",
  AccountNumber: "1111222233330000",
  AccountType:   "checking",
  Mask:          "0000"