Pre-Requisites: SCA (Strong Cardholder Authentication) (This document explains SCA implementation and configurations).
As discussed Scenario 2 focuses mainly:
Switch Interface or Restart Contactless with CVM Required
The config must be changed since we are ignoring Re-Authorise with Online PIN.
byte[] configSca = {(byte) 0x30, (byte) 0xF0, (byte) 0x00, (byte) 0x00};
//SIRCC, check for card support of contact/CDCVM. ROP not supported
Once your config is set, ACTION_TYPE_PINRequest and ACTION_TYPE_IdentificationRequired are converted to ACTION_TYPE_CDCVerificationMethod in the ARKOS 1.8.3 version and AMANACQ 1.2.2 version to force for switch Interface or Restart Contactless with CVM Required.
Your transactions will be either fall-forwarded or restarted with Reader CVM Required Limit to zero and
Reader Contactless Floor Limit to zero.
In addition to the Bulletin 33 of NexoFAST, we support ACTION_TYPE_PinRetry. Upon receiving an invalid PIN, the action type is called and it either restarts with Reader CVM Required Limit to zero and
Reader Contactless Floor Limit to zero or fall-forward.
If the pin is invalid, you will get a message “Invalid pin, please insert card” or “Invalid pin, present card again” depending on the card. (Dual interface or contactless only)
If the pin try limit is exceeded, you will get a message “Declined Pin Limit Exceeded Please Contact Issuer".
The pin try limit has to be set in your acquirer/payment gateway as an ARC that will be converted to an action type.
In our case, we have ARC 75 for the pin try limit exceeded that will be converted to a new ACTION_TYPE(ACTION_TYPE_PINFailed) that we included outside the NexoFAST spec.
This new Action type has been added in AMANACQ 1.2.2 version.
case ActionType7Code_PINF:
TRACE_WARN("Parsing non Nexo value PINF");
elemSet_FromUInt8(action, ACTION_TYPE,ACTION_TYPE_PINFailed);
Example of an acceptor authorisation response with the PINF action type