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

 

Home > User Documentation > Aria6 Release Notes > Aria6 Release 10.1

Aria6 Release 10.1

 

Note: This is a draft version of the Aria Release Notes - Version 10.1, which is currently available in Stage Future.

Overview

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

Release Date

Stage Future Release Date

 3/2/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 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 UI since 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.

For New Accounts

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

Getting Here: Click Accounts > Create an account > Scroll to Billing Info > Payment Method

  • 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.

For Existing Accounts

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

Click Accounts > Select an account > Account Overview > Form of Payment > Add Payment Method > Tokenized Direct Debit

Enter a value in one of the following fields.

  • In the first field, enter a previously approved token ID that has a signed mandate associated with it.
  • In the second field, enter the International Bank Account Number (IBAN) to generate a new token. This field is ignored if there is a value in the field above it.

 

Application Fixes

  • When edit access was false for a user role, the user was able to make edits (TICKET-13575)
  • Fields for read, create, edit and delete were not automatically unchecked when the read option was not selected in the user role configuration screen (TICKET-13594)
  • Internal error message occurred when attempting to create a new contract (TICKET-13612)
  • Copy Config changed/updated virtual time (TICKET-13690)
  • Plan set to rollover on third payment was rolling over on second payment (TICKET-13691)
  • Approve button sometimes opened re-calculate page from pending invoices (TICKET-13733)
  • Canadian tax was not validated correctly (TICKET-13754)
  • Plans took excessive time to open in the UI (TICKET-13814)
  • “Select a field" option not available when removing field in "refine search" option (TICKET-13947)
  • Batch job error alert email had incorrect timestamp (TICKET-14148)
  • The usage period was displayed as 'NA' when the first invoice was voided and regenerated (TICKET-6745)

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, 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

  • Error message was displayed when using update_coupon with a discount bundle (TICKET-13144)
  • Get_promotion_details had a data type mismatch (TICKET-13672)
  • 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 mismatch occurred in <product> field for several Get APIs (TICKET-13818)
  • Save_paypal_bill_agreement required that a payment method was entered (TICKET-13824)
  • Get_promo_plan_set_details documentation had incorrect data type defined (TICKET-13826)
  • Get_inventory_item_details documentation had incorrect data type defined (TICKET-13855)
  • In Admintools APIs, <error_msg> was returned as integer/long (TICKET-13856)
  • Get_plan_service_details_m was incorrectly validating some fields (TICKET-13863)
  • Replacing an account plan using an API or UI and invoicing unbilled usage creates a database error (TICKET-13865)
  • Account was not created even though the create_acct_hierarchy API was successful (TICKET-13895)
  • Queued plan changes were terminating supplemental plans incorrectly (TICKET-13904)
  • Modify_acct_universal_contract generated an error when modifying contract (TICKET-13909)
  • Data type for input field <include_translation> was not working properly in multiple APIs with Java SDK (TICKET-14043)
  • Indentation issue corrected in get_invoice_information (TICKET-14189)

 


You must to post a comment.
Last modified
14:30, 1 Mar 2017

Tags

This page has no custom tags.

Classifications

This page has no classifications.