# CardConnect test cards

> Test card numbers, bank accounts and other details for CardConnect's sandbox, and the result each one gives.

Use these details to try payments in a CardConnect 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.

CardConnect's sandbox is its UAT (user acceptance testing) environment. Fiserv's guide says to request a UAT merchant ID and API credentials from integrationdelivery@fiserv.com, and an ACH-enabled test merchant account if you want to test ACH. UAT results come from an emulator of the processor your test merchant ID uses: the standard UAT merchant ID uses First Data North, and the cards below are for First Data North and Rapid Connect.

:::note[Where these details come from]
These are CardConnect's test details, not ours. They were copied from Fiserv's [CardPointe Gateway Developer Guide](https://developer.fiserv.com/product/CardPointe/docs/?path=docs/documentation/CardPointeGatewayDeveloperGuides.md) on 19 October 2026, and were correct on that date as far as that page shows. CardConnect can change or withdraw them at any time, and we can't confirm that they work. Check Fiserv's page for the current details, and ask CardConnect if one doesn't behave as described.
:::

## How to choose a test result

- Connect your UAT account here: enter the UAT site URL and API credentials Fiserv gives you in the CardConnect connection settings. Results then come from the emulator for the processor your UAT merchant ID uses ([CardPointe Gateway Developer Guide](https://developer.fiserv.com/product/CardPointe/docs/?path=docs/documentation/CardPointeGatewayDeveloperGuides.md)).
- On the First Data North and Rapid Connect emulators, the card number sets most declines, and an amount from $1,000 to $1,999 sets the processor response code. Enter the amount at the checkout in dollars, for example `1116.00`.
- The last three characters of the billing ZIP code set the address check result. Enter it in the billing address at checkout: we ask for a billing address only while **Require address (AVS)** is switched on in the connection settings (it's on by default).
- Enter CVC triggers in the checkout's CVC field.
- For ACH, switch on **Enable ACH** in the connection settings, and ask Fiserv for an ACH-enabled test merchant account.

## Cards

Fiserv's guide doesn't say which expiry date or CVC to use. On the First Data North and Rapid Connect emulators, any card number with the right prefix and length that passes the Luhn check is approved.

### Successful payments

| Card | Number | Notes |
| --- | --- | --- |
| Visa | `4788 2500 0012 1443` | |
| Visa | `4111 1111 1111 1111` | Used in our own tests (with CVC `441` and an expiry date three years ahead) |
| Mastercard | `5454 5454 5454 5454` | |
| American Express | `3714 496353 98431` | |
| Discover | `6011 0009 9550 0000` | |
| Diners Club | `3643 8999 9600 16` | |
| JCB | `3528 0000 0000 0007` | |

### Declines and errors

Where the two emulators give different results, First Data North's comes first. Fiserv lists the same declines for Mastercard and Discover cards on its page.

| Number or trigger | Result |
| --- | --- |
| `4387 7511 1111 1038` | Declined: do not honour |
| `4387 7511 1111 1053` | Declined: insufficient funds (First Data North), or declined (Rapid Connect) |
| `4387 7511 1111 1046` | Declined: wrong expiry date (First Data North), or expired card (Rapid Connect) |
| `4387 7511 1111 1020` | Declined: refer to issuer (First Data North), or call for authorisation (Rapid Connect) |
| Amount from $1,000 to $1,999 ($1,001 to $1,999 on Rapid Connect) | Returns the processor response code given by the last three digits of the whole-dollar amount. For example, $1,116 returns Rapid Connect code 116: declined, insufficient funds |
| `4387 7501 0101 0101` with an amount of $6.00 or more | Partial approval: only $5.00 approved |

### Address and CVC checks

The address check result is set by the last three characters of the billing ZIP code. These endings work on the First Data North, Rapid Connect, First Data Nashville, Paymentech Tampa, American Express and Vantiv emulators (US ZIP codes only for American Express and Vantiv). Chase Paymentech uses different endings, which Fiserv lists separately. Any other ZIP code returns the processor's normal result. The CVC values work on the First Data North and Rapid Connect emulators. Fiserv lists more ZIP code endings on its page.

| Value | Result |
| --- | --- |
| ZIP code ending `224` | Address and ZIP code match (AVS code X) |
| ZIP code ending `225` | Address and ZIP code match (AVS code Y) |
| ZIP code ending `111` | Address matches, ZIP code doesn't (AVS code A): declined for Visa, Mastercard and American Express |
| ZIP code ending `226` | ZIP code matches, address doesn't (AVS code Z) |
| ZIP code ending `112` | Neither address nor ZIP code matches (AVS code N) |
| ZIP code ending `221` | Address unavailable (AVS code U) |
| ZIP code ending `218` | Issuer system unavailable (AVS code R) |
| CVC `112` (`1112` for American Express) | CVC matches |
| CVC `111` (`1111` for American Express) | CVC doesn't match |
| CVC `222` (`2222` for American Express) | CVC not processed |
| CVC `333` (`3333` for American Express) | CVC result unknown |

## ACH (US bank accounts)

| Routing number | Account number | Result |
| --- | --- | --- |
| `036001808` or `011401533` | Any | Accepted |
| `011401533` | `1234123412341234` (checking) | Accepted. Used in our own tests |
| An invalid routing number | Any | Error: not a valid routing number |