Testing Overview

testing overview in the following sections, you'll find the recommended testing and cartridge configuration paths required in order to ensure a smooth transition to listen mode please note that in addition to receiving valid credit card transactions, you should also be sending the following no auth orders (declined by processor) \[no auth]\( /processor decline no auth testing md) orders are defined by forter as orders where the credit card or payment instrument has been rejected by the payment processor 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 non credit card orders if you would like decisions on non credit card orders including orders paid fully by paypal , gift card , loyalty points , store credit , applepay , amazonpay , etc , these orders will require a dedicated object in the payment instrument file dedicated sandbox transactions should be made for each payment method using any valid email as well as the dedicated forter decision testing emails ( approve\@forter com , decline\@forter com , and notreviewed\@forter com ) you can find additional information about mapping and testing each payment method in the alternative payment methods (non credit card) tests docid\ d0pc5b5a45hhvcwvkr6cr section please contact your dedicated onboarding team to make sure that decisioning is enabled in sandbox for all applicable payment methods business manager configurations and processor actions the forterresponse jsonresponseoutput processoraction functions should be tested for each payment method and each forter decision (including not reviewed ) to ensure that all orders are being correctly handled and all flows are managed correctly prior to enabling approve/decline decisions in your production environment