In­App Transactions

For in-app transactions, include the following required fields in the authorization request:

nbillTo_city

nbillTo_country

nbillTo_email

nbillTo_firstName

nbillTo_lastName

nbillTo_postalCode—required only for transactions in the U.S. and Canada.

nbillTo_state—required only for transactions in the U.S. and Canada.

nbillTo_street1

ncard_accountNumber—set to the token value that you received from the token service provider.

ncard_cardType—CyberSource strongly recommends that you send the card type even if it is optional for your processor. Omitting the card type can cause the transaction to be processed with the wrong card type.

ncard_expirationMonth—set to the token expiration month that you received from the token service provider.

ncard_expirationYear—set to the token expiration year that you received from the token service provider.

nccAuthService_cavv—for 3D Secure in-app transactions, set to the 3D Secure cryptogram. Otherwise, set to the network token cryptogram.

nccAuthService_commerceIndicator

nccAuthService_networkTokenCryptogram

nccAuthService_run—set to true.

nmerchantID

nmerchantReferenceCode

npurchaseTotals_currency

npurchaseTotals_grandTotalAmount or item_#_unitPrice

npaymentNetworkToken_transactionType

Include 3D Secure data in the following fields:

nFor Visa requests, include the ccAuthService_cavv field set to the Visa Secure cryptogram.

nFor Mastercard requests, include:

lucaf_authenticationData—set to the Identity Check cryptogram.

lucaf_collectionIndicator—set to 2.

nFor JCB requests, include the ccAuthService_cavv field set to the J/Secure cryptogram.

See API Fields for:

nDetailed descriptions of these required request fields

nOptional request fields

nReply fields

After a successful authorization request, the rest of the credit card processing proceeds as described in Credit Card Services Using the Simple Order API (PDF | HTML).