Overview
Enhancements and fixes to Aria functionality for this release are described below.
Overview
Enhancements and fixes to Aria functionality for this release are described below.
Release Date
Stage Future Release Date
2-February-2021
Production Release Date
02-March-2021
System Requirements
Supported Browsers
Screen Resolution
1024 x 768 or higher
Release 34 Contents
The Aria Ingenico integration is now enhanced by the addition of the Account Updater, which automatically updates your account holders’ card information (Tokenized cards only). This feature supports Visa® and Mastercard® card types issued in the U.S. and Canada.
When an account holder's card information is updated (associated with the particular token), Ingenico provides the "push" notification via the Webhooks tool, which sends real-time data from one application to another based on system events as part of a larger integration. You must configure an endpoint that will act as a "listener" to receive these notifications. Please refer to the Ingenico payment gateway page linked below for more information.
Aria now supports the Webhook Key and Webhook Secret configuration fields from Ingenico that are used to validate the incoming Webhooks notifications. These fields accept alphanumerics and special characters. Set these two field values on the Ingenico configuration center for your merchant account. After doing so, configure those values in your Ingenico payment gateway configuration. Once Webhooks is enabled, you can subscribe to the token.updated and token.deleted events supported by the Account Updater.
Notes:
The Webhook Key and Webhook Secret values are honored in the Ingenico Payment Gateway configuration only and not the Collection Group configuration at this time.
Learn more about the Ingenico payment gateway from here.
Aria’s latest iteration of the Data Streaming Web Service includes non-subscription offering (order item) objects and coupon objects. See the Data Streaming Logical Object Model for details.
This feature enhances Aria's proration functionality by enabling full proration for plans upgraded via the Single Line Upgrade feature, which you can enable in your Aria instance by requesting that your Aria representative enable the parameter <single_line_upgrade>.
With <single_line_upgrade> enabled, Aria will now calculate Single-Line Downgrades with LIFO (Last-In, First-Out) processing for plan quantity decreases.
Notes:
Plan replacements will continue to use the standard proration logic, even for clients using Single Line Upgrade.
The Credit Note template has been enhanced to support the existing replacement string ‘insertPlainMaskedFormPymt’. The Statement and invoice templates could already use the ‘insertPlainMaskedFormPymt’ replacement string, and with this enhancement it is now available in the Credit Note template as well.
This feature significantly improves the performance for some contract-expiration-related pre-invoice housekeeping jobs, especially for Aria clients with thousands of plan instances and contracts.
Adyen now supports Apple payment methods for recurring payments, including the ApplePay payment method (38) and the new Tokenized ApplePay payment method (47). When an ApplePay indirect payment takes place outside of Aria, the payment is recorded using the record_alternative_payment_m API. Once the external payment is recorded, Aria performs a capture request and receives the respective notification.
More information on the Adyen payment gateway can be accessed from here.
The parameter Allow contract to end even when PI on contract is not billed through the contract end date has been added (Configuration > Billing > Invoice Settings). This allows Aria to end contracts with the following actions when a plan instance on a contract is not billed: Terminate Service and Billing, Terminate Service and Billing and Prorate Final Invoice, and Rollover to a Plan and/or a Rate Schedule. This is enabled when value is set to True (default is False).
Learn more about managing Invoice settings from here.
When configuring an event notification (Configuration > Notification > Events) to send a data payload using a secure token via the Simplified Account Data via Secure HTTP (Name Value Pairs and XML Document) methods and the OAuth 2.0 Authentication Type, a token is used to transmit the payload to the Destination URL. This enhancement now ensures that, if the cached token expires, the token is automatically refreshed upon unsuccessful payload submission and the new token will be used to successfully transmit a payload.
Learn more about Event Notifications from here.
Refund transactions generated from Aria now appear on the Ingenico payment portal (the Aria refund payment ID appears in the Ingenico Merchant Reference ID field). Previously, only original payments were supported and not payment refunds. Refunds can be generated for any payment method accepted by Ingenico (e.g., credit card, tokenized credit card, Giropay, etc.).
Learn more about refunds from here.
The Merchant Account ID field has been added as part of the Braintree integration for Payment Gateways and Collection Groups within Aria. This allows Braintree clients with international accounts and multiple currencies to be billed using FreshBooks® accounting software. This also allows Braintree to transfer tokens associated with the Merchant ID field.
The Merchant Account ID field is used to identify the currency type of the merchant as part of the Payment Gateway/Collection Group. If no Merchant Account ID is entered, the transaction will process with the default currency configured for the merchant (existing Braintree integration behavior). For example, if USD is the default currency configured for the merchant but GBP is configured at the Merchant Account ID field, Braintree will process the payment with the GBP currency.
More information about Aria's Braintree payment integration is here.
This feature introduces the behavior of excluding from your Data Stream individual usage records discarded when their associated pending invoice is discarded. Aria has updated the Invoice Logical Object Model with a new property, ‘usage_record_status’, that will indicate whether the aforementioned usage records were discarded or unbilled.
The Webhook Secret field has been added as part of the Ingenico Account Updater enhancement for Payment Gateways and Collection Groups within Aria. This field along with the existing Secret API Key field will be masked to enhance data security.
These fields appear in the description for DEV-10008.
More information about the Ingenico payment gateway can be accessed from here.
This feature introduces two new Usage Provisioning Events related to discarding pending invoices:
Electronic payments are now re-applied to an invoice during credit memo application of the invoice. This will ensure the payment is applied to other open items on the invoice. (TICKET-18147)
The Ingenico 3D Secure integration now supports transactions using the American Express® (Amex) card in addition to the Visa® and Mastercard® card types.
The existing Amex credit card type is now supported in Ingenico's 3DS configuration for the following APIs:
Enter the following inputs to enable this feature:
authorize_3dsecure_m
Input | Description |
---|---|
<cc_prefix> | First six digits of Amex card (starting with 3) |
authorize_electronic_payment_m
Input | Description |
---|---|
<cc_number> | Amex card number (starting with 3 - 15-character numeric value) |
<attempt_3d_secure> | True |
update_payment_method_m
Input | Description |
---|---|
<cc_number> | Amex card number (starting with 3 - 15-character numeric value) |
To learn more about the Ingenico payment gateway, click here.
This features adds the input field <client_acct_id> as an alternate input for <acct_no> to the following API calls:
This feature enhances Aria’s Sovos Tax Engine integration so calls to the create_acct_complete_m API with 10 or more Non-Subscription Offerings (NSOs, or order items) can return the complete set of applicable tax data. Aria has increased the number of characters supported in returns from the Sovos tax processor so tax calculation can be displayed on customers' check-out screens.
Previously, passing more than 9 arrays to the <master_plan_nso_list> field resulted in a “failed to calculate taxes” error.
Aria has enhanced the get_all_acct_contracts_m API with additional filtering options as described below:
Stage Current
US | https://secure.current.stage.ariasys...l_wrapped.wsdl |
EUR | None |
AUS | https://secure.current.stage.aus.ari...l_wrapped.wsdl |
Stage Future
US | https://secure.future.stage.ariasyst...l_wrapped.wsdl |
EUR | https://secure.future.stage.cph.aria...l_wrapped.wsdl |
AUS | https://secure.future.stage.aus.aria...l_wrapped.wsdl |
Production
US | https://secure.ariasystems.net/api/A...l_wrapped.wsdl |
EUR | https://secure.prod.cph.ariasystems....l_wrapped.wsdl |
AUS | https://secure.prod.aus.ariasystems....l_wrapped.wsdl |
Stage Current
US | https://secure.current.stage.ariasys...l_wrapped.wsdl |
EUR | None |
AUS | https://secure.current.stage.aus.ari...l_wrapped.wsdl |
Stage Future
US | https://secure.future.stage.ariasyst...l_wrapped.wsdl |
EUR | https://secure.future.stage.cph.aria...l_wrapped.wsdl |
AUS | https://secure.future.stage.aus.aria...l_wrapped.wsdl |
Production
US | https://secure.ariasystems.net/api/A...l_wrapped.wsdl |
EUR | https://secure.prod.cph.ariasystems....l_wrapped.wsdl |
AUS | https://secure.prod.aus.ariasystems....l_wrapped.wsdl |