Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!

 

Home > Aria Crescendo Documentation > Aria Crescendo Release Notes > Release 10.1

Release 10.1

This article applies to:Aria Crescendo

Overview

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

Release Date

Production Release Date

 3/27/2017

System Requirements

Supported Browsers

  • Firefox 39
  • Chrome 44
  • Internet Explorer 9, 10, 11 

Java Settings

Java 7.0​​

Screen Resolution

1024 x 768 or higher

Application 

Features

Fixes

API

Features

Fixes


Application Features

Ingenico Payment Gateway Adds Tokenized SEPA Direct Debit as a Payment Method (DEV-8093)

This feature adds SEPA Tokenized Direct Debit as a supported payment method for the Ingenico payment gateway.

Note: The API portion of this change was implemented as part of Ingenico Payment Gateway Adds Tokenized SEPA Direct Debit as a Payment Method - API (DEV-8093).

This payment method requires that the account holder sign a mandate before it can be implemented. Payments can only be made with SEPA Tokenized Direct Debit after the mandate has been approved with the record_mandate_approval_m API. It is the client's full responsibility to ensure that the end user signs a paper mandate that verifies that this electronic mandate is valid. Neither Aria or the payment gateway can intervene if the end user disputes signing the mandate later.

The client must collect in the account's currency, which must be a currency supported by SEPA Direct Debit.

Because this payment method requires setting up the client mandate in advance, it is not available as an alternative one-time payment method when creating orders.

If the payment status for a SEPA Direct Debit payment returns as “PENDING_APPROVAL”, you must approve the payment on the Ingenico website after a mandate has been signed. You cannot approve the mandate and resubmit the payment using the Aria U Isince Ingenico does not currently provide an update capability via APIs.

Add SEPA Direct Debit as a Payment Method

When you add SEPA Direct Debit to an account as a payment method, there are additional fields you must specify.

Getting Here:

Click Accounts > Create an account > Add  a plan > Payment Method

or

Click Accounts > Select an account > Plans > Select a plan > Primary Payment Method or Secondary Payment Method

When you select Tokenized Direct Debit with the account assigned to the Ingenico payment gateway, you see the following options:

  • If you select Token/Agreement ID, you must enter a previously approved token ID that has a signed mandate associated with it.

  • If you select Direct Debit, you must enter the International Bank Account Number (IBAN) to generate a new token.

 

Application Fixes

  • Assign master plan with monthly rollover did not consider the assign effective date (TICKET-12889)
  • Could not assign a supplemental plan on an anniversary if a rollover was scheduled (TICKET-12890)
  • Execute link was missing for grandchild plan, when non-mandatory and mandatory grandchild were queued (TICKET-12924)
  • Duplicate records were logged under the Plan History tab when replacing a plan (TICKET-12973)
  • Data table warning displayed in UI when creating a new destination contact for a supplemental plan (TICKET-13142)
  • Unable to remove dispute hold (TICKET-13252)
  • Usage period on first full invoice ended after start date of the recurring period (TICKET-13451)
  • UI was not creating account when selecting an account group using the Pass Test payment gateway (TICKET-13510)
  • Supplemental plan rollover did not occur when assigning master plan and supplemental plan together (TICKET-13519)
  • Short cycle invoice was not generated when account was created with a plan having rollover in days and a retroactive start date (TICKET-13524)
  • Add new plan in UI with parent pay for existing account was not working properly (TICKET-13590)
  • Void transactions not captured in Aria CSR Activity (TICKET-13622)
  • Copy Config changed/updated virtual time (TICKET-13690)
  • Anniversary supplemental plan change did not trigger "Account Supplemental Service Plan Modified" event (TICKET-13706)
  • Approve button sometimes opened re-calculate page from pending invoices (TICKET-13733)
  • Discount Bundle and Discount Rule coupon were not applying for invoice and prorated invoice (TICKET-13735)
  • Usage was not recorded when usage units were in tens of billions (TICKET-13739)
  • Canadian tax was not validated correctly (TICKET-13754)
  • Incorrect period interval shown in Custom Price Breakdown (TICKET-13769)
  • Cash Credit Reason Codes were not working correctly (TICKET-13790)
  • Plans took excessive time to open in the UI (TICKET-13814)
  • Incorrect proportional allocation of charges occurred when an account had more than one master plan instance with same services (TICKET-13825)
  • Could not create product field with a type of "date" using the custom date format mask (TICKET-13848)
  • Activation charge line item was not included in invoice while update units on anniversary (TICKET-13854)
  • When some master plan instances were assigned with create_acct_complete_m, the same set of plans were duplicated under queued plans (TICKET-13857)
  • Sorting was incorrect in some columns in the Products and Marketing modules (TICKET-13861)
  • Replacing an account plan using an API or UI and invoicing unbilled usage creates a database error (TICKET-13865)
  • Could not edit "date" type plan instance field in account section (TICKET-13876)
  • Legal Entities section had some UI Bugs (TICKET-13896)
  • Could not view a custom billing interval on a plan's rate schedule (TICKET-13897)
  • The client defined ID for cancelled plans showed the client plan ID, not the client plan instance ID in the UI (TICKET-13898)
  • Plan unit fulfillment batch was incorrectly included in the eom_invoicer batch (TICKET-13899)
  • “Select a field" option not available when removing field in "refine search" option (TICKET-13947)
  • New dropdown values were not saved under the Product field (TICKET-14031)
  • The usage period was displayed as 'NA' when the first invoice was voided and regenerated (TICKET-6745)
  • Current_unapplied_svc_crdt_bal in the creditUtil package was not working (TICKET-8882)

API Features

Ingenico Payment Gateway Adds Tokenized SEPA Direct Debit as a Payment Method - API (DEV-8093)

This feature adds support for SEPA Direct Debit as a payment method for the Ingenico payment gateway.

New API

A new API, record_mandate_approval_m, that supports the SEPA Direct Debit payment method that is being added to the Ingenico payment gateway with this release.

This API electronically verifies that the end user (Aria account holder) has physically signed a SEPA Direct Debit mandate. Payments can only be made with SEPA Tokenized Direct Debit after the mandate has been approved with this API. It is the client's full responsibility to ensure that the end user signs a paper mandate that verifies that this electronic mandate is valid. Neither Aria or the payment gateway can intervene if the end user disputes signing the mandate later.

The client must collect in the account's currency, which must be a currency supported by SEPA Direct Debit.

Because this payment method requires setting up the client mandate in advance, it is not available as an alternative one-time payment method when creating orders.

If the payment status for a SEPA Direct Debit payment returns as “authorized” in the output of the APIs that create or retrieve a tokenized SEPA DD payment, you must approve the payment on the Ingenico website after a mandate has been signed. You cannot approve the mandate and resubmit the payment using Aria APIs since Ingenico does not currently provide an update capability via APIs.

Modified APIs

The following APIs have been modified to support SEPA DD.

The following fields have been added

Field Name Field Type Description
bill_agreement_id String Unique ID of the bill agreement (also referred to as a token).
mandate_id String Unique ID of the mandate returned for Direct Debit and Tokenized Direct Debit payment methods.

API Fixes

  • In get_acct_plans_m, the <available_from_dt>/<available_to_dt> values were not displayed properly in the  API response (TICKET-12779)
  • Duplicate records were logged under the 'Plan History' tab while assigning custom rates via update API's (TICKET-12971)
  • Get_invoices_to_writeoff_or_dispute_m  was not returning the correct invoice total (TICKET-13026)
  • Could not update credit template with valid fields in update_credit_template_m API (TICKET-13399)
  • The <client_plan_id> was changed if the plan was edited/updated using <plan_no> with <edit_directive> set to 2 (TICKET-13558)
  • Get_writeoff_details_m was not returning values unless <acct_no> was specified in addition to <writeoff_transaction_id> (TICKET-13589)
  • Get_supp_fields_m was generating an error on empty fields in the system (TICKET-13624)
  • Get_supp_field_details_m returned all locale details rather than translations which have been only defined with the <account> field (TICKET-13625)
  • Set_usg_threshold_m did not save threshold levels when called through API Live (TICKET-13628)
  • Update_supp_obj_field_m generated a 500 Internal Server Error (TICKET-13673)
  • Multiple issues addressed with update_acct_plan_multi_m  (TICKET-13729)
  • Update_acct_plan_multi_m generated an error when assigning grand child plan (TICKET-13730)
  • Update_acct_plan_multi_m was not generating an error when passing an invalid supplemental plan no (TICKET-13737)
  • Update_acct_plan_multi_m did not include <invoice_no> in its response (TICKET-13743)
  • 500 Internal Server Error occurred when using edit_coa_m (TICKET-13757)
  • Data type mismatches occurred in get discount rule APIs (TICKET-13794)
  • Data type mismatches occurred in Finance module Get APIs (TICKET-13816)
  • Data type mismatch occurred in <product> field for several Get APIs (TICKET-13818)
  • Save_paypal_bill_agreement required that a payment method was entered (TICKET-13824)
  • In Admintools APIs, <error_msg> was returned as integer/long (TICKET-13856)
  • Get_plan_service_details_m was incorrectly validating some fields (TICKET-13863)
  • Data type issues occurred in some service APIs (TICKET-13864)
  • Get plan APIs were not working correctly (TICKET-13870)
  • Usage period was not displaying in generated invoices and the invoice was not generating for usage service when using update_acct_plan_multi_m (TICKET-13873)
  • Update_acct_plan_multi_m did not generate proration details on plan cancellation (TICKET-13912)
  • Data type for input field <include_translation> was not working properly in multiple APIs with Java SDK (TICKET-14043)
  • Update_acct_plan_multi_m output fields required a data type correction (TICKET-14143)
  • Extra or duplicate payment methods were included in the get_acct_payment_methods_and_terms_m API response (TICKET-14149)
  • Copy_acct_payment_method_m sometimes caused duplication of the payment method (TICKET-9834)

 

You must to post a comment.
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.