CyberSource

Cardholder-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MIT) for Visa, MasterCard, American Express, and Discover

This feature sends flags distinguishing cardholder-initiated transactions (CIT) and merchant-initiated transactions (MIT) within the <recurring_processing_model_ind> parameter of the following API calls:

• assign_acct_plan_m
• authorize_electronic_payment_m
• cancel_acct_plan_m
• collect_from_account_m
• create_acct_billing_group_m
• create_acct_complete_m
• create_order_m
• create_order_with_plan_m
• manage_pending_invoice_m
• replace_acct_plan_m
• settle_account_balance_m
• update_acct_billing_group_m
• update_acct_complete_m
• update_acct_plan_m
• update_acct_plan_multi_m
• update_payment_method_m
• validate_acct_fraud_scoring_m

The input values for the <recurring_processing_model_ind> are the following:

• 0: Cardholder-Initiated Transaction—Credentials on File: a credit card transaction initiated by the cardholder for a new order or a plan upgrade that uses a credit card that is currently stored in Aria. (Default)
• 1: Cardholder-Initiated Transaction—a credit card transaction initiated by the cardholder for a new account or creating an order that uses an alternate credit card that is not currently stored in Aria.
• 2: Merchant-Initiated Transaction—Standing Instruction – Recurring: a credit card transaction initiated by Aria’s clients for a recurring charge that uses a credit card that is currently stored in Aria.
• 3: Merchant-Initiated Transaction—Unscheduled Credentials on File: a credit card transaction initiated by Aria’s clients for a non-recurring charge (one-time order or plan upgrade) that uses a credit card that is currently stored in Aria.

The output field of this call is <proc_initial_auth_txn_id>.

The American Express card type can now be used also for CITs and MITs. This applies to both the Credit Card and Tokenized Credit Card pay methods.

Getting Here: Add or edit a payment gateway and/or collection group.

UI Configuration

► Merchant Account Details

The Merchant Account Details tab appears as shown:

This screen contains the following fields:

Field	Description
Merchant id	A unique value that identifies a merchant in the CyberSource system. CyberSource merchants have access to a CyberSource business center, and this ID is used to log into the Business Center. The ID is also submitted with every payment transaction sent from Aria to CyberSource.
server host	Identifies the server host end-point where transactions are sent. The default setting for CyberSource is ics2wstest.ic3.com.
server port	(optional): Identifies the server port where transactions are sent.
keys	You can obtain a Private Key from CyberSource's Business Center. CyberSource supports many different types of Private Keys, but Aria recommends the SOAP Tookit API Key (which has been fully tested and verified by Aria).
Accepts refunds beyond the payment processor's standard refund window	Click this checkbox if the payment processor can accept refunds outside the normal payment window.

► Processing Options

The Processing Options tab appears as shown:

This screen contains the following fields:

Field	Description
3DS Authentication Settings Note: If you want to use 3D Secure (3DS) authentication 2.0, complete all fields under 3DS Authentication Settings. If you leave these fields blank, Aria will use 3DS 1.0. Please contact your payment gateway representative for more information.
JWT Org Unit ID	This is a non-secure value (part of orgUnitid claim) that CyberSource provides for usage within the JWT 3dSecure transactions.
JWT Api Identifier	This is a non-secure value (part of iss claim) that CyberSource provides for usage within the JWT 3dSecure transactions.
JWT Api Key	This is a unique value (i.e., password) that should be known only to you and CyberSource's 3dSecure provider Cardinal.
3DS Client JS Library Url	This is the URL of the client side JavaScript library that is included on the checkout page to interact with the 3DS authentication provider. A standard default value will be used if no value is supplied.
Payer Authentication Transaction Mode	This is a transaction mode identifier which identifies the channel from which the transaction originates. Value Description M MOTO (Mail Order Telephone Order R Retail S eCommerce P Mobile Device T Tablet This defaults to S for eCommerce if no values are provided or there are no special rules that dictate that the initial transaction can be recurring.
Level2/Level3 Data Options
Send Level2/Level3 Data in the payment request	This has been added for the AMEX and GPN back-end processors (No is the default). The AMEX and GPN processors support the following card types: Supported Card Type Processor VISA, Mastercard, American Express and DIscover GPN American Express AMEX This enables Level 2 and Level 3 data to be sent with VISA, Mastercard, and Discover payments (American Express supports Level 2 data only; Mastercard does not support $0 payments). Level 2 and Level 3 data can be enabled at the Payment Gateway and Collection Group levels. As a reminder, by providing Level 2 and Level 3 data, merchants qualify for lower interchange fees, which merchants pay to card-issuing banks for each card purchase. Notes: The back-end processor is established at the time of Payment Gateway and Collection Group creation. A maximum of 98 invoice lines are allowed. Anything beyond that is truncated into the 99th line.
Refund Options
Send Capture Request ID Only for Refunds	Only sends the Capture Request ID for TCC refunds - leaves out the Subscription ID and Capture Request Token. Turn this on if your CyberSource account has Network Tokens enabled, or refunds will fail.

► Field Options

The Field Options tab appears as shown:

Note: Image has been altered for presentation.

This screen contains the following fields:

Field	Description
shipFrom_postalCode	This is the postal code from which the order will be shipped.
billTo_ipAddress	This value is used for fraud protection.
shipTo_firstName	This is the first name of the customer to which the order will be shipped.
shipTo_lastName	This is the last name of the customer to which the order will be shipped.
shipTo_street1	This is the street1 address to which the order will be shipped.
shipTo_street2	This is the street2 address to which the order will be shipped.
shipTo_city	This is the city to which the order will be shipped.
shipTo_state	This is the state/province to which the order will be shipped.
shipTo_postalCode	This is the postal code to which the order will be shipped.
shipTo_country	This is the country to which the order will be shipped.
afsService_run	This determines whether or not the Advanced Fraud Service should be used (true/false).
afsService_customRiskModel	This is the merchant-defined Risk Model for the Advanced Fraud Service.
merchantDefinedData_(fields 1 through 20)	This is the merchant-defined data used for the Advanced Fraud Service (fields 1-20).
deviceFingerprintID	This ID improves the user verification process and further minimizes identity fraud.
ccAuthService_commerceindicator	This represents the recurring billing indicator.

► CVV/AVS Conditions

Error codes can be returned to Aria for specific Card Verification Value (CVV) and Address Verification Service (AVS) responses. You may need to contact the payment processor directly so that they do not reject the result regardless of the settings at these tabs.

► P12 Authentication Method

The P12 Authentication tab appears as shown:

Select the P12 Certificate file, assign a password and click Upload. From here, you can attempt a payment and verify the payment result.

Backend Processors

• Chase Paymentech (Salem)
• Streamline
• Global Payments

Links

• Technical Reference