Release 70

Sovos Added To Aria Smart Tax (DEV-12166)

With this release, Aria adds the Sovos global tax compliance engine as a Smart Tax integration. This includes support for geo codes for tax calculation of invoice items, which will be used instead of the Ship To, Bill To, Ship From, and Bill From addresses with the Sovos tax engine. The geo code generated will have no expiry period. Voided taxes are likewise supported through Sovos APIs along with transaction logging for calculate, post, refund (full and partial) and void tax actions.

Phase 5 of Aria Payment Plans (DEV-12219)

Phase 5 of Aria Payment Plans introduces new notification capabilities, including enhanced Payment Plan Due email template support for Notify Method 13 (XML Master Filed); a new email template class for Payment Plan Creation; a new daily batch job that creates estimates of installment and payment plan due dates data to improve payment-plan- and installment-term-related reporting (DEV-12466); and some general fixes.

Aria enhances XML Master File (Notify Method 13) support for PPD email template processing, adding to the existing support for Notify Methods 15 (XML Master File and HTML Email) and 16 (XML Master File and Text Email). Contact Aria Support to enable this feature.

Once a PPD email template is configured and selected, Aria supports account-level overrides via two paths: through the API (set_acct_notify_override_m), via the UI (Account Overview > Notification Method), or via a Notification Template Group (configurable at the Account, Billing Group, Functional Account Group, Plan, and Client levels).

Aria introduces a new email template class, PPC (Payment Plan Creation), which sends a confirmation email to customers upon successful creation of a payment plan. 

The main body of the PPC template supports the following fields: insertPaymentPlanNo, insertPaymentPlanName, insertPaymentPlanType, insertPPCClientPaymentPlanId, insertPaymentPlanAmount, insertNextPaymentPlanDueDate, insertNextPaymentPlanDueAmount, insertLumpSumCollected, and insertInitialAmountCollected.

You can place any charges that were unpaid at the time of payment plan or installment cancellation onto a new payment plan when no remaining plan- or installment-level balance exists. This situation can arise when you unapply a payment after the Payment Plan or Installment has already transitioned to a non-active state.

• Aria now displays the correct due amounts on statements for Aligned Payment Plans when a lump sum and the first scheduled sequence fall due on the same aligned statement. |
• Aria can now redefine the unpaid balance on payment plan (even the notified sequences) with a new payment plan. When it does, the old payment plan will have a 'discontinued' status, and the new payment plan will have an 'active' status with the remaining unpaid balance. 

CCP Cancel Subscription (DEV-12244)

You can now cancel a subscription in CCP directly from the Subscription > Details page. Select the Cancel action for a subscription to open a cancellation drawer. This drawer displays key details of the subscription being cancelled. After reviewing and confirming the information, proceed with the Cancel Subscription action to complete the cancellation.

Additionally, you can now preview the invoice that will be generated as part of the cancellation. The invoice preview displays all applicable charges and credits in an itemized view allowing you to review the expected financial impact before finalizing a subscription cancellation.

Support Address Change Scenario For Refunds (DEV-12265)

The invoice Address and Date from the original invoice is now used during proration invoicing and rebill invoicing to calculate taxes when the client parameter Use Original Invoice Address and Date to Calculate Tax for Invoice Modification is set to TRUE. You can edit this parameter by navigating to Configuration > Billing > Taxation Settings in Aria Billing.

Edit Queued Subscriptions (DEV-12295)

The Subscriptions > All Service Rates section in CCP now supports rate management for queued subscriptions and add-ons. You can edit tier values for rate schedules already assigned to queued plans and add or edit custom rates. 

$0 Line Items To Tax Engine for Invoice-Based Credit Memos/Refunds (DEV-12352)

Aria now provides the ability to reverse $0 charge lines on an invoice and reverse the respective tax if it exists. Also, you can now issue an invoice-based credit memo for the $0 charge lines in an invoice and calculate the respective tax on the credit memo, allowing the tax to be reversed if it exists (Accounts > [search for an account] > Account Overview > Payments & Credits > Refunds).

API-related enhancements for this ticket are also noted on this page.

Nets Netaxept Smart Payments Phase 2 (DEV-12358)

Aria adds to the Nets Netaxept Smart Payments integration with this release with the following features:

• The Low Value Payment SCA Exemption has been added for the Credit Card pay method (PM-1). The exemption amount for Nets Netaxept is <=30 EUR.
• Transaction Logging has been added for the following (also for PM-1):
  • Authorization, payment, capture, reversal, refund (partial and full), 3DS Authorization and auto reversal actions.
  • Capture of log success and failure scenarios.
  • Capture of logs for all supported card types.
  • Masking of sensitive data in logs.
  • Capture of logs by type (Full, Summary, Error, and None) 
• Direct Post is also supported for Nets Netaxept Smart Payments (PM-1). Low-Value Payment SCA exemption has also been implemented (PM-1).
• Additionally, 3DS Authorization has been added for Nets Netaxept. Information on this feature is included in the API section of the release notes.

Back-End Processor and Level 2/Level 3 Support for CyberSource Smart Payments (DEV-12393)

For CyberSource Smart Payments, Aria has added the field Send Level 2/Level 3 Data in the payment request at the Processing Options tab for the AMEX and GPN back-end processors (No is the default).

The AMEX and GPN processors support the following card types:

This enables Level 2 and Level 3 data to be sent with VISA, Mastercard, and Discover payments (American Express supports Level 2 data only; Mastercard does not support $0 payments). Level 2 and Level 3 data can be enabled at the Payment Gateway and Collection Group levels. As a reminder, by providing Level 2 and Level 3 data, merchants qualify for lower interchange fees, which merchants pay to card-issuing banks for each card purchase.

Additionally, the Bank Account Type input field for the ACH Payment method supported by CyberSource has been added to following screens:

• Payments (Account > [search for an account] > Account Overview > Payments & Credits > Payments)
• Payment Methods (Configuration > Payments > Payment Methods)
• Account Creation (Account > Create New Account)
• Billing Groups (primary and secondary)(Account > [select an account] > Plans > Billing Groups)

Level3 Data Enhancement Added for Chase Paymentech (DEV-12405)

Level 3 data is now supported by Chase Paymentech for the MasterCard and Discover card types. This applies to the following pay records:

This enhancement applies to both legacy and Smart Payments integrations for Chase Paymentech.

Enhanced Proration Support for "Number of Uses" Coupons (DEV-12406)

This feature extends the existing “Use proration and remainder factors” option with coupons so you can use it with the “Number of Uses” duration type for fixed-amount discounts. When you configure coupons this way, Aria now prorates the associated discounts on invoices inline, handling both proration and remainder factors across first and last uses.

PayPal Wallet Pay Method Includes Transaction Logging (DEV-12429)

Transaction logging has been added for the new PayPal Wallet payments (pay method 52). This covers workflows for initializing and completing token creation. Basic actions captured in logging as part of token creation are payment, capture, reversal, and full/partial refunds. Logging types supported as part of this feature are Full, Summary, Error, and None.

CCP View Credit Memo (DEV-12450)

You can now unapply credit memo amounts directly from the credit memo details view in CCP. This feature can be found by navigating to Transactions > Credits > Credit Memos > Expand Credit Memo Record > Unapply Credit.

Additionally, a void action has been introduced to CCP in the Credit Memos action menu allowing you to void an entire credit memo from the credit memo page. Once the void transaction is confirmed, the credit memo is marked as void, and the Void option is disabled for already-voided records.

CCP Subscription Details Plan Instance (DEV-12452)

The Subscriptions > Queued Changes > Execute drawer in CCP now allows you to create a new destination contact directly from within the drawer and use that newly created contact when executing queued changes. 

CCP Create Subscription (DEV-12453)

The Subscription creation flow in CCP has been updated to handle parent-pay billing responsibility options, Add-On management, selection of Inventory Items (defined in the legacy product catalog), Bill Lag Days, extended product field management (to support both subscription‑level and add‑on‑level product fields), and previews of the invoice for the subscription that will be created.

CCP New Service Credit (DEV-12456)

The Cash Credits, Service Credits, and Refunds creation in CCP have been updated to honor currency limits. This ensures that credit types and refunds created with a configured currency comply with that currency's thresholds. 

Reporting Data for Aligned Payment Plan and Installment Future Dates Calculation (DEV-12466)

This feature introduces a backend process to calculate and store estimated future notify and due dates for aligned payment plans and installments in a dedicated reporting table. You can now report on this data via a request to Aria.

CCP Payment Method Not Showing Mandate Signature (DEV-12510)

The Mandate Signature Date can now be saved when creating Direct Debit and Tokenized Direct Debit payment methods in CCP. Previously, the Mandate Signature Date could not be saved when creating Direct Debit and Tokenized Direct Debit payment methods in CCP. This has been updated so that users can now save the Mandate Signature Date during payment method creation, and see the previously saved value when reopening the payment method drawer in edit mode.

Support For Refund With Open Paid Line Items Preview On Issue_refund_to_acct_m API (DEV-12182)

The <open_paid_line_item_list> output array has been added to the issue_refund_to_acct_m API. This output, which is already available in get_refund_detail_m, is now expanded and populated in issue_refund_to_acct_m for both <do_write> = true and <do_write> = false scenarios.

Phase 5 of Aria Payment Plans (DEV-12219)

Phase 5 of Aria Payment Plans expands API outputs to better support parent-pay and lump sum scenarios by returning additional child account, invoice, and status change details and fixes various calculations and API returns.

Aria has added new input and output fields to the API get_payment_plan_list_m: 

Aria has added new inputs to update_payment_plan_m supporting the newly added allowable value for <update_scope> = 2 (create new schedule).

$0 Line Items To Tax Engine for Invoice-Based Credit Memos/Refunds (API)(DEV-12352)

Aria now provides the ability to reverse $0 charge lines on an invoice and reverse the respective tax if it exists. This feature applies to the following APIs:

• create_cm_m
• issue_refund_to_acct_m

The following error code has been removed for the create_cm_m API:

Nets Netaxept Smart Payments Phase 2 (API)(DEV-12358)

3DS Authorization has been added as a feature enhancement for Aria's Nets Netaxept Smart Payments integration for the Credit Card pay method (PM-1).

Pre-requisite:

3DS Termination URL—Client has to specify the Merchant website URL in the Payment Gateway/ Collection group UI screen (which will get invoked when the shopper challenge is complete).

The Nets Netaxept 3DS authentication is a three-step process, as follows:

Step 1: Execute the authorize_electronic_payment_m or update_payment_method_m api with credit card details, billing address details and <attempt_3d_secure> as 'true' to perform client authentication, then the api will return the <proc_payment_id> (as the outer level output field) and <pa_3ds_form_content> (form value in the <proc_3dsecure_data/proc_3dsecure_auth_data array>) in the response.

Step 2: Use the Form value and save it as an html page and execute it. A challenge/redirect window pops up based on the 3ds transaction details; you then must submit the challenge/redirect form to end Step 2.

Step 3: Execute authorize_3dsecure_m with the <proc_pymnt_id> (from step 1), perform the authorization and verify the API result to complete the 3ds authentication-based authorization.

Enhanced Proration Support for "Number of Uses" Coupons (DEV-12406)

This feature extends the existing “Use proration and remainder factors” option with coupons so you can use it with the “Number of Uses” duration type for fixed-amount discounts. When you configure coupons this way, Aria now prorates the associated discounts on invoices inline, handling both proration and remainder factors across first and last uses.

This change updates the following APIs: create_discount_rule_m, get_discount_rule_details_m, create_coupon_m, update_coupon_m, and get_coupon_details_m. We updated the API field description for <remainder_discount_rule_indicator> to:

When set as 1, it will prorate the discount applied on the initial invoice if the respective charge is prorated and then force the remaining proportion of the discount on its final application. In any of its application, if respective charge is prorated, then the discount also gets prorated. By default it's null. This parameter is applicable only for (a) duration_type_ind = M (months type duration) and (b) duration_type_ind = U (usage count type duration) with flat_percent_ind = F (fixed discount type).

PayPal Wallet Pay Method Added For PayPal Smart Payments (DEV-12408)

To support the new PayPal Wallet pay method (pay method 52), Aria adds two new APIs: int_paypal_token_creation_m and complete_paypal_token_creation_m.

The init_paypal_token_creation_m api creates the token. To initiate the token creation process, you need to pass account inputs and the amount field. By passing either <acct_no> or <client_acct_id>, Aria identifies the account and creates the paypal wallet payment method (pm=52). You can pass either “0“ or any amount greater than 0 in the amount field.

If the amount is “0“, then Aria creates the setup token in PayPal and returns the confirmation url and session token. If the amount is greater than 0, Aria creates an order along with the token and returns the confirmation url and session token.

You can send billing group inputs (via <billing_group_no> or <client_billing_group_id> or <master_plan_instance_no> or <client_master_plan_instance_id>) to get the Billing Group’s Collection Group, which will be used to create the PayPal token. Once the payment method (pm=52) is created, Aria will map the created PayPal payment method as the Billing Group’s primary pay method.

The PayPal Wallet pay method supports the following actions:

• Authorization (as part of the PayPal Wallet token creation flow)
• Payment
• Capture
• Reversal
• Refund

For init_paypal_token_m , the input fields are as follows:

The output fields are as follows:

You must complete the form submission with the URL returned in the <agreement_confirmation_url> output field.

For complete_paypal_token_m, you must pass the account inputs and <request_token> value from the init_paypal_token_creation_m API to complete the token creation process.

The input fields are as follows: 

The output fields are as follows:

Aria allows you to send the Billing Group inputs (via <billing_group> or <client_billing_group_id> or <master_plan_instance_no> or <client_master_plan_instance_id>) to get the Billing Group's Collection Group for the zero amount, which is used to create the PayPal token. Once the payment method (pm=52) is created, Aria maps the created PayPal payment method as the Billing Group's primary pay method.

CM Amount Applying Only To Tax Line And Not Returning Associated Charge Line (DEV-12463)

The get_cm_details_m API logic has been updated to correctly retrieve and include the applicable tax lines in the API response. Previously, the get_cm_details_m API did not return tax line values when a credit memo was applied only to tax line items. The corresponding charge line items were then not included as part of the credit memo application.