Release 26

Enhancements to Account Creation Form (DEV-9409)

 

Changes have been made to the behavior of the Aria UI Account creation form at Accounts > Create New Account so that it no longer automatically assigns the default notify template method if you didn't select one when you created an account.

---

 

Collection Group at Billing Group Level Support for Tokenized Credit Cards (DEV-9472)

 

Aria now supports merchant accounts (collection groups) at a billing group level for tokenized credit cards (<pay_method>=13).  Support for non-tokenized credit cards (<pay_method>=1) was previously introduced.

 

Whenever a new “Tokenized Credit Card” Payment method (<pay_method>=13) is generated, Aria will look for the collection groups associated at the account level and collection groups associated at the billing group level and generate tokens from all the payment processors associated with the collection group.

 

Any API used to create or update a payment method is impacted by this change. These include the following:

• create_acct_complete_m
• update_acct_complete_m
• update_payment_method_m
• create_acct_billing_group_m
• update_acct_billing_group_m
• assign_acct_plan_m
• update_acct_plan_multi_m

The following Get APIs will retrieve the tokens for all collection groups associated at the billing group level:

• get_acct_details_all_m
• get_acct_hierarchy_details_m
• get_acct_billing_group_details_m

The following APIs will consider tokens in their processing:

• refresh_token_from_pmt_processor_m
• copy_acct_payment_method_m

---

 

Vertex Cloud Connector Support (DEV-9692)

 

Enhancements have been made to the Aria Vertex O-Series tax integration to support both the on-premises and the cloud hosted functionality. Previously, the Aria Vertex tax integration supported only the on-premises version. Now, when a tax request comes from Aria, either the Vertex Cloud Connector endpoint or the on-premises version can be used to calculate taxes using the Vertex tax engine.

The enhancements enable Aria to support versions 6 through 8 of Vertex Indirect Tax O Series and versions 6 through 9 of Vertex Cloud Indirect Tax.

The following taxable actions are supported:

• Invoice tax quotation and posting
• Void tax posting
• Refund-reversal tax posting
• Write-off
• Credit Memo 

---

 

Application Fixes 

 

• Links now appear as expected on the Master Plan Instance (MPI)​ Overview screen in the Aria UI.
  The system-wide default access settings of the links are now honored and the links will be displayed even when there is no client-level override of access settings.  When a plan is Active, the "Replace Plan," "Remove Plan Change," and "Plan Units" links should appear. (TICKET-17597)​

• In the Aria application, on the Change Plan Status screen, "Create One Time Order" is displayed as a supported operation only for plan statuses for which orders are allowed. In addition, "Create One Time Order (Only when billed Immediately)" is displayed for the statuses to which that condition applies. (TICKET-17619)

• If you enter more than a 2 decimal value when assigning or editing custom rates for a master plan or supplemental plan, the Custom Rate Value is no longer rounded off to 2 decimal points. Aria now honors the Custom Rate Value based on the client parameter settings for RECURRING_RATE_PER_UNIT_SCALE and USAGE_RATE_PER_UNIT_SCALE. The Customer Rate Value can be set at a number other than 2 based on client need. (TICKET-17627)​ ​

• When the client parameter <ENCODE_STATEMENT_VALUES> is set to ENCODE, currency symbols printed on HTML statements now display as expected. Previously, the already-encoded symbols were encoded again, causing them to display incorrectly. (TICKET-17635)

• An issue has been resolved which was causing negative Value Added Tax (VAT) to be calculated when there were discounts on a product and service credits were applied on a Master Plan Instance (MPI)/Account. This issue resulted in invoices with a negative pre-tax net total. Aria now prevents the excess discount line items so the pre-tax net total will be either 0 or positive. Once the pre-tax net total is 0 or positive, the net tax will no longer be negative. (TICKET-17640)

• Decimals in the full balance amount on the MPI detail screen in the Aria UI now display as expected when the client setting "Universal Override Currency Format Mask" (Configuration > Client Settings > Miscellaneous Settings) is set as "European Format." (TICKET-17647)

---

 

Tax-inclusive Order Line Items Correctly Identified (DEV-9498)

 

When you call the get_all_invoice_information_m API and the returned invoice details contain a tax-inclusive order line item, the <tax_inclusive_ind> output now correctly identifies that line item as tax-inclusive.

---

 

Use CyberSource to Authorize Tokenized Credit Cards (DEV-9701)

 

If you use the CyberSource payment gateway, you can now:

• Authorize a tokenized credit card that was previously authenticated outside of Aria without having to repeat the authentication in Aria. To do so, use the new <bill_agreement_id> and <cc_id> inputs or the pre-existing <bill_seq> input in the authorize_electronic_payment_m API; and
• Authorize a tokenized credit card when you change/add payment information. To do so, use the pre-existing <bill_agreeement_id> or <payment_method_no> input in the update_payment_method_m API.

---

 

CIT and MIT Support Available for WorldPay Transactions (DEV-9702)

 

Aria's integration with the WorldPay payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Discover credit card. When you use WorldPay to process a Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

assign_acct_plan_m authorize_electronic_payment_m cancel_acct_plan_m collect_from_account_m create_acct_billing_group_m create_acct_complete_m create_order_m  create_order_with_plan_m manage_pending_invoice_m

replace_acct_plan_m settle_account_balance_m update_acct_billing_group_m update_acct_complete_m update_acct_plan_m update_acct_plan_multi_m update_payment_method_m validate_acct_fraud_scoring_m

 

Note:  Adyen, and possibly other payment gateways will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.  

 

---

 

CIT and MIT Support Available for CyberSource Transactions (DEV-9706)

 

Aria's integration with the CyberSource payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Mastercard and Discover credit cards. When you use CyberSource to process a Mastercard or Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

assign_acct_plan_m authorize_electronic_payment_m cancel_acct_plan_m collect_from_account_m create_acct_billing_group_m create_acct_complete_m create_order_m  create_order_with_plan_m manage_pending_invoice_m

replace_acct_plan_m settle_account_balance_m update_acct_billing_group_m update_acct_complete_m update_acct_plan_m update_acct_plan_multi_m update_payment_method_m validate_acct_fraud_scoring_m

 

Note:  Adyen, and possibly other payment gateways, will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.

CIT and MIT Support Available for Adyen Transactions (DEV-9711)

 

Aria's integration with the Adyen payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Mastercard and Discover credit cards. When you use Adyen to process a Mastercard or Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

 

assign_acct_plan_m authorize_electronic_payment_m cancel_acct_plan_m collect_from_account_m create_acct_billing_group_m create_acct_complete_m create_order_m  create_order_with_plan_m manage_pending_invoice_m

replace_acct_plan_m settle_account_balance_m update_acct_billing_group_m update_acct_complete_m update_acct_plan_m update_acct_plan_multi_m update_payment_method_m validate_acct_fraud_scoring_m

 

Note:  Adyen, and possibly other payment gateways, will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.  

CIT and MIT Support Available for Braintree Transactions (DEV-9712)

 

Aria's integration with the Braintree payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Mastercard and Discover credit cards. When you use Braintree to process a Mastercard or Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

assign_acct_plan_m authorize_electronic_payment_m cancel_acct_plan_m collect_from_account_m create_acct_billing_group_m create_acct_complete_m create_order_m  create_order_with_plan_m manage_pending_invoice_m

replace_acct_plan_m settle_account_balance_m update_acct_billing_group_m update_acct_complete_m update_acct_plan_m update_acct_plan_multi_m update_payment_method_m validate_acct_fraud_scoring_m

 

Note:  Adyen, and possibly other payment gateways, will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.

CIT and MIT Support Available for Ingenico Transactions (DEV-9728)

 

Aria's integration with the Ingenico payment gateway has been enhanced with support for Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for the Visa, Mastercard, and Discover credit cards. When you use Ingenico to process a Visa, Mastercard, or Discover card transaction, you can now specify whether you are completing a cardholder- or merchant-initiated transaction and whether the card information is already stored in Aria.

To work with CIT/MIT, you can use the existing <recurring_processing_model_ind> input field and <proc_initial_auth_txn_id> output field in the following APIs:

assign_acct_plan_m authorize_electronic_payment_m cancel_acct_plan_m collect_from_account_m create_acct_billing_group_m create_acct_complete_m create_order_m  create_order_with_plan_m manage_pending_invoice_m

replace_acct_plan_m settle_account_balance_m update_acct_billing_group_m update_acct_complete_m update_acct_plan_m update_acct_plan_multi_m update_payment_method_m validate_acct_fraud_scoring_m

 

Note:  Adyen, and possibly other payment gateways, will require your customers to re-enter their credit cards before 31 October 2020 to comply with PSD2 (second Payment Services Directive) for recurring transactions. Please check with your payment gateway representative for more information.

 

 

API Fixes  

 

• When updating a supplemental field using the API call update_supp_obj_field_m, the fields <min_no_sel> and <max_no_sel> are now set to the values passed to the API call. Previously, both fields were reset to the value "1" despite values passed via the API call. (TICKET-17087)
• An error no longer occurs when you use the update_acct_plan_m API to change a plan's status from inactive/cancelled to active. (TICKET-17600)
• Master Plan Instances (MPI) are now being billed as expected when the plan is changed from pending activation to active through the update_acct_plan_m API. ​Additionally, any related Supplemental Plan Instance (SPI) is getting billed and any account level coupon discounts and surcharges are generated along with SPI billing.​ Accumulated GL (general ledger) details which contain both MPI and SPI information are now made ​​available for proration invoice generation. (TICKET-17623)
• Your specified minimum collection threshold is honored for only electronic payments and not for net terms payments recorded using the Aria application, as expected. (TICKET-17631)
• An issue has been resolved, which was allowing the update_acct_plan_multi_m​ API to add PI (plan instance) supplemental field values greater than the configured “Maximum Number Selections Allowed” despite returning this error: "Number of Product Field value exceeds maximum number of allowed values".  Now, changes are only committed after the validation and checking of the rules of the PI supplemental field and the following expected behavior occurs (TICKET-17634):​
  • If you add PI supplemental field values via update_acct_plan_multi_m​ greater than the configured maximum number of selections allowed, the API will return the error: "Number of Product Field value exceeds maximum number of allowed values" and the changes will not be committed.
  • If you add PI supplemental field values via update_acct_plan_multi_m less than or equal to the configured maximum number of selections allowed, the API successfully executes and the supplemental values are added.​
• The API call get_cm_details_m now returns expected data when the <client_acct_id> (rather than <acct_no>) field is provided as the reference to an existing account. (TICKET-17646)