Aria6 Release 27

CIT and MIT Support Available for Vantiv Transactions (DEV-9716)

• Aria's integration with the Vantiv payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (CIT) for the Mastercard and Discover credit cards. This feature allows you to specify whether you are processing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.​
• To do so, use the pre-existing <recurring_processing_model_ind> ​input and <proc_initial_auth_txn_id> output in these APIs:

• validate_acct_fraud_scoring
• manage_pending_invoice
• collect_from_account
• settle_account_balance
• create_order_with_plans
• update_acct_complete
• authorize_electronic_payment

• The new Send orderSource as recurring for all transactions setting is now available in your payment gateway and/or collection group configuration for Vantiv. This new setting allows you to send the orderSource field* value to Vantiv as recurring, regardless of the value that you passed into the <recurring_processing_model_ind> field.

* The orderSource field indicates the type of payment. Please contact your Vantiv representative for more information.

Vertex O Series Version 9 Support (DEV-9763)

The Aria Vertex tax integration has been enhanced with support for Vertex O-Series version 9 for both the on-premises and the cloud hosted functionality. To use this new version of Vertex O-Series, enter 9 in the DocVersion field in your Vertex O-Series configuration.

Please contact your Vertex representative for more details.

New First Data Payeezy Endpoint for Tokenization (DEV-9775)

First Data Payeezy has changed its endpoint for credit card tokenization. This means that if you use Payeezy to process tokenized credit card payments, no later than March 15, 2020, you will need to update your Payeezy configuration settings. To do so, enter the required value in the new Transarmor Token field in your Payeezy configuration settings to connect to this new endpoint. This is required for only US merchants.

Please contact your Payeezy representative ​for more information.

Braintree Support for 3D Secure Authentication 2.0 (DEV-9730)

Aria's integration with the Braintree payment gateway has been enhanced with support for 3D Secure (3DS) authentication 2.0. The 3DS authentication feature provides additional fraud prevention when transactions are processed.

To perform 3DS authentication 2.0, use the following new fields in this API as described in the authorize_3dsecure documentation:

Please contact your Braintree representative ​for additional information about using 3DS 2.0.

Additional Fields To Be Anonymized (DEV-9747)

When you call the delete_acct_data API, the following additional account contact fields considered Personally Identifiable Information (PII) are now anonymized, as expected:

• <city>
• <locality>
• <zip>
• <cell_phone>
• <phone_suffix>
• <intl_cell_phone>
• <intl_work_phone>
• <fax_phone>
• <work_phone>
• <phone_country_code>

CyberSource Support for 3D Secure Authentication 2.0 (DEV-9765)

Aria's integration with the CyberSource payment gateway has been enhanced with support for 3D Secure (3DS) authentication 2.0. The 3DS authentication feature provides additional fraud prevention when transactions are processed.

To use 3DS 2.0:

1. Configure the Payer Authentication Settings in the Aria application's payment gateway and/or collection group screens for CyberSource; and
2. Use the following new fields in these APIs as described in the authorize_3dsecure documentation:
    

   APIs	New Inputs	New Outputs
   authorize_3dsecure authorize_electronic_payment	In the <proc_field_override> array: <payer_auth_reference_id> <payer_auth_transaction_id> <payer_auth_transaction_mode>	Allowable values in the <proc_3dsecure_data> array: <pa_3ds_form_action> <pa_3ds_js_lib_url> <payer_auth_reference_id> <payer_auth_transaction_id> The <proc_3dsecure_data> output array has been added to the authorize_3dsecure API.

Please contact your CyberSource representative ​for additional information about using 3DS 2.0.

Adyen Support for 3D Secure Authentication 2.0 (DEV-9766)

Aria's integration with the Adyen payment gateway has been enhanced with support for 3D Secure (3DS) authentication 2.0. The 3DS authentication feature provides additional fraud prevention when transactions are processed.

To use 3DS 2.0:

1. Configure the Payer Authentication Settings and API URL in the Aria application's payment gateway and/or collection group screens for Adyen; and
2. Use the following new fields in these APIs as described in the authorize_3dsecure documentation:

Please contact your Adyen representative ​for additional information about using 3DS 2.0.