Home > Aria Crescendo Documentation > Aria Release Notes > Release 24

Release 24

Overview

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

Release Date

Stage Future Release Date

29-August-2019

Production Release Date

19-September-2019

System Requirements

Supported Browsers

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

Screen Resolution

1024 x 768 or higher

Release 24 Contents

Application Features

Replacement Strings "insertItemTotalDiscAmt" and "insertItemNetPrice" Now Display Two-Digit Decimal Precision in the Statement Template (DEV-8593)

In your customer's statements, the replacement strings “insertItemTotalDiscAmt” and "insertItemNetPrice” now format the price/amount with​​ two-di​git decimal precision. The following replacement strings have also been modified to support two-digit decimal precision in statements:

  • insertItemMonthlyAmount
  • insertItemInlineDiscAmt
  • insertItemOffsetDiscAmt
  • insertNettermsAcctDunBal

Performance Improvement in Account Updater Batch Process (DEV-9358)

The performance of Aria's batch process that runs Chase Paymentech's Account Updater has been improved.

Aria has removed the following links from the Master Plan Instance and Supplemental Plan Instance screens ([Specific Account] > Plans > [Plan Instance ID link for suspended plan instance]) in the Aria Application for suspended plan instances:

  • Replace Plan
  • Remove Plan
  • Change Plan Units

This change eliminates the ability to initiate these actions on suspended plan instances, which would result in an error.

View of Plan in Active Status:

dev-9368.png

View of Plan in Suspended Status:

dev-9368-2.png

Voided/Out-Of-Band Electronic Credit Transaction Deprecated (DEV-9619)

The "out-of-band electronic credit" and "voided out-of-band electronic credit" transaction types are no longer in use and have been deprecated in any locations where one or both of them were previously available on the following screens in the Aria application:​

  • Configuration > Notifications > Events > Financial Transactions;
  • Configuration > Notifications > Statement Sending > Selected Transaction Typ​es; 
  • Configuration > GL Code Mappings > Transaction Types > New;
  • Configuration > Client Settings > Locale Settings > New.

Braintree Payment Processor Support for 3D Secure 1.0 (DEV-9676)

This feature enhances Aria's integration with the Braintree Payment Processor Braintree Payment Processor by adding support for 3D Secure 1.0. 3D Secure 1.0.

3D Secure is a XMLprotocol that provides an additional security layer for online card transactions.

Application Fixes 

  • An error no longer occurs when you remove the activation fee while rebilling an invoice. (TICKET-15751)
  • An empty “Plan Details Modified” event payload (Event ID–1214), if configured in the Products Event Group, is no longer triggered when a Plan is deleted from the Product Catalog. This is also applicable to the deletion of other Product Catalog objects including Services, Usage Types, and Non-Subscription Offerings. The following Product Event Group’s modify events, if configured, are no longer triggered when a Plan, Service, Usage Type, or Non-Subscription Offering is deleted from the Product Catalog: (TICKET-17463)
    Event Name Event ID Description
    Plan Details Modified 1214 Existing Plan Details Modified
    Service Modified 1209 Existing Service is Modified
    Usage Type Modified 1212 Existing Usage Type is Modified
    Non-subscription Offering Details Modified 1218 Existing Non-subscription Offering Details is Modified
  • When an account has more than three electronic payment methods configured, the "Apply Payment" page now displays the expected input fields when ACH (Electronic Check) or Direct Debit is chosen, allowing successful payments. (TICKET-17512)
  • You can now successfully update an account's Billing Group ([Specified Account] > Plans > Edit button) that includes a Birthdate field value for the Statement Contact. Previously, pre-populated date values in this field caused the Billing Group update to fail because of how Aria validated the date format. (TICKET-17525)
  • When a supplemental plan instance is activated, the nightly Aria batch invoicer is now made to use any custom rates assigned to the plan’s activation service in lieu of using the plan’s activation service rate from the product catalog, which should only occur in a replacement plan scenario. (TICKET-17528)
  • The <proration_text>, <adv_billing_period_total_days> and <proration_remaining_days> field values are now being returned in get_invoice_details_m API response as expected. This also occurs as expected when passing the fulfillment_directive as "1"  in update_acct_plan_unit_instance_m API. (TICKET-17530) 

API Features 

Identify Transaction Type in Payment Transactions (DEV-9576)

If you use Chase Paymentech, you can now tell that payment gateway which transaction type is involved (examples: single or recurring transaction) when you process a customer's payment information. To do so:

  • Pass the relevant transaction type into a new input array called <proc_field_override> in any of these APIs: assign_acct_plan_m, authorize_electronic_payment_m, collect_from_account_m, create_acct_billing_group_m, create_acct_complete_m, create_acct_hierarchy, create_order_m, create_order_with_plans_m, manage_pending_invoice_m, replace_acct_plan_m, settle_acct_balance_m, update_acct_billing_group_m, update_acct_complete_m, update_acct_plan_m, update_acct_plan_multi_m, update_payment_method_m, and validate_acct_fraud_scoring_m; or
  • When you call the set_reg_uss_config_params_m API to create a Direct Post configuration, pass the relevant <transaction_type> into the <in_reg_uss_config_params> array.

    You can also use the Aria application to specify the transaction type when you create a Direct Post configuration.

Note: The transaction type that you pass into an API will override the default transaction type that you specified in your configuration settings for Chase Paymentech.

Please see the API documentation for more information.

Identify Cardholder Initiated and Merchant Initiated Transactions with Chase Paymentech (DEV-9578)

Aria's ​Chase Paymentech integration has been enhanced with support for the Cardholder Initiated Transaction​ (CIT)/Merchant Initiated Transaction (MIT) feature for the Mastercard and Discover credit cards. CIT/MIT support for Visa was introduced in Release 17 (8/16/2018); support for American Express (AMEX) was introduced in Release 42 (4/19/22). This feature applies to the credit card and tokenized credit ca​rd payment methods. If you use Chase Paymentech as your payment gateway and process a VIsa, Mastercard, AMEX or Discover payment, you can now specify whether the transaction was initiated by the cardholder or merchant. To do so, use the pre-existing ​input <recurring_processing_model_ind> and output <proc_initial_auth_txn_id> in these APIs:

get_client_plans_all_m Performance Improvement (DEV-9610)

The get_client_plans_all_m API has been fine-tuned to enhance overall performance. There are no functional changes to this API.

Voided/Out-Of-Band Electronic Credit Transaction Deprecated (DEV-9619)

The "out-of-band electronic credit" and "voided out-of-band electronic credit" transaction types are no longer in use and have been deprecated as described below:

Object Query APIs list_payment_methods(_m) No Longer Return the “Click&Buy” and “PayByCash” Payment Methods (DEV-9624)

The object query APIs list_payment_methods_m and list_payment_methods ​no longer return the disabled Click&Buy and PayByCash​​ payment methods.​  Aditionally, ​those payment methods are no longer available for selection on the "​Create New Payment Method" screen in the Aria user interface. ​​With the introduction of the new 'disabled_ind' column, the screen  has been adjusted to display the records with "no_display_ind = 0 AND disabled_ind = 0".

clipboard_eb159e08e5b2933f089a0d679a6537958.png

Set Notification Template Group at Account Level in create_acct_complete_m API (DEV-9644)

You can now assign a Notification Template Group at the account level using the create_acct_complete_m API. New input fields <notification_template_group_no> and <client_notification_template_group_id> inputs have been added as alternate optional inputs to support this assignment.

Additionally, the <client_notification_template_group_id> input field has been added to the following APIs:

Braintree Payment Processor Support for 3D Secure 1.0 (DEV-9676)

This feature enhances Aria's integration with the Braintree Payment Processor Braintree Payment Processor by adding support for 3D Secure 1.0. 3D Secure 1.0.

To invoke 3D Secure authentication for payments:

  1. call the payment API authorize_electronic_payment_m authorize_electronic_payment or update_payment_method_m update_payment_method with the field <attempt_3d_secure> set to "true";
  2. pass the values of <client_auth_token> and <cc_single_use_token> values returned by the API call in step 1 to your custom Direct Post payment page; and
  3. pass the value of <client_3ds_nonce> returned by your payment page in a call to API authorize_3dsecure_m. authorize_3dsecure.

New Inputs For API Calls

API Call

New Input Fields

authorize_3dsecure

<proc_field_override>: Array of processor-specific fields.

  • <proc_field_name>: The name of the processor-specific field.
  • <proc_field_value>: The value associated with the proc_field_name.

API Call

New Input Fields

authorize_3dsecure_m

<proc_field_override>: Array of processor-specific fields.

  • <proc_field_name>: The name of the processor-specific field.
  • <proc_field_value>: The value associated with the proc_field_name.

New Outputs For API Calls

API Call

New Output Fields

authorize_electronic_payment

<proc_3dsecure_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.

validate_acct_fraud_scoring

<proc_3dsecure_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.
authorize_3dsecure <processor_id>: The Payment Processor ID used for external collection or authorization.

API Call

New Output Fields

authorize_electronic_payment_m

<proc_3dsecure_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.

validate_acct_fraud_scoring_m

<proc_3dsecure_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.

update_payment_method_m

<proc_3dsecure_auth_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.
authorize_3dsecure_m <processor_id>: The Payment Processor ID used for external collection or authorization.

API Fixes 

  • XML Exception error: Unexpected element: CDATA was being displayed in authorize_electronic_payment_m API response instead of in the correct XML format (TICKET-16091)
  • If you use Chase Paymentech as your payment gateway, you no longer get an error when you complete a credit card authorization reversal. (TICKET-17510)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

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

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by CXone Expert ®