---
title: Credit Card Tests
slug: extensions/uStV1iNWzpyGf78_m6jHx
docTags: 
createdAt: 2025-12-14T14:23:42.414Z
---

# Credit Card Testing

Below is an outline of recommended credit card testing and flows. Please make sure to configure your processorResponse.json file according to the different available Forter decisions (**approve**, **decline**, and **not reviewed**). Also, please refer to the \[No Auth Tests]\(./Processor Decline\_No Auth Testing.md) to test the processor decline/no auth flows for credit cards.

## Declined by Forter

- Guest Checkout Decline:  customer makes a purchase with email address `decline@forter.com` using a valid test card
- Registered Customer Decline: Customer creates an account using `decline@forter.com` and then logs into new account and places order.

## Approved by Forter

- Registered customer: Customer logs in and does a checkout using the email `approve@forter.com` and a valid test card for the transaction
- Guest Checkout Approve: Customer makes a purchase as a guest using any email and a valid test card

## Not Reviewed by Forter

By default a `"Not Reviewed"` decision will be routed to the decision node with condition `ForterResponse.JsonResponseOutput.processorAction === 'notReviewed’`. In order to customize the behavior for this flow, use the `ForterResponse.JsonResponseOutput.processorAction` to split it from the **"skipCapture"** flow and **insert your merchant-specific logic for a **`"Not Reviewed"`** use case**.

- Customer makes a purchase using a valid test card and the email address `notreviewed@forter.com` Or customer places a transaction using a No-Auth test card (see [No Auth Testing](docId\:NUDYinpkVls9mzAuZTyKN) for more details on testing this flow)

## Test Email addresses

- Place a Guest Checkout order in Sandbox or UAT using any valid test email address
- Place a Registered Customer order in your sandbox environment using a saved credit card including any valid registered (test) customer account email address