Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 26

Aria6 Release 26

Overview

Enhancements and fixes to Aria functionality for this release are described below.

Release Date

Stage Future Release Date

11-December-2019

Production Release Date

15-January-2020

System Requirements

Supported Browsers

  • Chrome 63
  • Firefox 52
  • IE11
  • Safari 11 on MacOS 

Screen Resolution

1024 x 768 or higher

Release 26 Contents

Application Features 

Collection Groups List Performance Improvement in Aria UI (DEV-9520)

This feature improves the performance of the Collection Groups Collection Groups list screen in the Aria UI. This will be especially helpful if you have many collection groups.

Vertex Cloud Connector Support (DEV-9692)

Enhancements have been made to the Aria Vertex O-Series tax integration to support both the on-premises and the cloud hosted functionality. Previously, the Aria Vertex tax integration supported only the on-premises version. Now, when a tax request comes from Aria, either the Vertex Cloud Connector endpoint or the on-premises version can be used to calculate taxes using the Vertex tax engine.

The enhancements enable Aria to support versions 6 through 8 of Vertex Indirect Tax O Series and versions 6 through 9 of Vertex Cloud Indirect Tax.

The following taxable actions are supported:

  • Invoice tax quotation and posting
  • Void tax posting
  • Refund-reversal tax posting
  • Write-off
  • Credit Memo 

Application Fixes 

  • If you enter more than a 2 decimal value when assigning or editing custom rates for a master plan or supplemental plan, the Custom Rate Value is no longer rounded off to 2 decimal points. Aria now honors the Custom Rate Value based on the client parameter settings for RECURRING_RATE_PER_UNIT_SCALE and USAGE_RATE_PER_UNIT_SCALE. The Customer Rate Value can be set at a number other than 2 based on client need. (TICKET-17627)​

API Features 

Use CyberSource to Authorize Tokenized Credit Cards (DEV-9701)

If you use the CyberSource payment gateway, you can now authorize a tokenized credit card that was previously authenticated outside of Aria without having to repeat the authentication in Aria. To do so, use the new <bill_agreement_id> and <cc_id> inputs or the pre-existing <bill_seq> input in the authorize_electronic_payment API.

CIT and MIT Support Available for WorldPay Transactions (DEV-9702)

Aria's integration with the WorldPay payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Discover credit card. When you use WorldPay to process a Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

  • assign_acct_plan
  • authorize_electronic_payment
  • cancel_acct_plan
  • collect_from_account
  • create_acct_billing_group
  • create_acct_complete
  • create_order
  • create_order_with_plan
  • manage_pending_invoice
  • replace_acct_plan
  • settle_account_balance
  • update_acct_billing_group
  • update_acct_complete
  • update_acct_plan
  • update_acct_plan_multi
  • update_payment_method
  • validate_acct_fraud_scoring

Note:  Adyen, and possibly other payment gateways, will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.  

CIT and MIT Support Available for CyberSource Transactions (DEV-9706)

Aria's integration with the CyberSource payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Mastercard and Discover credit cards. When you use CyberSource to process a Mastercard or Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

  • assign_acct_plan
  • authorize_electronic_payment
  • cancel_acct_plan
  • collect_from_account
  • create_acct_billing_group
  • create_acct_complete
  • create_order
  • create_order_with_plan
  • manage_pending_invoice
  • replace_acct_plan
  • settle_account_balance
  • update_acct_billing_group
  • update_acct_complete
  • update_acct_plan
  • update_acct_plan_multi
  • update_payment_method
  • validate_acct_fraud_scoring

Note:  Adyen, and possibly other payment gateways, will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.

CIT and MIT Support Available for Adyen Transactions (DEV-9711)

Aria's integration with the Adyen payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Mastercard and Discover credit cards. When you use Adyen to process a Mastercard or Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

  • assign_acct_plan
  • authorize_electronic_payment
  • cancel_acct_plan
  • collect_from_account
  • create_acct_billing_group
  • create_acct_complete
  • create_order
  • create_order_with_plan
  • manage_pending_invoice
  • replace_acct_plan
  • settle_account_balance
  • update_acct_billing_group
  • update_acct_complete
  • update_acct_plan
  • update_acct_plan_multi
  • update_payment_method
  • validate_acct_fraud_scoring

Note:  Adyen, and possibly other payment gateways, will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.  

CIT and MIT Support Available for Braintree Transactions (DEV-9712)

Aria's integration with the Braintree payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Mastercard and Discover credit cards. When you use Braintree to process a Mastercard or Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

  • assign_acct_plan
  • authorize_electronic_payment
  • cancel_acct_plan
  • collect_from_account
  • create_acct_billing_group
  • create_acct_complete
  • create_order
  • create_order_with_plan
  • manage_pending_invoice
  • replace_acct_plan
  • settle_account_balance
  • update_acct_billing_group
  • update_acct_complete
  • update_acct_plan
  • update_acct_plan_multi
  • update_payment_method
  • validate_acct_fraud_scoring

Note:  Adyen, and possibly other payment gateways, will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.

CIT and MIT Support Available for Ingenico Transactions (DEV-9728)

Aria's integration with the Ingenico payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Visa, Mastercard, and Discover credit cards. When you use Ingenico to process a Visa, Mastercard, or Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

  • assign_acct_plan
  • authorize_electronic_payment
  • cancel_acct_plan
  • collect_from_account
  • create_acct_billing_group
  • create_acct_complete
  • create_order
  • create_order_with_plan
  • manage_pending_invoice
  • replace_acct_plan
  • settle_account_balance
  • update_acct_billing_group
  • update_acct_complete
  • update_acct_plan
  • update_acct_plan_multi
  • update_payment_method
  • validate_acct_fraud_scoring

Note:  Adyen, and possibly other payment gateways, will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.

API Fixes 

  • When you call the delete_coupons API and pass a value into the <coupon_nos> field, this error is no longer returned: "Coupon code value cannot be blank". (TICKET-17628)

WSDL File Locations

Stage Current

US https://secure.current.stage.ariasystems.net/api/Advanced/wsdl/26/complete-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/Advanced/wsdl/26/complete-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/Advanced/wsdl/26/complete-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/Advanced/wsdl/26/complete-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/Advanced/wsdl/26/complete-doc_literal_wrapped.wsdl

Production

US https://secure.ariasystems.net/api/Advanced/wsdl/26/complete-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/Advanced/wsdl/26/complete-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/Advanced/wsdl/26/complete-doc_literal_wrapped.wsdl

Object Query WSDL Files

Stage Current

US https://secure.current.stage.ariasystems.net/api/AriaQuery/wsdl/26/integration_services-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/AriaQuery/wsdl/26/integration_services-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/AriaQuery/wsdl/26/integration_services-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/AriaQuery/wsdl/26/integration_services-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/AriaQuery/wsdl/26/integration_services-doc_literal_wrapped.wsdl

Production

US https://secure.ariasystems.net/api/AriaQuery/wsdl/26/integration_services-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/AriaQuery/wsdl/26/integration_services-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/AriaQuery/wsdl/26/integration_services-doc_literal_wrapped.wsdl
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by CXone Expert ®