Release 59

Usage Pooling and Accumulation Now Support Volume Discount Pricing (DEV-10540)

This feature adds support for Volume Discounts for usage when using Usage Pooling or Accumulation. This only works when Aria rates usage at invoice time via the client parameter "Configuration > Billing > Invoice Settings > Automatically Rate Un-rated Usage Records at Load Time". For Volume Discounts to work with Usage Accumulation, you must also enable Usage Pooling. If you already use Usage Pooling, you can use this new feature immediately.

Webhook Notifications Implemented for Worldpay Smart Payments (DEV-11355)

With this release of Smart Payments for the Worldpay payment gateway, Aria now supports webhook notifications for Credit Card, Tokenized Credit Card, ACH, SEPA, and Tokenized SEPA payment and refund transactions.

Details follow on feature implementation:

1. Integrated Worldpay webhook notifications for following pay methods:
   1. Credit Card (pay method = 1)
   2. Tokenized Credit Card (pay method = 13)
   3. ACH (pay method = 2)
   4. SEPA (pay method = 26)
   5. Tokenized SEPA (pay method = 37)

NSO Installments Phase 3 (DEV-11363)

Aria introduces Phase 3 of the Installments feature for non-subscription offerings (NSOs). This includes support for extended use cases and the ability to access installment features from the Aria Billing Cloud (Crescendo) user interface (API enhancements are included below).

This includes the following:

• Tracking a payment applied to an installment for each statement cycle, which helps determine the correct installment amount due for future statements.
• Allowing clients to define a “lump sum days until due” in the installment catalog definition for an aligned installment type so the due date on a lump sum payment can be any day other than the future installment due date.
• Using the installment due date to determine if an installment is past due regardless of the payment application method system wide in Aria (FDFO for First Due First, Out; FIFO for First In, First Out for oldest invoices; etc.).
• Calculating estimate dates for aligned installments by gathering the billing interval and rate schedule for all plan instances under the aligned MPI and generating all invoicing dates and taking the upcoming ones for however many installments are left.

• Create Installment Terms from the Product menu; these can be mapped to an NSO.
• View NSO installment terms when selecting a plan from the Product menu when you map an NSO to a plan.
• Allow you to define the number of days in the installment catalog definition for an aligned installment type so the due date on a lump sum payment can be any day other than the future statement due date.

• View/select installment terms from the new Installment column at the Accounts > Statements & Invoices > Orders screen.

• Enable dunning for installments as part of master plan instances (MPIs) associated with the Net Terms pay method. Now, when an MPI is in dunning because the installment amount due is not paid, once the installment amount is paid and the batch runs on the next degrade date, the MPI will come out of dunning. This eliminates the need to validate future installment amounts for dunning or out-of-dunning movements.

• Use a new event for installment assignment and trigger the event with the appropriate payload (XML, Name-Value Pair, and Email)—Account Installment Assigned under Accounts and Master Plan Instances.
  • When the installment is successfully assigned, event 760 will be triggered (against the destination account) and the payload will be generated.

• Exclude future installments due from collection when setting the existing Auto Collect on Order Invoicing parameter to True.

Support for Daily-Weekly Contracts When Contracts End Mid-Billing Period (DEV-11410)

Aria now supports Contracts on plans with Daily-Weekly rate schedules with the end action “Terminate service and billing and prorate final invoice”. When a contract ends on plans with Daily-Weekly rate schedules in the middle of a billing period, Aria correctly calculates proration.

District Tax Now Considered in Proration Calculation for Plan Cancellations (DEV-11476)

Aria now considers credits for district taxes when you cancel a plan. Previously, Aria omitted the credit when the district tax amount was rounded down to zero.

New Statement Replacement String Incorporates Credits in Tax Summary (DEV-11498)

Aria added a new Statement Template Replacement String, "insertTaxSummaryAfterCreditAmt". This replacement string displays the correct post-credit tax amount in a Tax Summary, ensuring the total reflects the true invoice amount.

New Client Parameter to Force Client Order ID Uniqueness (DEV-11518)

You can now control whether or not <client_order_id> is required to be unique via a new client parameter "Configuration > Client Settings > Miscellaneous Settings > Enforce Unique Client Order ID." This parameter can be found from either the Aria Billing Cloud UI, or the API calls create_order_m and create_order_with_plan_m.

This parameter is "True" by default and, if you attempt to create an order with a duplicate ID, Aria returns Error 3118 "The client_order_id provided already exists." The uniqueness requirement applies only to active orders (not cancelled orders).

Specify Currency Format in Email Templates By Locale (DEV-11520)

You can now customize how currency appears in your email notifications with a new "Currency Format" setting. This new parameter on the Locale Configuration screen specifies a format for how numbers are displayed as currency within Locale-specific Email Templates. When not specified, Aria uses your client-level currency format settings (Configuration > Client Settings > Miscellaneous Settings) or the system-wide default (USD).

Credit Note Replacement String InsertCreditActivityTrTypeDesc Not Displaying The Correct Translated Value (DEV-11526)

The 'insertCreditActivityTrTypeDesc' replacement string within the Credit Note Template has been updated to display the Voided Invoice description in the correct language based on the the transaction type set during the transaction. Previously, the transaction type for Void Invoice was mapped to Invoice (1) instead of Voided Invoice (-1), causing an incorrect translation.

Copy Config Copies Functional Account Groups for Payment Terms (DEV-11534)

This features enhances Copy Config functionality by correctly copying Functional Account Groups for Payment Terms.

Fraud Scoring and BACS/SEPA Direct Debit and Tokenized Direct Debit Smart Payments for Worldline (DEV-11542)

Aria delivers additional functionality through its integration with the Worldline payment gateway in this release, including the following new features:

Aria now provides fraud detection during payment authorization for credit card payments. Unlike other processors where Aria depends on the fraud score, Aria relies on the fraud message from Worldline, which can be one of the following:

• accepted – authorized
• denied - rejected

Also included in this release are BACS Direct Debit initial and recurring payments (pay method = 26), as well as transaction logging with masking of sensitive information (a BACS payment is a bank-to-bank transfer in the United Kingdom).

This introduces a new masking configuration to mask all characters of the bank-check-digit field in transaction logging.

BACS support also includes full and partial refunds for Direct Debit initial and recurring payments (pay method = 26), as well as integrated transaction logging.

Worldline’s Smart Payments integration is also enhanced with SEPA create token and payment support (pay method  = 37), including transaction logging (SEPA payments are cashless Euro transactions that can be made across the European Union and several non-E.U. countries).

At present, from Aria, we only support accepting/rejecting cards for fraud. Challenged payments should be configured to either accept/reject categories by the client with Worldline.

NSO Installments Phase 3—APIs (DEV-11363)

The following API enhancements are included as part of the NSO Installments Phase 3 release:

• get_acct_installment_m

• move_payment_m and unapply_cm_m

When running these APIs, the tax at the installment level will now be properly unapplied.

API proc_field_override for Adyen, Stripe and Worldline (DEV-11464)

For the Adyen, Stripe and Worldline payment gateways included in Aria’s Smart Payments integration, the following enhancement has been added. For the authorize_electronic_payment_m API, the “pa_3ds_termination_url” value in the input parameter now overrides the 3DS Termination URL field value for these payment processors (Configuration > Payments > Payment Gateways\Collection Groups > Processing Options tab).

Enhanced Ability to Update Billing Groups via update_acct_complete_m (DEV-11503)

This feature enhances your ability to update billing groups via the API call update_acct_complete_m. A new input field <billing_group_directive> specifies whether you are updating an existing billing group or creating a new one. Additional input fields <existing_client_billing_group_id> and <new_client_billing_group_id> allow you specify a billing group and, if desired, update a Client Billing Group ID.

The field <client_billing_group_id> is now deprecated. In addition, you can now create or update new payment methods for existing billing groups via new input field <payment_method_directive> in the <payment_methods_array>.

update_payment_method_token_m API Introduced for Worldline Smart Payments (DEV-11505)

With this release, Aria introduces the update_payment_method_token_m API for Worldine as part of Aria’s Smart Payments integration. Use this API to update all payment information along with token details, including customer first and last name as well as credit card expiration date. Additionally, the Tokenization: Store Full Credit Card client parameter must be set to True to enable this feature.

New Output Fields Return Complete Client Sequence ID in Credit Memo API Calls (DEV-11519)

Two APIs used for managing credit memos (get_cm_details_m and create_cm_m) now return an additional field, <client_appended_cm_seq_id>. This output includes a prefix or suffix that you defined for your credit memo IDs. Previously, these APIs only returned the system-generated <client_cm_seq_id>.

Enhanced Input Validations For Send Account Email API (DEV-11531)

This feature adds more informative errors when an incorrect template class or template number are specified in send_acct_email_m. The enhancement also adds a requirement for either <template_class> or <template_no>; you can also now use either <acct_no> or <client_acct_id> to specify the email recipient.

API fields ean_gln_num and ean_gln_requisition_num updated for multiple APIs (DEV-11540)

The <ean_gln_num> and <ean_gln_requisition_num> field description have been updated as follows for the below APIs:

• create_acct_billing_group_m
• create_acct_complete_m
• update_acct_complete_m
• update_acct_plan_multi_m
• update_acct_billing_group_m