Release 68

New Statement Template String: Usage Unit Type Description (DEV-11829)

This feature adds a new replacement string to statement templates that pulls the usage unit type description for invoice line items, improving statement clarity for your customers. Contact your Aria representative to update your usage-based statement templates by including this new text description.

Ability to Configure Default Country for New Accounts (DEV-11835)

This feature enhances country configuration in your Aria instance, allowing you to set a default country in the Aria UI via a new dropdown field "Default Country?" When you select "Yes," Aria assigns this country to new accounts created with no country specified (the default value is "No"). This enables Aria to send taxation information for new accounts, even if you do not assign a <country> value to an account.

If you have not set a default country, Aria defaults to "US." Aria also applies this logic to account contacts via the API and UI. Billing or statement contacts and related currency/email functions still retain their previous behavior and will continue to default to “US” or remain null where applicable.

New Generic Rebill and Credit Memo Email Templates Available (DEV-11836)

This feature introduces two new email templates to inform customers of Rebills and Credit Memos. To take advantage of either of these templates, contact Customer Support to enable and customize "Rebill Notification" (template class RB) and "Credit Memo Notification" (template class CM).

Three New Coupon-Related Events (DEV-11837)

This feature introduces three new coupon-related events in the Accounts and Master Plan Instances event class:

• Coupon Assigned (Event 765)—fires when a Coupon is added to a customer’s Master Plan Instance (MPI) or Account;
• Coupon Cancelled (Event 766)—fires when you cancel an existing Coupon on an MPI or Account; and
• Coupon Expired (Event 767)—fires when a Coupon expires for an Account.

These events can also provide you greater visibility and operational efficiency if you leverage coupons in Aria Billing Cloud. 

CCP—Enhanced Credit Memo Functionality (DEV-11862)

A new ‘calculation’ feature has been added to the New Credit Memo drawer seen at Transactions > Credits > Credit Memos subtab > New Credit Memo button > Create Credit Memo drawer. This new feature allows you to calculate amounts for price change or cancellation credit memos based on a given date range.

If a calculated value is invalid, for example a negative value for the date range selected, a message displays informing you that a credit memo cannot be created for your selected entry.

Additionally, you can now apply credit to already created credit memos from the Transactions > Credits > Credit Memos subtab. To apply credit, expand your selected existing credit memo from the list, select the ⋯ row actions, and choose the Apply Credit option.

CCP—Advanced Account Search Enhancement (DEV-12059)

The new search operator, Is One Of, has been added to the Advanced Account Search  in CCP. This new operator allows you to search a list of different criteria in one single search. For example, previously to search for a Client ID that contains any of the three following strings of numbers, you would need to compound searches by using the Equals and the OR operator as follows:

• ClientID Equals 1234 OR
• ClientID Equals 5678 OR
• ClientID Equals 9000

Now, with the new Is One Of operator, you can easily search for all these search criteria in one search using syntax as follows:

• ClientID Is One Of 1234, 5678, 9000

3DS Indicator No Longer Processed for Evertec Smart Payments (DEV-12069)

3DS indicators will now be processed directly by Evertec instead of Aria. This update improves authentication, error handling, and overall payment processing efficiency.

Client Number Added to Transaction Log for Evertec Smart Payments (DEV-12076)

The client number is now included in the Evertec Smart Payments adapter transaction log output for more efficient troubleshooting. It should be noted that the payment adapter transmits transaction information to Evertec and then receives a response containing the final transaction status.

Learn more about Evertec Smart Payments from here.

Address Validation Added for Avalara Sales and Use Smart Tax(DEV-12161)

For the new Avalara Sales and Use Smart Tax, Aria has added the following two fields to ensure accuracy in tax calculation (Configuration > Integrations > Taxation Configuration > Avalara Sales and Use Smart Tax > Configuration tab):

• Address Validation – This field indicates whether or not the address validation should be processed for the destination contacts, including the Billing Contact.
• Use Updated Avalara Address – This field indicates whether the validated address should be returned by the Avalara Address Validation API and stored in the Aria account.

Address validation is performed for the following countries:

• United States
• Canada

Note: Country eligibility is determined before the validation process. If validation fails or is unsuccessful, the original address provided is used, ensuring uninterrupted processing.

Learn more about Avalara Smart Tax from here.

Cybersource Smart Payments Integration—Phase 1 (DEV-12193)

With this release, Aria now includes the Cybersource payment gateway as part of Aria's Smart Payments integration. Cybersource is a U.S.-based financial technology company providing online payment and fraud management services for small businesses as well as medium and large-sized merchants. Cybersource (with subsidiary Authorize.net) processes payments for almost half a million businesses worldwide.

Aria's Cybersource Smart Payments integration includes the following:

• Customer-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MTI) for the Visa, Mastercard, and Discover card brands
• Fraud detection, ensuring relevant data is sent to Cybersource when fraud scoring is enabled (details below)
• Actions listed in the following table:

*-Visa (001), Mastercard (002), American Express (003) and Discover (004)

For the Payment Gateway and Collection Group configuration, the Merchant Account Details tab contains the following fields (for the REST method collection):

apitest.cybersource.com

api.cybersource.com

Additionally, The Field Options tab contains the following fields for fraud scoring:

Payment Plans Phase 3: Cancellation, Dunning Configuration, and Other Use Cases (DEV-12217)

Phase 3 of Aria Payment Plans delivers key enhancements enabling broader customization and control over payment plans, which improves both administrative and customer experiences. There is now support for different primary and backup payment methods; payment plan cancellation; early payoff options; and advanced dunning configuration. The update also introduces new and improved event notifications, empowers more flexible billing group updates, and streamlines handling of complex use cases such as overpayments and invoice associations.

Aria has added the ability to include payment plan details for the notification methods XML Master File and HTML Email (Notify Method 15) and XML Master File and Text Email (Notify Method 16).

Aria has introduced new replacement strings supporting payment plan overpayments for inclusion on customer statements.

• insertStmtAlignedPaymentPlanRemainingCharge—payment plan charge due
• insertStmtAlignedPaymentPlanRemainingFee—payment plan fee
• insertStmtBaseDebitWithAlignedRemainingInstlAmt—invoice total + aligned payment plan amount and fees without tax + payment plan charge due
• insertStmtTaxesWithAlignedRemainingInstlAmt—invoice total tax charge + aligned payment plan taxes + payment plan tax due
• insertAlignedPymntPlanSeqRemainingAmt—due amount
• insertAlignedPymntPlanSeqAmt—due amount

Aria now supports use cases in which a zero-dollar charge still invokes a taxation charge.

Aria has introduced a client-configurable parameter, Dunning Option for Payment Plan, allowing you to customize dunning behavior for failed payment plan collections. Selectable values include:

1. Restart Dunning Process—Always restarts dunning from Step 1 when a Payment Plan collection fails.
2. Align with invoice due date—Aligns the MPI’s dunning step with the invoice due date.
3. Optional—Dunning step customization. You can specify the Dunning plan step customer plans should be placed in when a collection for a payment plan fails:

   Note: Contact Aria Support to assign a value for this feature. In a future release, you will be able to define this value directly in the Aria UI.

   1. -1 (Default): Fully honors due-date-based step alignment.
   2. 0: Places MPI into the last dunning step.
   3. 1: Places MPI into (last minus 1) step.
   4. 2: Places MPI into (last minus 2) step and so on.

Aria's daily collection batch job now attempts payment plan collections against the payment method specified when the payment plan was created, while still honoring billing group payment methods for non-payment-plan charges. If no payment method has been associated with the payment plan, Aria will attempt to collect against the billing group payment method.

Aria has introduced a new event, Account Payment Plan Status Changed (Event 763), to the Accounts and Master Plan Instances Event Class.

Aria enhanced the payload for the "failed payment" event (947) in the Financial Transactions event class to include information about the charge transaction against which the attempted payment was to be applied. 

PayPal Smart Payments Phase 3 (DEV-12233)

Continuing its Smart Payments integration with the PayPal payment gateway, Aria now supports the following functionality to streamline payment processing:

• Direct Post for 3DS Authorization
• iDEAL-Direct Added as Pay Method
• Webhook Notification Support
• Real-Time Account Updater
• Apple Pay Payments Now Supported
• Transaction Logging for iDEAL-Direct and Apple Pay

Configure the 3DS Notification URL at the Payment Gateway/Collection Account Group (PG/CAG) levels to enable 3DS Authorization via the Direct Post payment handler. Please consult the Internal note below for more information.

Aria now supports iDEAL-Direct as a direct pay method. This is introduced as as pay method 49. Please consult the API ticket here for more information.

PayPal supports Return URL options for ideal payment in which you will be redirected after completing the iDEAL payment. To support this, Aria has introduced the following options (Configuration > Payments > [Payment Gateways/Collection Groups] > Processing Options tab) to configure based on need.

Aria has also added the following new UI field for PayPal webhook support (Merchant Account Details tab):

The below four events are honored for iDEAL-Direct (pm=49) payments:

• CHECKOUT.ORDER.APPROVED
• CHECKOUT.ORDER.DECLINED
• PAYMENT.CAPTURE.COMPLETED
• PAYMENT.CAPTURE.DENIED

The “PAYMENT.AUTHORIZATION.VOIDED“ event is honored for CC (pm=1) and TCC (pm=13) authorizations.

PayPal provides the Account Updater information as part of real-time API response (i.e payment response). Aria supports the following responses: card expired, token expired, card closed, and token closed. This feature is applicable for Credit Card and Tokenized Credit Card pay methods; currently, PayPal supports the Visa and Mastercard card types.

Aria now supports Apple Pay Payments as part of PayPal's Smart Payments integration. This pay method supports recurring payments and refunds for initial payments outside of Aria (via the record_alternative_payment_m API, the Aria UI, and batch processing; additional API-related details are here).

To configure Apple Pay for PayPal Smart Payments, navigate to the Apple Pay tab (Configuration > Payments > Payment Gateways/Collection Groups [PayPal Smart Payments]). Download the Certificate Signing Request (.csr) file (Step 1). After downloading the .csr file, perform the following (Step 2):

• Visit the Apple Pay portal.
• Log into your merchant account.
• Attach the CSR file.
• Get the .cer format file.

After obtaining the .cer file, upload the file from the Apple Pay tab (Step 3) to complete the pre-requisite steps for making Apple Pay payments. You should make an Apple Pay payment outside of Aria to make an encrypted payload and complete payment using the record_alternative_payment_m API (pay method 47 for Tokenized Apple Pay). More information on enabling Apple Pay payments is here.

Additionally, Aria will store shipping contact details from the encrypted payload.

Transaction logging support was implemented for the following functionalities:

• iDEAL payment + refund
• Apple Pay initial payment + refund
• Apple Pay recurring payment + refund

Both success and failure scenarios are covered for both supported pay methods. All logging types (FULL, SUMMARY, ERROR, and NONE) are supported. Sensitive data are masked with configurable masking configurations.

CIT/MIT Now Supported for JCB Cards via Chase Paymentech Smart Payments (DEV-12287)

For Chase Paymentech Smart Payments, Japan Credit Bureau (JCB) cards now support flags for Customer-Initiated Transactions (CIT) and Merchant-Initiated Transactions (MIT); these Chase-specific recurring flags will now be sent for transactions via this card type. Please note that JCB cards are processed via Discover by Chase and this applies to U.S. transactions only.

CCP—Additional Payment Methods and Billing Types Now Supported (DEV-12290)

This feature adds three new billing type options for one-time payments in CCP:

• Tokenized Credit Card
• Direct Debit
• Tokenized Direct Debit

Additional actions to the payment method flow in CCP include:

• Add collection group dropdown for adding tokenized credit card as payment method
• Add "Alternate One-Time" to Payment Method options—Tokenized Credit Card (13)
• Add "Alternate One-Time" to Payment Method options—Direct Debit
• Add "Alternate One-Time" to Payment Method options—Tokenized Direct Debit

Learn more about making payments in the Customer Care Portal from here.

Apple Pay Now Supported Through Adyen Smart Payments (DEV-12339)

Aria now supports Apple Pay Payments as part of Adyen's Smart Payments integration. This pay method supports recurring payments and refunds for initial payments outside of Aria (via the record_alternative_payment_m API, the Aria UI, and batch processing).

To configure Apple Pay for Adyen Smart Payments, navigate to the Apple Pay tab (Configuration > Payments > Payment Gateways/Collection Groups [Adyen Smart Payments]). Download the Certificate Signing Request (.csr) file (Step 1). After downloading the .csr file, perform the following (Step 2):

• Visit the Apple Pay portal.
• Log into your merchant account.
• Attach the CSR file.
• Get the .cer format file.

After obtaining the .cer file, upload the file from the Apple Pay tab (Step 3) to complete the pre-requisite steps for making Apple Pay payments. You should make an Apple Pay payment outside of Aria to make an encrypted payload and complete payment using the record_alternative_payment_m API (pay method 47 for Tokenized Apple Pay). More information on enabling Apple Pay payments is here.

Additionally, Aria will store shipping contact details from the encrypted payload. Transaction logging is also supported as well as $0 authorizations.

More information on API processing is here.

CCP—View Only Option for Billing Group Details Drawer (DEV-12345)

The Billing Group > Details drawer now has a ‘View Only’ option for users who lack Edit privileges for Billing Groups. Now, when a user who is not permitted Edit privileges selects a Billing Group Name from the Billing Group page, the Details drawer opens in view-only mode. This allows the user access to the billing group information along with its associated subscriptions, but prevents any modifications from being made.

To indicate to the user that they are in view-only mode, a yellow informational panel appears at the top of the Details drawer showing the view-only status as well as guidance on how to obtain the necessary privileges for editing.

CCP—Manage Child Accounts Pop-Out Drawer Enhancement (DEV-12346)

Child Accounts can now be updated through a streamlined drawer interface located from the Account > Child Accounts page within CCP. The Update action has been added to the Child Accounts data grid, allowing you to easily view and edit child account details directly from a pop-out drawer. At the top of the drawer, the account number and contact details are displayed. From this drawer, you can change billing responsibilities for subscriptions. Any billing responsibility updates will be instantly reflected on the main Child Accounts page after saving your changes.

Billie Updates (DEV-12349)

Added the capability to send emails to customer contacts based on a response from Billie.

• Added link to Knowledge Central within Billie CUI for improved user guidance.
• Reworked user feedback system with contextual feedback capture capabilities.

Migrated Anthropic Claude Sonnet 3.5 v2 to Anthropic Claude Sonnet v4 for improved performance.

Structured response support for "bill comparison" and "estimate next bill" features.

New API to Retrieve Open Balance Due for Invoice Line Items (DEV-11825)

This feature introduces a new API, get_acct_charges_paid_status_m, to enhance invoice processing. It returns the balance due for each invoice line item in a specified invoice, supporting the identification of eligible services and account-level charges to pay. It also returns details for other unpaid charges and offers filtering options for both pay and unpay operations. 

Ability to Configure Default Country For Newly Created Accounts (DEV-11835)

This feature enhances account creation logic to use your default country configuration when none is provided when creating an account via the create_acct_complete_m API, improving accuracy in address and tax calculations. Previously, the system defaulted the new account's country to "US" when you did not pass a value for <country>.

Plan Update APIs Enhanced With Plan Instance Queue Editing (DEV-12160)

This feature enhances the update_acct_plan_m and update_acct_plan_multi_m APIs to allow you to edit plan instance queues assigned for future activation, making the API consistent with UI capabilities. You can now update fields like Service Location, Destination Contact, Plan Instance Client Defined Identifier, and Description via the API for queued plan instances. A new parameter, <limit_update_to_object_types>, allows you to specify which objects can be updated.

Payment Plans Phase 3: Cancellation, Dunning Configuration, and Other Use Cases (DEV-12217)

Phase 3 of Aria Payment Plans delivers key enhancements enabling broader customization and control over payment plans, which improves both administrative and customer experiences. Aria enhanced the following APIs to support Payment Plan functionality: 

• record_external_payment_m
• update_acct_billing_group_m
• create_payment_plan_m
• get_invoice_history_m
• collect_from_account_m

The record_external_payment_m API now supports Payment Plan details via updated and new input fields.

Aria now supports <recalculate_installment_date> input field in the update_acct_billing_group_m API for payment plans.

Aria has deprecated the <client_payment_method_id> input field and replaced it with the following parameters:

Added a new true/false input to get_invoice_history_m called <include_payment_plan_info>. If true, the following fields will be returned with info about any payment plans associated with the invoice:

The collect_from_acct_m API now allows you to specify <client_payment_plan_id> or <payment_plan_no> to apply payments to the specified payment plan. You can also specify via the field <payoff_installment_ind> whether the full balance should be paid or only the due amount (default). 
 

PayPal Smart Payments Phase 3 (API)(DEV-12233)

The following payment processing has been enabled for PayPal Smart Payments:

Once the invoice and statement are generated for the account, you can initiate the iDEAL payment using the record_alternative_payment_m API with the following inputs:

Please follow these steps:

1. Once the record_alternative_payment_m API is executed with the above inputs, Aria will return a <payment_redirect_issuer_url> in the response.
2. You should invoke this <payment_redirect_issuer_url> value in the browser to complete the iDEAL payment (where you are redirected to the issuer/bank page in which they will pass bank details and complete the payment). 
3. Once the iDEAL payment is completed, the status of your payment will be updated in Aria via Webhook notification.

While executing the record_alternative_payment_m API, Aria will decrypt the payload, and the decrypted values will be used for completing the intial Apple Pay payment in Adyen, including the following fields:

Specify Order of Discount Rules Returned by get_discount_bundle_details_m API (DEV-12239)

This feature enhances the get_discount_bundle_details_m API to return the Discount Rules assigned to a Bundle in the order they were assigned (chronologically) when the <primacy> parameter is set to "true."

Previously, although Discount Rules were ordered correctly within the UI and during Bundle creation, the API would return these rules in rule number order instead of the order defined during creation.

APIs Enhanced to Return Pending Balances (DEV-12259)

Aria has enhanced the APIs get_acct_balance_m and get_acct_details_all_m to provide a detailed breakdown of pending balances, including overdue amounts, helping customers better understand account balances with dynamic payment schedules. Setting the new input parameter <include_acct_past_due_balance> to 1 causes these APIs return the past-due outstanding balance in the field <acct_past_due_balance>.

Apple Pay Now Supported Through Adyen Smart Payments (API)(DEV-12339)

While executing the record_alternative_payment_m API, Aria will decrypt the payload, and the decrypted values will be used for completing the initial Apple Pay payment in Adyen, including the following fields: