Supported Features
- Card-specific system overrides
- Backend-processor-specific configuration for associated Collection Account Groups
- Ability to create a stand-alone credit when a refund cannot otherwise be created. Creating a stand-alone credit posts a credit to the payment card on file for the transaction and posts a stand-alone credit to CyberSource for the refund amount instead of issuing a true refund
- Tokenized credit card expiry notifications
- 3D Secure (3DS) authentication (currently, CyberSource's 3DS only supports Visa, Mastercard, American Express, and
Discover) - Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for Visa, Mastercard, and Discover credit cards
Cardholder-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MIT) for Visa, MasterCard 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>.
Aria Configuration Fields
Getting Here: Add or edit a payment gateway and/or collection group.
- 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.
- 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).
- 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.
- Payer Authentication Settings: If you want to use 3D Secure (3DS) authentication 2.0, complete all fields under Payer Authentication Settings. If you leave these fields blank, Aria will use 3DS 1.0. Please contact your payment gateway representative for more information.
Backend Processors
- Chase Paymentech (Salem)
- Streamline
- Global Payments
Specifying a Backend Processor
Within the Aria UI under Configuration > Payment > Collection Groups, you can specify a backend processor when creating a Collection Group.
Configuration Notes
-
If you use CyberSource as your payment gateway and you have Advanced Fraud Services enabled, you must complete the following fields in your payment gateway options in Aria based on information provided to you by CyberSource:
- afsService_customRiskModel
- afsService_run
- Fields beginning with merchantDefinedData_field
-
If you plan to use tokenized credit cards as a payment method, you must enable user profiles in CyberSource.