- 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
- Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for Visa, Mastercard, and Discover credit cards
Aria Configuration Fields
- 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: The Private Key can be obtained from CyberSource's Business Center following the Simple Order API instructions for retrieving the file.
- 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.
- Chase Paymentech (Salem)
- 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.
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:
- Fields beginning with merchantDefinedData_field
If you plan to use tokenized credit cards as a payment method, you must enable user profiles in CyberSource.
Regarding Processor/Gateway Integration Certifications
If you previously implemented a custom payment processor/gateway integration, you likely completed a certification process with that processor/gateway. Aria maintains certifications with each of the processors with which it integrates. Though you may wish to certify your Aria-related processor/gateway integration before going live on Aria, this is not necessary and could add significant time and Services costs to your Aria implementation process. Please consult your Aria Implementation representative for more detailed information.
Regarding Processor- and Gateway-specific Information
All Processor- and Gateway-specific information provided on Developer Central exists as publicly accessible information from the respective companies, and is presented here for your convenience. We update this information from time to time as necessary.