---
title: No Auth Orders
slug: extensions/OS5s7qY7f4c1rmLvEXAT3
docTags: 
createdAt: 2025-12-14T14:23:42.414Z
---

# No Auth Orders

## No Auth Overview

No auth orders are defined by Forter as orders where the credit card or payment instrument has been rejected by the payment processor.

## Why Does Forter need to receive No Auth transactions?

While Forter doesn’t decision these orders (we always return a `not reviewed` decision), it is important for Forter to receive these attempts because the behavior can be a relevant indicator in identifying fraud.

## Mapping No-Auth Orders

No-auth orders should be stored on the payment instrument and passed to the `ForterOrder.ds` file with the authorization response similar to how successfully authorized orders get passed to Forter. The relevant *not authorized* processor response should be mapped to the relevent fields so that Forter's server recognizes it as a not authorized order and returns a `not reviewed` response.

## Configure `JsonResponseOutput.processorAction`

In addition to mapping the authorization response for no-auth orders, make sure to configure the relevant `JsonResponseOutput.processorAction` to handle the `not reviewed` decision for these cases.

As no auth orders cannot be captured, you will need to make sure your cartridge is configured to cancel these orders and display the relevant message to the customer.

## Testing Resources

For gateway-specific resources to test no-auth/processor declines in sandbox, please see our dedicated [Gateway Resources Section](docId\:m_-9DLvE_cBkG3ZV7vAVL) which includes specific card numbers and testing cases relevant to your specific gateway.

If your gateway is not listed, please contact your dedicated onboarding team for additional resources and materials.