Skip to main content
Aria Knowledge Central

Release 60

Overview

Enhancements and fixes to Aria functionality for this release are described below.

Release Date

Stage Future Release Date

 08-October-2024

Production Release Date

 30-October-2024

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 60 Contents

  1. Application Features 
    1. Auto Rescue Now Available For Adyen Credit Card/Tokenized Card Smart Payments (DEV-11397)
    2. Installment Terms Phase 4: Extended Use Cases (DEV-11504)
    3. Enhanced Bill Date Reset Support For Reactivated Master Plans (DEV-11543)
    4. Auto-Renew Contracts With Different Durations (DEV-11544)
    5. Daily-Weekly Contract Duration (DEV-11546)
    6. Sale/Authorization Code Enhancement for Vantiv Payment Gateway (DEV-11551)
    7. New "Service Type" Replacement String Now Available on Statement Templates (DEV-11552)
    8. New Statement Replacement Strings and API Outputs to Display Activation Charges (DEV-11553)
    9. New "Legal Entity" Replacement Strings Now Available on Statement Templates (DEV-11554)
    10. New Loop Available For Displaying Funcional Account Group Information on Statements (DEV-11555)
    11. New "Payment Term" Replacement Strings Now Available on XML Statement Templates (DEV-11556)
    12. Webhook Notifications Implemented for Worldline Smart Payments (DEV-11559)
    13. Apple Pay Payment Method Now Available With Worldline Smart Payments (DEV-11587)
    14. BACS, SEPA and Apple Pay Transaction Logging for Worldline Smart Payments (DEV-11588)
    15. CCP Quick Search Parameter Expansion (DEV-11600)
    16. CCP Pending Invoice List View And Pending Invoice Approval (DEV-11601)
    17. Additional Fraud Feature Support for Worldline Smart Payments (DEV-11637)
    18. CCP Subscription Billing Group Details Drawer And Actions (DEV-11641)
    19. Token Removed When Removing BACS/SEPA For Worldline Smart Payments (DEV-11668)
    20. Account Balance Shows Negative Value Even When There Is A Balance Due (DEV-11673)
    21. Support Currency Scale Specification For Locale-specific Currency Formats (DEV-11676)
    22. Search Web API Logs For set_acct_notify_tmplt_grp_m Via Account Number (DEV-11692)
    23. Application Fixes 
  2. API Features 
    1. Installment Terms Phase 4: Extended Use Cases (API)(DEV-11504)
    2. Enhanced Bill Date Reset Support For Reactivated Master Plans (DEV-11543)
    3. Auto-Renew Contracts With Different Durations (DEV-11544)
    4. Daily-Weekly Contract Duration (DEV-11546)
    5. New API Outputs to Display Activation Charges (DEV-11553)
    6. Webhook Notifications for Worldline Smart Payments (API) (DEV-11559)
    7. Update Payment Token via API Added for Worldpay Smart Payments (DEV-11577)
    8. Avalara Billing Group Company Code API Override of Tax Configuration UI Value (DEV-11581)
    9. CCP Password Length and Requirements (DEV-11594)
    10. CCP Subscription List View And Queued Changes (DEV-11595)
    11. Fraud Scoring Fields Added for Worldpay Smart Payments (DEV-11636)
    12. Token Removed When Removing BACS/SEPA For Worldline Smart Payments (APIs) (DEV-11668)
    13. API Fixes 
  3. WSDL File Locations
    1. Object Query WSDL Files

Application Features 

Auto Rescue Now Available For Adyen Credit Card/Tokenized Card Smart Payments (DEV-11397)

Aria now implements auto rescue for Credit Card and Tokenized Credit Card pay methods in the event of real-time payment failures; this is available through the Adyen Smart Payments integration. This works when the client parameter Allow Dunning during payment recovery is set to True.


Installment Terms Phase 4: Extended Use Cases (DEV-11504)

As part of Phase 4 of Installment Terms implementation for non-subscription offerings (NSOs), Aria now supports lump sum installment payments, mid-period cancellation of installments, and additional use cases:

  • This release of Installment Terms includes support for dunning late fees; a past due installment will be considered as part of dunning fee calculation.
    • For electronic dunning, Aria now excludes the future installment balance from the master plan instance (MPI) balance to calculate the dunning fee via Fee Type: Percentage Fee, which is determined when you create a dunning process. This implementation is only for self-pay MPIs.
    • For Net Terms dunning, Aria now excludes the future installment balance from the MPI balance to calculate the dunning fee via Fee Type: Percentage Fee. This implementation is only for self-pay MPIs.
  • The Days Until Due field value on a Payment Term configuration (Finance > Payment Terms > [New Payment Term]) and a Payment Method configuration (Configuration > Payments > Payment Method > [Add a Payment Method]} is now used to calculate the invoicing due date for independent installments. These enhancements were made in the Aria UI as well as the relevant APIs.
  • Aria has also introduced additional loops and strings in support of lump sum payments; please contact your Aria representative for more information. Also, if there is a lump sum with a given installment schedule, the lump sum payment will appear first on that schedule. Otherwise, the oldest installment appears first.
  • UI Improvements:
    • An existing installment with lump sum now will display lump sum details by persisting the data on the checkbox. In previous releases, it didn’t persist, and created confusion with users if those lump sum details stored or not.
    • Mandatory fields are now shown in red.
    • Previously, the installment due displayed incorrectly when aligned_lump_sum = 0 (lump sum is communicated when invoice is created). This has been resolved.

Note: When changing a rate schedule for an aligned installment, the installment payments assume the schedule of the new billing interval (e.g., changing from a monthly to a yearly billing interval).

API-related enhancements for this feature are also presented on this page.


Enhanced Bill Date Reset Support For Reactivated Master Plans (DEV-11543)

This feature adds a new option ("Use the master plan’s next future anniversary date by offsetting with its billing interval") to the client parameter "Automatically Reset Plan Billing Dates on Non-Billable to Billable Account Status Change" (Configuration > Billing > Invoice Settings), allowing you to automatically adjust the billing date for a reactivated plan, even if the plan has been suspended for multiple billing cycles.

You can also select this option for the Reset Billing Dates field in the "Change Plan Status" UI of a Master Plan Instance (Account Overview > Plans > Status link in side panel > Change Plan Status link at the top).


Auto-Renew Contracts With Different Durations (DEV-11544)

This feature enhances Aria's support for contracts by introducing the ability to specify a different contract duration for auto-renewal, when either creating or modifying a contract (e.g., you could specify that a contract auto-renew from a monthly contract to a daily-weekly contract). Key details appear below.

New Client Parameter to Prevent Multiple Contracts for Same Plan

Aria added a new contract-related client parameter, "Prevent multiple active contracts on same plan instance". This setting controls whether you can create multiple active contracts for the same plan instance. When set to "True" (default), you will not be able to create multiple active contracts for the same plan instance, and the system will return the error, "16034—Multiple active contracts on the same Plan Instance are not allowed," if you attempt to do so.

Notes:

  1. Prior to this release and the creation of this client parameter, Aria allowed multiple active contracts on the same plan instance. To retain backward compatibility in currently active Aria client instances, Aria has set it to "False." Because this is a backend setting, you must request that Aria Customer Support set "Prevent multiple active contracts on same plan instance" to "True" to take advantage of this setting.
  2. This parameter will be set to "True" by default in all new Aria instances.
  3. When creating a contract, you can select the option "Automatically discard open contracts on this account for the same service plan?" When you create a contract for a plan instance and select this option, the system will discard existing contracts and create the new contract rather than returning an error.

Aria UI Updates to Support Auto-Renewal of Contracts With Different Durations

You can now choose as a Contract End Action "Renew existing contract automatically with different duration" when creating or modifying either a Multi-Plan or Universal contract in the Aria UI. This option is available under Contract End Action on the screen Account Overview > Plans > Contracts tab > Create a New Contract, after you select Multi-Plan or Universal.

When selected, additional choices appear allowing you to specify an end date or specify a numeric duration and duration type (days, weeks, or months).

New Email Template Classes

Aria introduces two new email template classes to support this feature:

  • Contract Renewal (ARAD): Automatically renew with a different duration.
  • Contract End (CERD): Notify account holders of an impending expiry of an existing service plan contract, which will be automatically renewed with a different duration.

New Version of "Accounts and Master Plan Instances" Event Class

The ability to create contracts with Daily-Weekly durations introduces a new version of the "Accounts and Master Plan Instances" provisioning event class (see release note). If you want to leverage new contract-related fields in this event class, contact Aria Support to update it to version 3.6.


Daily-Weekly Contract Duration (DEV-11546)

This feature introduces the ability to create contracts with a daily or weekly duration. You can specify a daily-weekly duration either while creating or modifying a contract. In Account Overview > Plans > Contracts tab, you can select "Specify Duration" for Contract Completion. Then, you can specify a number in the Contract Duration text field and select "days," "weeks," or "months" in the Contract Duration dropdown menu.

New Version of "Accounts and Master Plan Instances" Event Class

Aria will send two new fields in "Accounts and Master Plan Instances" event payloads for Aria instances using version 3.6 of that event class:

  • <contract_duration_type>: Indicates whether the contract <duration_length> is based on months, weeks, or days. Possible values are 1—days, 2—weeks, or 3—months.
  • <contract_duration_length>: The number of time units specified in the <duration_type> the contract will last after the <start_date> of a contract. 

Note: The field <contract_months> is deprecated from, and will no longer exist in, payloads beginning with version 3.6 of this event class.

Related events:

  • Account Service Plan Contract Pending Expiration
  • Account Service Plan Contract Expired
  • Account Contract Created
  • Account Contract Edited
  • Account Contract Deleted

New Replacement Strings for Contract-related Email Template Classes

You can now select these new replacement strings when creating custom contract-related email templates:

  • "insertContractDurationLength": Contract Duration Length
  • "insertContractDurationTypeInd": Contract Duration Type (numerical value 1—days, 2—weeks, or 3—months)
  • "insertContractDurationTypeStr": String associated with above value (days, weeks, or months)

Sale/Authorization Code Enhancement for Vantiv Payment Gateway (DEV-11551)

Aria’s Vantiv (Litle) payment integration previously only recognized response code 000 for a successful sale/auth transaction; now, Aria will treat 141 and 142 as codes for a successful sale/auth transaction also. This applies to the following pay methods: Credit Card, Tokenized Credit Card, and Merchant-Specific Gift Card.

Learn more about Aria's integration with the Vantiv payment gateway from here.


New "Service Type" Replacement String Now Available on Statement Templates (DEV-11552)

This feature introduces the "insertItemLineType" replacement string for inclusion on Statement Templates to indicate the service type for a line. Following are possible values:

  • Recurring (RC)
  • Activation (AC)
  • Usage based (US)
  • Recurring Arrears (RA)
  • Order based (OR)
  • Surcharge (SC)
  • Tax (TX)
  • Service Credit
  • Coupon Credit
  • Cancellation
  • Minimum Fee

New Statement Replacement Strings and API Outputs to Display Activation Charges (DEV-11553)

This feature adds new statement template replacement strings to show totals of activation-related charges and credits on your customers' statements:

  • "insertGLTotalActivationCharges"—Total of all activation charges in the invoice (including balance transfer transactions);
  • "insertGLTotalActivChgAfterCredits"—Total activation charges minus credits (including balance transfer transactions); and
  • "insertGLActivationDiscountCredits"—Total credits on activation charges (including balance transfer transactions).

New "Legal Entity" Replacement Strings Now Available on Statement Templates (DEV-11554)

This feature adds new replacement strings to show Legal Entity information on your customers' statements:

  • "insertLegalEntityNo"
  • "insertLegalEntityName"
  • "insertClientLegalEntityId"
  • "insertLegalEntityRegistrationNo"
  • "insertLegalEntityVatRegistrationNo"
  • "insertLegalEntityAddress1"
  • "insertLegalEntityAddress2"
  • "insertLegalEntityAddress3"
  • "insertLegalEntityCity"
  • "insertLegalEntityStateProv"
  • "insertLegalEntityLocality"
  • "insertLegalEntityPostalCode"
  • "insertLegalEntityCountry"

New Loop Available For Displaying Funcional Account Group Information on Statements (DEV-11555)

This feature introduces the loop "beginLoopAcctFunctionGroups" to display Functional Account Group information on statements. Replacement strings available are:

  • "insertAcctFuncGrpGroupNo"—Functional Account Group No;
  • "insertAcctFuncGrpGroupName"—Functional Account Group Name;
  • "insertAcctFuncGrpClientGroupId"—Client Group ID; and
  • "insertAcctFuncGrpDescription"—Description.

New "Payment Term" Replacement Strings Now Available on XML Statement Templates (DEV-11556)

This feature adds new replacement strings to show Payment Terms information on XML statement templates. The new replacement strings are: "insertStmtPaymentTermsNo", "insertStmtClientPaymentTermId", "insertEanGlnNumber", and  "insertEanGlnRequisitionNumber".


Webhook Notifications Implemented for Worldline Smart Payments (DEV-11559)

With this release of Smart Payments for the Worldline payment gateway, Aria now supports webhook notifications for the following event types to support changes in transaction status:

  • payment.captured
  • payment.paid
  • payment.reversed
  • payment.rejected
  • payment.rejected_capture

Note: A webhook notification is a message that can be sent automatically between applications whenever a designated event occurs. These messages can serve as updates in real time and streamline payment processing for clients and their customers.

API-related enhancements for this feature appear below.


Apple Pay Payment Method Now Available With Worldline Smart Payments (DEV-11587)

Aria is excited to introduce Apple Pay as a digital payment method to our Worldline Smart Payments integration. Tokenized payments (initial payments and refunds) are supported for the Mastercard® card type.

To configure Apple Pay for Worldline Smart Payments, navigate to the Apple Pay tab (Configuration > Payments > Payment Gateways/Collection Groups [WorldPay]). 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 can now contact Aria with your Apple Pay payload using existing Aria APIs as part of your Worldline Smart Payments integration.


BACS, SEPA and Apple Pay Transaction Logging for Worldline Smart Payments (DEV-11588)

Aria has added the following in support of the Worldline payment gateway as part of Smart Payments integration:

BACS Direct Debit Payments

Worldline now supports Tokenized Direct Debit initial and recurring BACS Direct Debit payments (pay method 37) for Create Token and Query Token actions. This also includes integrated transaction logging with masking of sensitive information.

SEPA Approve Mandate and Capture Payments

This release also includes support for SEPA Approve Mandate and Capture Payments (pay method 37). SEPA payments are enabled via the following process:

Apple Pay Transaction Logging

Aria now supports transaction logging for Apple Pay transactions from Worldline Smart Payments. To do this, two new fields (dpan and verified_auth_value) have been introduced in the Logging Payment Request to display the Worldline Apple Pay transaction details. As with BACS transaction logging, the dpan value will ben masked as it contains sensitive information.


CCP Quick Search Parameter Expansion (DEV-11600)

The parameters available through Quick Search have been expanded to include the following search parameters that do not require a search operator: Test Account, Account Status, Subscription (Formerly Account Service Plan), and Custom Fields (Formerly Client Defined Account Fields). The search has also been updated to display a comprehensive explanation (via tooltip hover) of why the listed account matches the query.


CCP Pending Invoice List View And Pending Invoice Approval (DEV-11601)

Pending Invoices can now be viewed, recalculated, and approved in Customer Care Portal (CCP) from CCP > Transactions > Pending Invoices

Click on the invoice number within the list to expand the Invoice Details pop-out drawer. From this Invoice Details drawer, select the History tab to view a list of previous actions that have been taken on the pending invoice.

To approve an invoice, recalculate an invoice, or View & Print an invoice select the row actions ⋯ on any pending invoice line and then click the action you want to take.


Additional Fraud Feature Support for Worldline Smart Payments (DEV-11637)

With this release, Aria introduces additional fraud security as part of Worldline's Smart Payments integration. An end_user_device_fingerprint field is now included at the Payment Gateway and Collection Group levels (Configuration > Payments > Payment Gateways/Collection Groups > Advanced Options); this field, when used with the <bill_address> field from the validate_acct_fraud_scoring_m API, will limit the number of attempts to validate fraud scoring through this API (10 attempts is the default).


CCP Subscription Billing Group Details Drawer And Actions (DEV-11641)

The Billing Group Details drawer has been updated to enhance the experience of managing billing groups through CCP. You can now access the updated drawer from Subscriptions > Details > Edit. This opens a drawer with the following three tabs:

  • Billing Tab: This tab displays the billing group details, which are pre-populated. Users can update these details and manage Statement Recipients’ emails with options to add to both CC and BCC lists.
  • Payment Tab: You can now add or select Primary Payment Method, Secondary Payment Method, Collection Group, Statement Contact, and Terms (Note: Terms details cannot be edited).
  • Subscriptions Tab: You can now manage subscriptions by assigning or unassigning them from the billing group table.

Token Removed When Removing BACS/SEPA For Worldline Smart Payments (DEV-11668)

When removing BACS/SEPA as a payment method for Tokenized Direct Debit payments (pay method 37), the token associated with that payment is also removed. This can be accomplished within Aria Billing Cloud by navigating as follows:

  • Accounts > [search for an account] > Account Overview > Payment Methods (Delete Payment Method)

Account Balance Shows Negative Value Even When There Is A Balance Due (DEV-11673)

The Account Balance calculation has been modified to deallocate the adjusted negative balance forward (Transaction Type 18) from the invoice during the invoice void actions. 


Support Currency Scale Specification For Locale-specific Currency Formats (DEV-11676)

This feature adds support for displaying currency amounts formatted with a Locale-specific currency mask to the currency scale you have specified for your Aria instance (Configuration > Billing > Currencies > (click a currency) > Currency Scale).


Search Web API Logs For set_acct_notify_tmplt_grp_m Via Account Number (DEV-11692)

This feature adds the capability to search Aria's Web Service API Logs by account number for the API call set_acct_notify_tmplt_grp_m, even if you called it specifying a <client_acct_id> or <user_id>.


Application Fixes 

  • The correct line item names are now calculated and displayed on invoices. The name displayed on the invoice is now determined by the last sequence number before a tax call and each subsequent invoice line item is incremented by that sequence number plus one. This ensures the service credit line item has a unique sequence number and that the line item amount and comments are correctly displayed. (TICKET-19216)
  • The time stamps for both the Start Date and End Date UI input fields are now cleared when editing Taxation Configuration. Previously, when editing internal tax rates via Configuration > Integrations > Taxation Configuration > Internal Values tab, the existing taxes had a Start Date listed with an incorrectly formatted time stamp which caused an error stating “The date format is invalid” upon attempting to save. (TICKET-19511)

  • When you switch from Payment Terms to a Payment Method for a billing group via Accounts > select an account > Plans > Billing Groups in the UI the payment terms are now cleared from the billing group and the selected Payment Method is used.

    Previously, Billing Group History was not saving properly when switching between Payment Method and Net Terms and, as a result, the Payment Option and Net Terms remained associated with the billing group instead of displaying the client's Primary Payment Method. (TICKET-19534)


API Features 

Installment Terms Phase 4: Extended Use Cases (API)(DEV-11504)

The following API enhancements are included in Phase 4 of NSO Installment Terms:

New API

The get_acct_statement_all_m Core API has been added with this release. This API returns the list of all statements along with installments (when applicable) on an account for all the MPIs or a specified MPI, statement, statement sequence string, secondary statement sequence string, or invoice associated with the account at the time the statement is generated.

Existing APIs

create_order_m

The following output has been added:

Field Name Field Type Description
<installment_no> Long Aria-assigned installment schedule no (added to existing <cart_invoice_line_items> array).
<installment_term_no> (Existing parameter) Long Description updated to "Aria-assigned installment term no."

create_order_with_plan_m

The following inputs have been added:

Req Field Name Field Type Description
  <order_line_items> hash existing hash
  <assign_installment_term> string

Allowable values:

  <client_installment_term_id> string Specifies client installment id. If null, then it selects the installment default.
  OR    
  <installment_term_no> string Installment no on product catalog. If null, then it selects the installment default.

The following outputs have been added:

Field Name Field Type Description
<cart_invoice_line_items> array Existing array
<installment_term_no> Int Aria-assigned installment term no
<installment_no> Int Aria-assigned installment schedule no

get_acct_installment_m

The following input has been added:

Req Field Name Field Type Description
<installment_no> Long Aria-assigned installment schedule no.

The following outputs have been added:

Field Name Field Type Description
<order_no>   The unique identifier for an order in the context of an client_no and account_no
<billing_group_no>   Billing Group Number
<client_billing_group_id>   The billing group's client assigned identifier
<master_plan_instance_no>   The Master Subscription plan instance number
<client_master_plan_instance_id>   Client-defined Master plan Subscription plan instance ID
<total_amount>   Total amount on installment after service credit and discount - includes tax

get_invoice_history_m

The following output has been added:

Field Name Field Type Description
<installment_ind> long

Indicates if one or more invoice lines have installments.

Allowable Values

Values Description
0 No Installment
1 Has Installment

Exclude Future Installment Dues from Collections: Future installment dues are now excluded from collection processes triggered by:


Enhanced Bill Date Reset Support For Reactivated Master Plans (DEV-11543)

This feature adds a new option to the <force_bill_date_reset> field in several API calls allowing you to automatically adjust the billing date for a reactivated plan, even if the plan has been suspended for multiple billing cycles. This option will set the next billing date to a future date that aligns with the original billing schedule. This change is available in these API calls: update_acct_plan_status_m, update_acct_plan_m, replace_acct_plan_m, update_acct_plan_multi_m, and edit_acct_plan_queued_changes_m.

Existing Input Field New Allowable Value
<force_bill_date_reset>
Value Description
3 Reset the billing anniversary date to coincide with next future anniversary date by offsetting with its billing interval.

Auto-Renew Contracts With Different Durations (DEV-11544)

This feature enhances Aria's support for contracts by introducing the ability to specify a different contract duration for auto-renewal, when either creating or modifying a contract (e.g., you could specify that a contract auto-renew from a monthly contract to a daily-weekly contract). Aria has updated several API calls to accommodate this new functionality.

New API Input Fields, Updated Allowable Values

Input Field Type Description
<renewal_duration_type> (new field) long

Indicates whether the contract renewal duration in length is based on months, weeks or days.

Allowable Values

Values Description
1 Days
2 Weeks
3 Months
<renewal_duration_length> (new field) long The numerical value of the contract renewal duration in units specified by <renewal_duration_type>. 
<renewal_end_date> (new field) string Date on which the renewal contract ends. Date format is YYYY-MM-DD. For the new contract type '9-Renew contract with different duration',  it is mandatory to pass the either the renewal_end_date or the renewal_duration_type and renewal_duration_length. If both are passed, renewal_duration_length will take the precedence over the renewal_end_date.

create_acct_complete_m: <contract_type_no> (existing)

create_instance_contract_m, create_acct_universal_contract_m, modify_instance_contract_m, modify_acct_universal_contract_m: <type_no> (existing)

 

 

New Allowable Value

Value Description
9 Renew existing contract automatically with different duration.

New API Output Fields

New Output Field Type Description
<renewal_duration_type> long

Indicates whether the contract renewal duration in length is based on months, weeks or days.

Allowable Values

Values Description
1 Days
2 Weeks
3 Months
<renewal_duration_length> long The numerical value of the contract renewal duration in units specified by <renewal_duration_type>. 
<renewal_end_date> string Date on which the renewal contract ends. Date format is YYYY-MM-DD. For the new contract type '9-Renew contract with different duration',  it is mandatory to pass either the <renewal_end_date> or the <renewal_duration_type> and <renewal_duration_length>. If both are passed, renewal_duration_length will take the precedence over the renewal_end_date.

Note: If the <renewal_duration_type> and <renewal_duration_length> were provided during contract creation, then <renewal_end_date> would not be returned in the output. And if <renewal_end_date> were provided during creation, then <renewal_duration_type> and <renewal_duration_length> would not be returned in the response. If both the renewal duration fields and <renewal_end_date> were provided, then the renewal duration values would take precedence and be returned in the response (not the end date).


Daily-Weekly Contract Duration (DEV-11546)

This feature introduces the ability to create contracts with a daily or weekly duration. You can specify a daily-weekly duration both while creating or modifying a contract. New input fields <duration_type> and <duration_length> are added to these APIs to support this functionality: create_acct_complete_m, create_instance_contract_m, create_acct_universal_contract_m, modify_instance_contract_m, and modify_acct_universal_contract_m

New Input Field Type Description
<duration_length> long The number of time units specified in the <duration_type> the contract will last after the <start_date> of a contract. 
<duration_type> long

Indicates whether the contract <duration_length> is based on months, weeks, or days.

Allowable Values

Values Description
1 Days
2 Weeks
3 Months (default)

New API Outputs to Display Activation Charges (DEV-11553)

This feature adds new output fields to show totals of activation-related charges and credits on the API Call get_acct_preview_next_bill_m. The new output fields are: <total_activation_charges>, <total_activation_charges_after_credits>, and <total_activation_discount_credits>.

New Output Field Type Description
<total_activation_charges> double Total of all activation charges of the next invoice which includes balance transfer transactions (if any) for parent pay.
<total_activation_charges_after_credits> double Total activation charges minus credits which includes balance transfer transactions.
<total_activation_discount_credits> double Total discount and service credits applied to activation charges including balance transfer activation discount & credits.

Webhook Notifications for Worldline Smart Payments (API) (DEV-11559)

In support of webhook notifications for Worldline Smart Payments, validations have been added to the following existing fields of the update_payment_method_token_m API:

  • <cc_expire_mm>
  • <cc_expire_yyyy>

The following error messages are now included for this API to support this feature:

Error Message Description
33005 When specifying a pay_method_no, then the fields cc_expiration_date, or demographics should be provided as an additional input for validation.
4008 Invalid expiration date. The date must be a future date.

Update Payment Token via API Added for Worldpay Smart Payments (DEV-11577)

With this release, Aria adds the ability to update token expiry details for Worldpay as part of Smart Payments integration via the update_payment_method_token_m API. This includes the following input fields:

  • <cc_expire_mm>
  • <cc_expire_yyyy>
  • <bill_first_name>
  • <bill_last_name>

Avalara Billing Group Company Code API Override of Tax Configuration UI Value (DEV-11581)

Aria has added enhancements to selected APIs to override the Avalara company code at the Tax Configuration screen (Configuration > Integrations > Taxation Configuration > Avalara Tax Service). The new <taxation_company_code> for these APIs will be stored against the respective billing group and will be sent in the tax request of all subsequent invoices for the affected account.

The following APIs have been enhanced to support this feature:

API Enhancement
create_acct_complete_m A new field, <taxation_company_code>, is added to the <bliing_group> array.
The given <taxation_company_code> will be mapped with the newly created billing group.
create_acct_billing_group_m, update_acct_billing_group_m, assign_acct_plan_m A new field, <taxation_company_code>, is added as the first-level parameter in the API request.
The given <taxation_company_code> will be mapped with the newly created billing group.
update_acct_plan_multi_m A new field, <taxation_company_code>, is added inside the <acct_billing_groups> array.
update_acct_complete_m A new field, <taxation_company_code>, is added inside the <billing_groups_array> array.

CCP Password Length and Requirements (DEV-11594)

Passwords for Customer Care Portal (CCP) must be a minimum of 12 characters and contain at least one alphabetic, one numeric and one special character (!@$^()+-). These can be reset through legacy Aria APIs and the REST API. Set the Minimum Password Length setting at Client Settings > Miscellaneous Settings.


CCP Subscription List View And Queued Changes (DEV-11595)

The following output fields have been added to the get_acct_plan_queued_changes_m API: 

  • <current_rate_schedule_name>
  • <target_rate_schedule_name>
  • <anniversary_queue_ind>
  • <processed_by_batch_ind>
  • <execute_allowed>
  • <change_effective_date_allowed>
  • <delete_allowed>
  • <update_date>
  • <queue_type>

Allowable Values for <queue_type>

Values Description
1 Plan Assignment
2 Mandatory Child Plan Assignment
3 Plan Replacement
4 Plan Rollover
5 Plan Cancellation
6 Plan Update (units, rate schedule, status, etc.)
7 Plan Status Change

 


Fraud Scoring Fields Added for Worldpay Smart Payments (DEV-11636)

Aria enables more fields for fraud sight data scoring as part of Worldpay’s Smart Payments configuration. The following fields will be sent for Tokenized Credit Card payments (pay method 13) via the validate_acct_fraud_scoring_m API:

Aria Fields Worldpay Fields Worldpay Description About This Field
<first_name>+<last_name> shopperName The shopper's name
<acct_no> shopperId Your ID for your shopper
<date_of_birth>

birthDate.date

dayOfMonth="xx"

month="xx"

year="xxxx"

The shopper's date of birth
<bill_first_name> shopperAddress.address.firstName The first name of the shopper on your system
<bill_last_name> shopperAddress.address.lastName The last name of the shopper on your system
<bill_address1> shopperAddress.address.address1 The first line of the shopper's address
<bill_address2> shopperAddress.address.address2 The second line of the shopper's address
<bill_zip> shopperAddress.address.postalCode The shopper's post code
<bill_city> shopperAddress.address.city The shopper's city
<bill_country> shopperAddress.address.countryCode The shopper's country (Format: ISO-3166 country code)
<intl_phone> shopperAddress.address.telephoneNumber The shopper's telephone number

To use this feature, the following must be configured at the Payment Gateway or Collection Group level for Worldpay (Configuration > Payments > Payment Gateway/Collection Groups > Processing Options):

  • Send Fraud Sight Request – Enabled

The following fraud score results are returned from Worldpay via validate_acct_fraud_scoring_m when Send Fraud Sight Request is Enabled (from the <proc_fraud_scoring_info> array/ <proc_fraud_score_result> field:

  • High-Risk
  • Low-Risk
  • Review

Token Removed When Removing BACS/SEPA For Worldline Smart Payments (APIs) (DEV-11668)

When removing BACS/SEPA as a payment method for Tokenized Direct Debit payments (pay method 37), the token associated with that payment is also removed. This can be accomplished via the following APIs:


API Fixes 

  • The <credit_expiry_date> value has been modified to use the get_credit_details_m API’s default date format of YYYY-MM-DD. (TICKET-15090)
  • The update_acct_plan_multi_m API has been modified to retrieve the Client Defined Identifier using Aria generated sequence numbers and return it in the API response fields <primary_client_payment_method_id> and <backup_client_payment_method_id>. Previously, these output parameters were returning incorrect values. (TICKET-19085)
  • The APIs modify_instance_contract_m and create_acct_complete_m API calls now return Error Code 1016: "Invalid input: Specify only one among length_months/duration_length and end_date" if you pass values in both input fields <end_date> and <duration_length> when specifying contract parameters. (TICKET-19526)
    This change introduces a change in behavior:

    • Previously, modify_instance_contract_m accepted both input fields, but only honored <duration_length>. 

    • Previouslly, create_acct_complete_m accepted both input fields, but only honored <end_date>.

  • When you switch from Payment Terms to a Payment Method for a billing group Accounts > select an account > Plans > Billing Groups in the UI the payment terms are now cleared from the billing group and the selected Payment Method is used.

    Previously, Billing Group History was not saving properly when switching between Payment Method and Net Terms and, as a result, when using get_acct_billing_group_details_m API the Payment Option and Net Terms remained associated with the billing group instead of displaying the client's Primary Payment Method. (TICKET-19534)


WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

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