Processor Decline/No Auth Testing

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), we like to receive these attempts as the behavior can be a relevant indicator in identifying fraud for instance, a fraudster may have a list of 20 stolen credit card numbers the first 19 card numbers used by the fraudster may already be disabled or closed accounts, but if the 20th card number is still valid and our models have already seen the previous 19 attempts, our system will be better able to understand and accurately decision and decline the order testing no auth orders no auth orders can be difficult to test in a sandbox environment due to a limited number of test cards available by most gateways for gateway specific resources to test no auth/processor declines in sandbox, please see our dedicated testing resources docid\ qi3l0gzkhuxibda plkdb 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 additionally, no auth orders will always receive a not reviewed decision from forter's models you will need to make sure that your processorresponse json output controller is properly configured and customized in order to handle a not reviewed decision