Skip to main content
Aria Knowledge Central

Release 72

Note: This is a draft version of the release notes for Aria Billing Cloud—Version 72, 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

 30-June-2026

System Requirements

Supported Browsers

Aria supports the latest stable versions of the following Web browsers: 

  • Chrome 63
  • Firefox 52
  • Microsoft Edge
  • Safari 11 on MacOS 

Screen Resolution

1024 x 768 or higher

Release 72 Contents


Application Features 


Tokenized BECS Added as Payment Method for Stripe Smart Payments (DEV-12300)

Aria has added the Tokenized BECS (Australian Direct Debit) payment method as part of its Stripe Smart Payments integration, including refund support. Tokenized BECS is also now supported as a valid primary and backup payment method when creating or updating a payment plan.

 The Tokenized BECS pay method can be selected from the following locations in the Aria Billing Cloud UI:

  • Accounts > [search for Account] > Payments & Credits > Payments > Apply a Payment
  • Accounts > [search for Account] > Plans > Billing Groups > New (Create New Billing Group)
  • Accounts > [search for Account] > Plans > Billing Groups > Billing Group (Edit Existing Billing Group)
  • Accounts > [search for Account] > Plans > Plan > Add New Plan (Add New Master Plan Instance to Account)
  • Accounts > [search for Account] > Account Overview > Payment Methods > New (Create New Payment Method - Tokenized BECS)
  • Accounts > [search for Account] > Account Overview > Payment Methods > Edit button (Edit the existing Tokenized BECS payment method)
  • Accounts > Create New Account

This pay method is used with the following fields:

Condition Fields
via Bank Account Bank Account Number (6-9 characters—required)
Bank Branch Code (6 characters—required)
Account Holder Name
or
via Existing Token Agreement ID (required)

If this information is not provided, the following error message appears:

"Missing required parameters: bank_acct_num and bank_branch_cd or bill_agreement_id"

An API-related enhancement for this feature is also included on this page.


Custom Filename for Statement PDF Email Attachments (DEV-12435)

You can now configure a custom filename for the statement PDF that Aria attaches to customers' emailed statement notifications. Previously, Aria assigned a sequential number as the filename, which could not be mapped back to a customer account, statement, or transaction. The custom filename supports downstream invoice indexing, CSR tooling, and unique invoice tracking.

Note: See the API writeup for this feature.

Client Parameter

To support this feature, Aria has introduced a new client parameter, Custom PDF Statement Filename (Configuration > Notifications > Notification Settings > Custom PDF Statement Filename). To configure the filename, you can choose from the following tokens to construct your file name:

  • Account Client ID
  • Account Number
  • Aria Statement Number
  • Aria Invoice Number
  • Invoice Date
  • Statement Sequence Number

Payment Plans Phase 7: Financial Fees and Other Use Cases (DEV-12467)

Payment Plans Phase 7 introduces financial fee support, enhanced payment method visibility on payment plan APIs, and independent payment plan information on anniversary statements. This release also resolves several calculation and collection issues.

Note: View the API writeup for this ticket.

Financial Fee for Payment Plans

You can now configure a financial fee, a type of order-based service, that Aria charges when a customer's payment plan is created. The fee is calculated on the installment balance (excluding any lump sum) and allocated proportionally across payment plan sequences. Aria automatically generates an invoice for the fee.

Three fee types are supported:

  • P (Percentage-based): applied as a percentage of the installment balance.
  • F (Flat): a fixed amount per plan.
  • A (Amortized interest): distributed across sequences so that earlier payments carry a higher interest component and later payments carry less, as the principal decreases.

Note: Although Aria includes a generic 'Financial Fee' global service, you can assign any order-based service as the payment plan fee.

New Fee-related Statement Replacement Strings

New statement replacement strings are available for fee amounts on aligned payment plans, including insertStmtAlignedPaymentPlanFee (total fee inclusive of tax), insertStmtAlignedPaymentPlanRemainingFee, and per-sequence strings for fee due amount, total due (open), and fee due excluding lump sum.

Independent Payment Plan Information on Anniversary Statements

Independent payment plan statement strings are now available for inclusion in customers' anniversary statement templates. When an independent payment plan is active, the relevant plan details appear once on the anniversary statement, giving customers a clear view of their payment plan alongside their standard billing summary. 

Fixes

  • Next payment due amount calculation: When a lump sum and the first sequence share the same due date, Aria now correctly groups amounts by due date for the “next payment of $X” display. This applies to both independent and aligned payment plans.

Enhanced Proration Support for Universal Contracts (DEV-12535)

When you modify the end date of a type 7 (universal) contract before the first regular invoice is generated, or while a pending invoice exists, Aria Billing Cloud now correctly suppresses invoice generation so that approving the contract change does not result in a double charge.



PayPal Wallet/PayPal Credit Card Authorization (DEV-12565)

For the next phase of Aria's PayPal Smart Payments integration, PayPal Wallet authorization functionality is now included for credit card registration and payment, including authorization/capture/refund and authorization/reversal actions. During payment method registration, a $0 token is generated with 3DS for CyberSource, which performs an authorization for the full amount. If the authorization succeeds, provisioning proceeds against the user's account with a license for subscription for the full amount. If the authorization fails, an error is generated so the user can correct the payment method and retry the payment attempt.


Nets Netaxept Smart Payments Integration - Phase 4 (DEV-12576)

The following features have been added to Aria's Smart Payments integration with the Nets Netaxept payment gateway:

SCA Exemption

The Low Value Payment Strong Customer Authentication (SCA) exemption has been added for Tokenized Credit Card payments (pay method 13) for all supported card types (Visa, Mastercard, American Express, Dankort and Diners Club). You can skip the 3DS pop-up message when the SCA Exemption flag is enabled in the Billing Cloud UI (Configuration > Payments > Payment Gateways/Collection Groups).

Note: The amount of the SCA Exemption is determined outside of Aria.

3DS and SCA Exemption Error Handling

During 3DS authorization, Aria internally invokes Nets’ Terminal API, which returns HTML content with an HTTP status code of 200.

In frictionless or SCA exemption scenarios, Nets returns an authentication-skipped HTML response (containing a redirect link with responsecode=OK) along with an HTTP status code of 302, which is still considered a successful outcome. Aria checks for the returned response in such cases and validates it using the returned Transaction ID and the response code, and return the successful/ failure responses accordingly.

Direct Post Support

3DS Authorization and SCA Exemption are supported by Direct Post.

<cc_id> Added to <query_token> NETS API response

The query_token response has been enhanced to include the card type (cc_id) using the Issuer field value from the NETS API response. As with the SCA Exemption, all card types are supported.

Enhanced Transaction Logging

For Tokenized Credit Card payments, transaction logging has been added for the following actions:

  • Create_token
  • Query_token
  • Authorizations
  • Reversals
  • Capture
  • Payment
  • Refund
  • 3DS

This applies to initial and recurring transactions, as well as 3DS, non-3DS, success and failure scenarios. All card types listed for the SCA Exemption and Query Token enhancements are applicable for logging also, with logs captured based on the Full, Summary, Error, and None logging types.

An API-related enhancement also appears on this page.


Account Plan Instance Modified Event (718/719) Not Fired On Rate Change From Custom To Default Rate (DEV-12593)

New enhancements have been added for the Account and Plan Instance provisioning events:

  • The "Account Master Plan Instance Modified" (event 718) and "Account Supplemental Plan Instance Modified" (event 719) events now fire correctly when a custom rate is removed from a plan instance and the plan returns to its default rate schedule. Previously, these events fired when changing from a default rate to a custom rate, or when editing a custom rate, but not when removing a custom rate. This fix applies to all removal paths, including direct API removal and removal during plan updates.

  • When a custom rate is moved to a different rate schedule, the system now generates two events instead of one—one event for the custom rate removal and one for the rate schedule change. (Note: Both events carry the same payload except for the transaction ID.)

  • Two new fields have been added to the "Accounts and Master Plan Instances" provisioning payload for users on provisioning version 4.1 or higher: Rate Schedule Number (the rate schedule currently assigned to the plan instance) and Custom Rate Indicator (returns 1 if the plan instance has custom rates applied, or 0 if it does not). These fields appear in all three payload formats: XML, name-value pair, and email.


Tokenized ACH/Soft Descriptor Support Added for Run Payments (Smart Payments)(DEV-12598)

Aria now provides Token Creation functionality for ACH accounts/payments (all ACH payment indicators are flagged as Recurring at this time).

Note: Query token functionality for ACH currently does not exist; therefore, Aria provides the last 4 digits of the account number for the token.

Soft descriptors are also supported from the Collection Group/Payment Gateway hierarchy (Configuration > Payments > Payment Gateways/Collection Groups). If no soft descriptor is available, the <payment_description> field will not be populated in the Run Payments API.


CCP Additional Fixes And Improvements (DEV-12600)

The following improvements have been added for CCP:

  • The E-Mandate Signature field is now supported for Direct Debit and Tokenized Direct Debit payment methods. You can enter an E-Mandate Signature when creating a new payment method from Account > Overview > Payment Methods. When editing an existing payment method, the field appears as read-only and displays the saved value. The field is optional, so existing payment methods are not affected.

  • The E-Mandate Signature field and the Mandate Auth Date field are now available on the Make Payment / One-Time Payment screen when creating a new Direct Debit or Tokenized Direct Debit payment method.

  • Three new optional columns have been added to the Statements table in both Account > Overview and the Subscription > Details drawers: Sequential Statement ID, Second Sequential Statement ID, and Invoice Number. These columns are hidden by default. You can enable them by clicking the column settings icon on the table. The Invoice Number column displays all invoice numbers associated with a statement, separated by commas.



Subscription Details Plan Instance Updates (DEV-12669)

You now have the ability to update the dunning state of a subscription directly from CCP.

You can now click on the dunning state field in the Subscription Details drawer to open the Dunning State drawer. From there, you can update or select the dunning state as well as the next dunning degrade date. You can choose between dunning states of ‘None’, ‘In Progress’, or ‘Completed’. The top of the drawer displays key information about the subscription, including the Client ID, description, full balance, and balance due.

To access this feature, navigate to Subscriptions > Details > select a subscription > click on the Dunning State field in the light blue section of the drawer.

Note: A history of dunning state actions will be available at the bottom of this drawer in a future release.


Billie and Billie Connect Release 72 Updates (DEV-12673)

Aria has enhanced Billie and Billie Connect with the following:

  • Subscription suspension inquiry: You can ask Billie when a named subscription will enter a suspended state due to dunning. Billie returns either 1) the next degrade date if the subscription is on step x of n, or 2) the projected suspension date when a subscription is on step n of n, in response to the utterance “When will Subscription <name> be suspended?”
  • Service Calculated Drawer comment: You can add or edit a comment in the Service Calculated Drawer before confirming a calculated service credit.
  • Slash Menu starred items: Starred items (favorites) are now visually distinct in the Slash Menu List view, making it easier to identify your pinned commands.
  • Client parameter validation: Billie Connect validates required client parameters at the point of use before passing them to downstream calls. This prevents errors caused by missing values, including reason code defaults.

Application Fixes 

  • Accounts now properly sync to CCP when an account is created with Supplemental Fields containing values in a date format (such as "16.04.2026"). Previously, the system was incorrectly interpreting those string field values as dates, which prevented the account from syncing. The sync now ensures that supplemental fields defined as string fields are no longer misidentified as date fields during account sync. (TICKET-19990)

API Features 

Tokenized BECS Added as Payment Method for Stripe Smart Payments (API)(DEV-12300)

Aria has added the Tokenized BECS (Australian Direct Debit) payment method (pay method – 53) as part of its Stripe Smart Payments integration. This pay method is supported by the following Aria APIs:

This pay method is used with the following fields:

Condition FIelds
via Bank Account <bank_acct_num> (6-9 characters—required)
<bank_branch_cd> (6 characters—required)
or
via Existing Token <bill_agreement_id> (required)

If this information is not included, the following error message appears:

Code Description
1010 Missing required parameters: <bank_acct_num> and <bank_branch_cd> or <bill_agreement_id>

Application-related enhancements also appear on this page.


$0 Tax Enhancements to get_reversible_invs_by_payment_m API (DEV-12352)

The following enhancements have been added to the get_reversible_invs_by_payment_m API:

  • The API no longer returns separate $0 tax service lines for tax-inclusive charge lines. The tax for these lines remains embedded in the charge amount as expected.
  • $0 charge lines that carry non-zero associated tax (for example, fixed-tax use cases) are now correctly included as reversible items.
  • For eligible $0 charge lines, the API now correctly populates the following: 
    • <charge_event_no>
    • <pmt_applied_amount>
    • <reversible_amount>
    Previously, these fields would be returned as null for such charge lines.
  • Mixed invoices (with both tax-inclusive and tax-exclusive lines) now:
    • Return tax lines only for tax-exclusive charges
    • Do not include tax lines for tax-inclusive charges 

Also, when passing $0 against a non-zero invoice charge, the line (and any related tax) is now skipped rather than generating zero-dollar reversal details. This prevents unnecessary reversal rows and ensures that only charges actually selected for reversal are processed. 

In addition, refund-reversals on invoices with $0 charge lines plus tax, paid across multiple payments, now correctly credit the full flat tax. For $0 charge lines, the tax credit on a refund-reversal is now capped to the reversible amount allocated to that specific amount (cap applies only to refund-reversals).

For invoice-based credit memos, the credit amount input field is now added for $0 invoice lines without tax.

This also applies to the following APIs (in addition to refund-reversals in the Aria UI via Accounts > [search for an account] > Payments & Credits > Refunds):

Notes:

  • You must pass the $0 charge line in the Refunds – Credit Memo UI as well as via an API to issue a tax credit for the taxes assessed as a $0 line item.
  • Applicable Aria APIs now only accept the charge line that has positive tax lines (existing error code 2016 will otherwise be returned). This is a change in behavior.

The following error code is now removed when a $0 line item amount is passed in the create_cm_m API:

Code Description
3069 Invalid amount

Custom PDF Filename Support Added to get_acct_statement_all (DEV-12435)

You can now configure a custom filename for the statement PDF that Aria attaches to customers' emailed statement notifications. Previously, Aria assigned a sequential number as the filename, which could not be mapped back to a customer account, statement, or transaction. The custom filename supports downstream invoice indexing, CSR tooling, and unique invoice tracking.

Aria has enhanced the get_acct_statement_all_m API method to support this feature with a new output field, <custom_filename>, which returns the custom PDF statement filename associated with each statement when one is configured. The field returns null when no custom filename applies.

New Output Field Type Description
<custom_filename> string Custom PDF statement filename used (or to be used) when emailing the statement PDF.

Note: You must set the new client parameter, Custom PDF Statement Filename, to enable this feature. See the application writeup for details about this client parameter.


Payment Plans Phase 7: Financial Fees and Other Use Cases (DEV-12467)

Payment Plans Phase 7 introduces financial fee support, enhanced payment method visibility on payment plan APIs, and independent payment plan information on anniversary statements. This release also resolves several calculation and collection issues. Aria improved the following APIs:

Note: View the application writeup for this ticket.

create_inventory_item_m

The following inputs are now available for creating fee inventory items:

Field Type Description
<item_type> int Set to 3 for Fee.
<fee_application_type> int Defaults to 1 (applied to payment plan).
<fee_type> string Required when <item_type> is 3. Values: P (percentage), F (flat), A (amortized interest).
<fee_structure_list> array List of fee structures, one per currency. Each entry includes <currency_cd> and the fee amount or rate.

create_payment_plan_m

A new input, <client_sku>, references the fee inventory item when the item is a fee type.

New/Updated Field Name Input or Output Field Description
<client_sku> (New) Input The client-defined SKU for the fee-type inventory item. Applicable only when the inventory item is a fee type (<item_type> = 3). Mutually exclusive with <item_no>.

The following outputs are now returned:

Output Description
<fee_balance> Payment plan fee balance inclusive of tax.
<total_balance> Sum of principal balance and fee balance.
<fee_amount> (in <payment_plan_details>) Fee amount allocated to each sequence.
<total_due_amount> (in <payment_plan_details>) Sum of due amount and fee amount per sequence.

get_payment_plan_details_m

Release 72 adds fee-aware fields to the payment plan schedule and a new payment method identifier to the top-level response. Several existing sequence fields have updated descriptions to clarify that their values include fees.

The description of get_payment_plan_details_m is now: Returns the full details and schedule for a specific payment plan on an account. Payment plans allow customers to pay outstanding balances in installments over multiple billing periods. This API returns the plan’s configuration (type, total amount, number of installments, and frequency), current status, and the individual installment schedule showing each payment’s amount, due date, and payment status (paid, pending, or missed). Specify the payment plan by the <payment_plan_no> or <client_payment_plan_id> field. To list all payment plans on an account first, use get_payment_plan_list_m.

New/Updated Field Name Input or Output Field Description
payment_plan_schedule array
<seq_due_amount> (Updated) Output The principal amount due for a payment plan sequence.
<seq_fee_due> (New) Output The fee amount due for a payment plan sequence.
<seq_total_due> (New) Output The total amount due for a payment plan sequence (principal and fee).
<seq_remaining_due> (New) Output The remaining principal amount due for a payment plan sequence.
<seq_fee_remaining_due> (New) Output The remaining fee amount due for a payment plan sequence.
<seq_paid_amount> (Updated) Output The total amount paid for a payment plan sequence, including fees.
<seq_remaining_balance> (Updated) Output The remaining balance for a payment plan sequence, including fees.
<payment_method_no> (New) Output The Aria-assigned payment method number associated with the payment plan. If null, the payment method or payment term associated with the billing group is used. This field removes the ambiguity that occurred when <client_payment_method_id> returned null despite a payment method being explicitly set at the plan level.

get_payment_plan_list_m

Release 72 adds fee-aware output fields and a new payment method identifier to the get_payment_plan_list_m response. The existing <remaining_balance> field has also been updated to reflect the total remaining balance inclusive of fees.

The description of get_payment_plan_list_m is now: Returns a list of all payment plans configured on an account. Payment plans allow customers to spread an outstanding balance across multiple billing periods rather than paying the full amount at once. Each payment plan has a schedule defining the payment amounts, frequency, and duration. By default, only active payment plans are returned; set <include_all_statuses> to true to also include completed, cancelled, or suspended plans. Use get_payment_plan_details_m to retrieve the full details and payment schedule for a specific plan.

New/Updated Field Name Input or Output Field Description
payment_plan_list array
<payment_method_no> (New) Output The Aria-assigned payment method number associated with the payment plan. If null, the payment method or payment term associated with the billing group is used.
<fee_balance> (New) Output The payment plan fee balance, inclusive of tax, to be paid.
<remaining_balance> (Updated) Output The remaining balance, including fees, to be paid by the payment plan at the time of the API call.

get_inventory_items_m

Release 72 adds a new allowable value to the <item_type> output field to support fee-type inventory items.

Returns a list of inventory items created for the client.

New/Updated Field Name Input or Output Field Description
<item_type> (Updated) Output

The item type for the inventory item.

Allowable Values

Values Description
0 Inventory Item
1 Months To Stack (Deprecated)
2 Resource Item
3 Fee

get_inventory_item_details_m

Release 72 adds a new allowable value to <item_type> and introduces three new output fields that return fee configuration details for fee-type inventory items.

New/Updated Field Name Input or Output Field Description
<item_type> (Updated) Output The item type for the inventory item.

Allowable Values

Value Description
0 Inventory Item
1 Months To Stack (Deprecated)
2 Resource Item
3 Fee
<fee_application_type> (New) Output Specifies how the fee is applied. If <item_type> = 3, defaults to 1. Allowable value: 1 —Applied to payment plan. Null for non-fee items.
<fee_type> (New) Output

The type of fee calculation. Required when <item_type> = 3. 

Allowable Values

Value Description
P Percentage-based
F Flat
A Amortized (declining balance) interest

Null for non-fee items.

fee_structure_list array —List of fee structure components. Null or empty for non-fee items.
<currency_cd> (New) Output The ISO currency code for the fee.
<tax_inclusive_ind> (New) Output Indicates whether the fee is inclusive of taxes. Allowable values: 1 —Tax inclusive, 0 —Tax exclusive.
<fee_amount> (New) Output The fee amount. Works in conjunction with <fee_type>.

Fixes

  • Double collection during billing batch: Aria no longer attempts duplicate payment collection on accounts where COLLECTOR_REVIEWED_IND (a database field referenced during a batch process) via create_acct_complete_m has already triggered a payment attempt, when those accounts have installment dues with dunning completion master plan suites. Previously, a failed collection attempt during account creation would not set the indicator, causing the billing batch to incorrectly attempt collection a second time. Aria now handles failed collections resulting from create_acct_complete_m calls.
  • <recurring_amount> rounding: The update_payment_plan_m API now correctly rounds <recurring_amount> to two decimal places in the response, ensuring a more accurate accounting of payment plans.

Nets Netaxept Smart Payments Integration - Phase 4 (API)(DEV-12576)

In addition to setting the SCA Exemption type via the Payment Gateway and Collection Group configurations for Nets Netaxept Smart Payments, you can also set the <sca_exemption_type> value via the via the authorize_electronic_payment_m API at the <proc_field_override> array. Select from one of the following values:

Value Description
0 No exemption - This value will prefer to perform 3ds authorization steps (3ds challenge) for transaction.
1 Low Value Payment - This value will prefer to skip the 3ds authorization steps for transaction and this forms the SCA exempted transaction.
-1 Use client configuration Collection Group – Payment Gateway settings for determining the exemption type.

Application-related enhancements also appear on this page.


Product Field Updates Through "update_acct_plan_m" API Not Allow Duplicate Settings Values Differing Only By Case (DEV-12622)

Duplicate value validation for plan instance product fields have been added. Requests attempting to add a duplicate value to a plan instance product field of type Text, Textarea, Radio, Checkbox, or Select are now rejected. Duplicate detection is case and whitespace insensitive, meaning values like "One," "ONE," and " one " are all treated as the same value. If a duplicate is detected, either within the same request or against an existing saved value, the API rejects the request and returns error code 5065.

This validation applies when adding values using the assign_acct_plan_m, update_acct_plan_m, and update_acct_plan_multi_m APIs.



API Fixes 

None


WSDL File Locations

Stage Current

US https://secure.current.stage.ariasystems.net/api/Advanced/wsdl/71/complete_m-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/Advanced/wsdl/71/complete_m-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/Advanced/wsdl/72/complete_m-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/Advanced/wsdl/72/complete_m-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/Advanced/wsdl/72/complete_m-doc_literal_wrapped.wsdl

Production

US https://secure.ariasystems.net/api/Advanced/wsdl/71/complete_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/Advanced/wsdl/71/complete_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/Advanced/wsdl/71/complete_m-doc_literal_wrapped.wsdl

Object Query WSDL Files

Stage Current

US https://secure.current.stage.ariasystems.net/api/AriaQuery/wsdl/71/integration_services_m-doc_literal_wrapped.wsdl
EUR None
AUS https://secure.current.stage.aus.ariasystems.net/api/AriaQuery/wsdl/71/integration_services_m-doc_literal_wrapped.wsdl

Stage Future

US https://secure.future.stage.ariasystems.net/api/AriaQuery/wsdl/72/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.future.stage.cph.ariasystems.net/api/AriaQuery/wsdl/72/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.future.stage.aus.ariasystems.net/api/AriaQuery/wsdl/72/integration_services_m-doc_literal_wrapped.wsdl

Production

US https://secure.ariasystems.net/api/AriaQuery/wsdl/71/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/AriaQuery/wsdl/71/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/AriaQuery/wsdl/71/integration_services_m-doc_literal_wrapped.wsdl
TOP
  • Was this article helpful?