On This Page

Non-Payment Authentication

Non-Payment Authentication (NPA) requests enable a merchant to authenticate a customer without a transaction. A non-payment use case can be used for such tasks as adding a card to a merchant website, updating cardholder information on file, or to verify a cardholder's identity when creating a token for future use. The same authentication used during the checking enrollment process is used for NPA. Non-payment use cases are enabled using a combination of the

payerAuthEnrollService_messageCategory

and

payerAuthEnrollService_authenticationIndicator

values. For example to add a card to a loyalty program, set the Message Category value to

and the Authentication Indicator value to

. For other possible NPA use cases, refer to the other possible values for

payerAuthEnrollService_messageCategory

. The

payerAuthEnrollService_messageCategory

value must be set to

(non-payment authentication) to specify that the authentication is not for a transaction.

Card-Specific Requirements

Some payment cards require information to be collected during a transaction.

card_cardType: This field is required when the card type is Cartes Bancaires, JCB, UPI, or Meeza.
payerAuthEnrollService_defaultCard: This field is recommended for Discover ProtectBuy.
payerAuthEnrollService_MCC: This field is required when the card type is Cartes Bancaires.
payerAuthEnrollService_merchantName: This field is required for Visa Secure travel.
payerAuthEnrollService_productCode: This field is required for American Express SafeKey (U.S.) when the product code is
AIR
for an airline purchase.
shipTo_city: This field is required only for American Express SafeKey (US).
shipTo_country: This field is required only for American Express SafeKey (US).
shipTo_postalCode: This field is required for American Express SafeKey (US).
shipTo_street1: This field is required only for American Express SafeKey (US).

shipTo_street2: This field is required only for American Express SafeKey (US.)

Country-Specific Requirements

These fields are required for transactions in specific countries.

payerAuthEnrollService_merchantScore: This field is required for transactions processed in France.
payerAuthEnrollService_ merchantCountrycode: For Meeza transactions, this value must be set to
EG
when Egypt is not set as the country in the merchant configuration during merchant boarding.
invoiceHeader_ merchantDescriptorCountrye: For Meeza transactions, this value must be set to
EG
when Egypt is not set as the country in the merchant configuration during merchant boarding.
billTo_state: This field is required for transactions in the US and Canada.
billTo_city: This field is required for transactions in the US and Canada.
: This field is required when the
billTo_country
field value is
US
or
CA
.

shipTo_county: This field is required when the
shipTo_country
field value is
CA
,
US
, or
China
.

shipTo_postalCode: This field is required when the
shipTo_country
field value is
US
or
CA
.

Processor-Specific Requirements

These fields are required by specific processors for transactions.

transactionModee transactionMode: This field is required only for merchants in Saudi Arabia.

Endpoint

Set the

ccAuthService_run

field to

true

Send the request to:

Production:

https://ics2ws.ic3.com/commerce/1.x/transactionProcessor

Test:

https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor