Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 22

Aria6 Release 22


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

Release Date

Stage Future Release Date


Production Release Date


System Requirements

Supported Browsers

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

Screen Resolution

1024 x 768 or higher

Application Features 

Send or Suppress Statements Based on Balance and/or Transaction Type (DEV-8741)

In your Statement Sending options, you can now specify that statements should be sent or suppressed based on whether a statement has a zero balance and/or a particular transaction type is included in the statement. 

Cardholder- and Merchant-Initiated Transactions Implemented in Cybersource Payment Processor for Visa (DEV-9312)

This feature enhances Aria's Worldpay ​payment processor integration by sending flags distinguishing Cardholder Initiated Transactions​ (CIT) and Merchant Initiated Transactions (MIT)​ for Visa credit card transactions​​​, to comply with Visa's Payment Card Industry Data Security Standards (PCI DSS). These standards establish a set of 12 requirements for safeguarding sensitive information and controlling data access.

This feature applies to Credit Card and Tokenized Credit Ca​rd payment methods and leverages existing API ​input <recurring_processing_model_ind> and output <proc_initial_auth_txn_id> in the following API’s:

Note: This feature has not yet been implemented for MasterCard credit card transactions. 

Payment Processor / Gateway Deprecation (DEV-9480)

The following Payment Gateways/Processors, which are no longer in use or supported, have been removed from the Aria UI via the Configuration > Payments > Payment Gateways > New drop-down.

  • ​First Data Paypoint
  • Global Collect
  • Merchant eSolutions
  • MercuryPay
  • TNS​​

Application Fixes 

  • An alert pop up no longer displays when creating a new service via the Products > Plans > Services > Create ​New service tabs. (TICKET-17088) 
  • Refunds and authorization (auth) reversals are now processed with the same payment gateway that was used for the original payment/auth. This is true even if the customer involved was added to a different collection group in the timeframe between the payment/auth and the refund/auth reversal. (TICKET-17293)
  • The Plan Details Modified event is now triggered as expected when a child plan is added or removed from a parent plan. The Plan Rate Schedule Modified event is now triggered as expected when the default rate schedule is changed. (TICKET-17296)
  • Aria now sets the next bill date for a rollover supplemental plan to its provision date when activated. (TICKET-17302)
  • When replacing a supplemental plan with a recurring arrears service on a customer's billing anniversary, Aria no longer charges for the old recurring arrears service. (TICKET-17359)
  • Account Searches using "By Invoice No.", when enabled via the Configuration > Security > Account Access > Search > Pages tabs, are now successfully performed irrespective of any other search method types configured. (TICKET-17378)

API Features

API Fixes 

  • These 3 fixes have been implemented: (TICKET-16779)
    • When you replace a supplemental plan and record usage for the new supplemental plan, the usage is billed for the new plan, as expected.
    • When you assign a supplemental plan with an <alt_proration_start_date> and record usage for the plan, that <alt_proration_start_date> is honored as the usage start date on the next anniversary invoice, as expected.
    • If you assign a supplemental plan with a billing period greater than one month in the middle of a billing cycle: a) the next bill date is now calculated correctly, and b) the usage is now billed for the plan on the next anniversary invoice.
  • Refunds and authorization (auth) reversals are now processed with the same payment gateway that was used for the original payment/auth. This is true even if the customer involved was added to a different collection group in the timeframe between the payment/auth and the refund/auth reversal. (TICKET-17293)

WSDL File Locations

Stage Current

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

Stage Future

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


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

Object Query WSDL Files

Stage Current

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

Stage Future

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


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


This page has no custom tags.


This page has no classifications.