Credit Card Tests

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 processor decline/no auth testing docid ocssuno9tq4mxct8z9up 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