Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 33

Aria6 Release 33

Overview

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

Release Date

Stage Future Release Date

 24-November-2020

Production Release Date

 12-January-2021

System Requirements

Supported Browsers

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

Screen Resolution

1024 x 768 or higher

Developer Central Enhancements

We are happy to announce that on 11 December 2020, we will update Aria’s product documentation site with these enhancements:

For more information, please see this quick guide.

Release 33 Contents

Application Features

Use Direct Post to Collect Direct Debit Payments (DEV-9985)

  • If you use Direct Post, you can now collect payments made using the Direct Debit payment method. To do so:
  1. Set the pre-existing One Time Collection field to Yes in your Direct Post configuration in the Aria application (under Configuration > Client Settings > USS Reg Configuration > new or existing configuration).
  2. Pass DD into the <formOfPayment> field in your Form of Payment Page.
  3. Pass values into the additional new fields required for Direct Debit payments as described in Form of Payment Page Inputs.
  • In addition, if you pass DD into the <formOfPayment> input in your Form of Payment Page and you leave the <bban> or <iban> field blank, this new error is returned:
  • error_key: serverbankaccountrequired
  • error_code: 1010
  • error message: bban or iban

Statement BCC Email Address is now available for invoices (DEV-10041)

The Aria application has a new feature called Statement BCC Email Address. This gives you the ability to include a BCC email address in invoice statement emails. Statement BCC Email Address can be configured in Configuration > Notifications > Notification Settings > Statement BCC Email Address.

Application Fixes 

  • You can now view an Account's Supplemental Plans in the Aria UI at [selected Account] > Plans & Services > Supplemental Plans tab as expected when the number of Supplemental Plans exceeds 30. Previously, when the number of Supplemental Plans exceeded 30, this screen returned a "Data table warning" error, and no plan details were displayed. (TICKET-18170)
  • Import processing enhancements now allow you to overwrite import data for an existing client more than once (from Configuration > Utilities > Import) when that client has data configured in account fields (more on importing a configuration is here). (TICKET-18176)
  • Your accounts now move out of dunning, as expected (TICKET-18269):
    • If you have your Auto-Rollback Dunning When Balance is Zero parameter set to True (under Configuration > Billing > Invoice Settings); and
    • The account balance is paid in full after multiple unapplied payments from a voided invoice were applied to the outstanding balance. 
  • When you create a recurring service credit, the interval that you specified in the Months between credits field is now saved correctly. (TICKET-18296)

API Features

Ingenico Level 2 and Level 3 Enhancements (DEV-9945)

This feature adds Level 2 and 3 data processing support to the Ingenico payment gateway. Level 2 data are included for determining a card's affluence, which may influence your marketing initiatives, and Level 3 data includes invoice line item details that allow you to receive lower transactional fees from credit card processors. Level 2 and Level 3 data are supported by the Credit Card and Tokenized Credit Card payment methods and the Visa® and Mastercard® card types.

Note: Aria sends Level 2 and 3 data to Ingenico only when making a single API call to collect a payment. Level 2/3 data cannot be sent to Ingenico when payment collection is made with 2 separate API calls (e.g., using authorize_electronic_payment to authorize a $3 payment and collect_from_account to capture the $3 authorized amount).

Learn more about Aria's integration with the Ingenico payment gateway from here.

Use Direct Post to Collect Direct Debit Payments (DEV-9985)

  • If you use Direct Post, you can now collect payments made using the Direct Debit payment method. To do so:
  1. Pass 1 into the pre-existing <do_one_time_collection> field in the set_reg_uss_config_params API.
  1. Pass DD into the <formOfPayment> field in your Form of Payment Page.
  2. Pass values into the additional new fields required for Direct Debit payments as described in Form of Payment Page Inputs.
  • In addition, if you pass DD into the <formOfPayment> input in your Form of Payment Page and you leave the <bban> or <iban> field blank, this new error is returned:
  • error_key: serverbankaccountrequired
  • error_code: 1010
  • error message: bban or iban

Ingenico UK Direct Debit - New Payment Method (DEV-10017)

The Ingenico payment gateway now processes Direct Debit transactions for United Kingdom (UK)-based payments. The existing <mandate_id> input field will be honored now for the Direct Debit Basic Bank Account Number (BBAN) payment method for payments and refunds.

This enhancement applies to the following APIs:

Learn more about Aria's integration with the Ingenico payment gateway from here.

Promo Code Error Code Corrected in get_promotion_details (DEV-10076)

If you pass an invalid <promo_cd> into the get_promotion_details API, error code 1016 is returned, as expected, instead of error code 0.

API Fixes 

  • If the ban_acct API is run without the <days_to_restore> input field populated, a message with error code 1016 is now generated stating that "Ban requests must specify a valid restoration date between 1 and 28 days in the future." Please note that, if the <date_to_restore> input field is populated, the <days_to_restore> field is ignored. (TICKET-3650)
  • API calls to get_acct_preview_statement no longer trigger the "Account Service Plan Contract Expired" provisioning event (event 125). (TICKET-18272)
  • A payment authorization is now correctly processed as an authorization instead of a payment when you use the Ingenico payment gateway and you (TICKET-18279): This means that the authorize_electronic_payment API now returns the <proc_status_text> output PENDING_APPROVAL (authorization successful) instead of CAPTURE_REQUESTED (payment completed). Then a subsequent collection will use the existing authorization completed for the same amount, instead of ignoring that authorization.

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

US https://secure.ariasystems.net/api/AriaQuery/wsdl/33/integration_services-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/AriaQuery/wsdl/33/integration_services-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/AriaQuery/wsdl/33/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 ®