Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!



 

Home > Aria Crescendo Documentation > Aria Crescendo Release Notes > Release 19

Release 19

This article applies to:Aria Crescendo

Overview

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

Release Date

Stage Future Release Date

6-December-2018

Production Release Date

9-January-2019

System Requirements

Supported Browsers

  • Chrome 63
  • Firefox 52
  • IE11
  • Safari 11 on MacOS 

Screen Resolution

1024 x 768 or higher


Application Features

Create Recurring Service Credit with Expiration (DEV-4426)

You can now set up a recurring service credit with an expiration month/date as a goodwill gesture or for other business reasons. To do so, in the Aria application, create a new service credit and enter your chosen Expiration month/date and Frequency.

Note: The expiration date must be after the application date of the last service credit applied based on your specified Frequency. Example: If you create a service credit to be applied in the next 2 months, the expiration date must be more than 2 months away.


Assign a Collection Group to a Billing Group (DEV-8075)

For cost savings or for other reasons, you may choose to have payments made with a particular payment method processed by a specific payment gateway. To do so, you can now assign a collection group to a billing group when you:

Notes:

  • Aria will use this order of precedence when selecting the payment gateway to use for processing a payment:
  1.  Collection group assigned to the billing group associated with the master plan instance being invoiced;
  2.  Collection group to which the customer is assigned at the account level.
  • Aria does not currently support using collection groups at the billing group level when the tokenized credit card payment method is used. For this payment method, Aria will make collections using the payment gateway associated with the collection group at the account level.

You can also you APIs to assign a collection group to a billing group.


Deferred, Unapplied Payments (DEV-8957)

Users can now apply electronic or non-electronic payments to their accounts and defer their applications to anytime in the future via either API or UI; or, move a payment from one charge transaction to another via API or UI. Aria tracks accounts' Unapplied Payments and makes summary and balance information available via API, UI and statements.

Creating an Unapplied Payment

Getting here: Account Overview, or Account > Payments & Credits > Apply a Payment

  1. Find the account you want to add an unapplied/deferred payment to.
    8957_01_acctoverview.png

    1- The Account Overview now shows an "Unapplied Payments" balance.
    2- Click the "Make a Payment" button.
  2. Choose a payment option. Both electronic and non-electronic payments can be used to make an unapplied payment.
  3. Choose "Defer until later" from the "Apply Against" drop-down menu.
    8957_03_makepayment.png
  4. Choose either Balance Due, or type an amount for the payment, then click the "Apply Payment" button.
    .
    8957_04_makepayment.png
     
  5. Upon success of the payment. on the account overview, the "Full Balance" and "Unapplied Payment(s)" totals have updated.

    8957_05_balance_after_deferred.png

    1- The "Full Balance" is reduced by the Unapplied payment. This prevents an over-collection by the Aria collection batch process.
    2- The "Unapplied Payment(s)" total reflects the amount of the deferred payment.

Applying a Deferred Payment

Getting here: Account Overview, or Account > Payments & Credits > Apply a Payment

  1. Find the Account Overview of the account with an Unapplied Payment you wish to apply. 
  2. On the Payment page, choose "Unapplied Payments" from the "Payment Option" pick list; then, click the "Select" link.8957_06_make_payment_from_deferred.png
  3. The Unapplied Payment list opens in a pop-up window. Choose the Unapplied Payment from which you want to draw the payment.
    8957_07_select_deferred.png
  4. Choose what you want to apply the payment against from the "Apply Against" drop-down menu, then select or type the amount you want to apply.
    8957_08_amount_less.png
    1- You can choose the apply the payment against:
    Charges per standard FIFO method: Choosing this option applies the payment on a "First-In, First-Out" basis, and will apply to oldest charges first.
    Invoices and other account-level charges: Choosing this option loads a list of invoices and othere account-level charges; type an amount next to the charge(s) you want to apply the payment against.
    Services (invoice line items) : Choosing this option loads a list of line-item charges that have not yet been paid in full. Type an amount next to the charges) you want to apply the payment against.
    2- If the Unapplied Payment equals or exceeds the Full Balance on the account, you can choose to apply it to the Full Balance. Otherwise, you must choose "Other Amount" and type an amount equal to or less than the Unapplied Payment selected. 
  5. The balances on the account reflect the new totals:

    8957_09_final_balance_after_application.png

    1- The Full Balance remains the same, because the previous Unapplied Payment has already been taken into account.
    2- The Unapplied Payment(s) balance is reduced by the amount drawn from the Unapplied Payment.

Unapplying a Payment

Getting here: Account > Payments & Credits > Unapply a Payment

  1. In this example, the chosen account is starting with the same Full Balance and Unapplied Payment(s) balance shown in Step 5 above. On the Payments & Credits screen, click the Unapply a Payment link. 

    8957_10_unapply_link.png
  2. Choose what you want to unapply the payment from, choose or type the amount you want to unapply, then click the "Unapply Payment" button.8957_11_unapply-2.png

    1- Choosing "Invoices and other account-level charges" will load a list of invoices and other account-level charges. Choosing "Services (Invoice line-items)" loads a list of line-level charge transaction. Type an amount in the text box(es) of the row(s) displaying the charge(s) you want to unapply payments from.
    2- Check the "Unapply all" checkbox to unapply the full amount of all the payments listed.
  3. When the payment is unsuccessfully applied, the account's Unapplied Payment(s) balance increases by the amount specified when unapplying the payment(s).

    8957_12_post_unapply_balance.png

New Vertex O Series Tax Engine Configuration Parameter to Skip Line Item Address (DEV-8982)

For the Vertex O Series Tax Engine, Aria has introduced a new configuration option, "Skip Default Line Level Destinations," on the Vertex O Series config page. When set to "Yes," and the line item and header levels share the same address, Aria will not send the line item level address to Vertex.

8982-skipparam.png


Assign Custom Rates to Future Plans (DEV-9021)

If a customer has a future plan that is already scheduled to be assigned after a rollover from a currently-assigned plan, you can now assign custom rates to the future (queued) plan. This applies to a future plan that is scheduled to be assigned on the customer's  anniversary date or on any other chosen date. Example: You may choose to offer a customer a promotional rate for a future plan as a goodwill gesture or for other business reasons.

Use the Aria application to assign custom rates to a queued plan.

You can also use APIs to assign custom rates to a future plan.


Billing Groups and Master Plan Instances Invoice When Some Plans Have Future Plan Changes (DEV-9038)

Aria now allows Billing Groups and Master Plan Instances that include multiple plans, one or more of which have future plan changes scheduled, to invoice. Such invoices exclude plans with queued changes, and invoices them when the change is executed.

Previously, Aria returned error codes 1069 (Long cycle invoice is not available) or 3100 (Future invoice cannot be created) if just one plan in a Billing Group or Master Plan were queued for a change. Now, these errors are returned only when all plans in the Billing Group or Master Plan Instance have queued changes.


3D Secure Authentication Support for Adyen Payment Gateway (DEV-9050)

Aria now supports 3D Secure authentication for payment transactions processed through the Adyen Payment Gateway. When calling APIs authorize_electronic_payment_m, validate_acct_fraud_scoring_m, or update_payment_method_m authorize_electronic_payment or validate_acct_fraud_scoring (or associated Direct Post procedures) with additional API input parameters (documented in the API Features section below), Aria parses the results to support either Manual or Dynamic 3D Secure authentication.

Note: If you enable Adyen’s Dynamic 3DS service, you must configure it in Adyen’s configuration portal. 3DS configuration is not available in the Aria UI.


Support for Adyen Fraud Tools, RevenueProtect+ (DEV-9051)

Aria has enhanced its integration with the Adyen Payment gateway to support Adyen's RevenueProtect+, a fraud protection mechanism. The API validate_acct_fraud_scoring_m validate_acct_fraud_scoring (documented in the API Features section below) now sends fraud-related customer data to Adyen's customizable rules engine to return more granular fraud scoring for payment transactions. 

This enhanced integration includes support for existing fraud capabilities of Aria's Direct Post.

Configuring Adyen Payment Gateway to Support Fraud Tools

Getting here: Configuration > Payments > Payment Gateways > Adyen

This assumes that you have already configured the Adyen Payment Gateway in Aria. A "Fraud Options" section appears on the Gateway Options tab.

9051_fraudoptions_adyen_numbered.png

  1. Send Fraud Scoring Request: When set to true, Aria sends a request to Adyen to return fraud scoring information. If the fraud score returned is below the Fraud Scoring Threshold or the Fraud Score response is "Not Successful," Aria modifies the status based on "Change Status on Fraud Scoring Failure" setting. "Send Fraud Scoring Request" must be set to "True" to enable the "Change Status on Fraud Scoring Review" menu.
  2. Change Status on Fraud Scoring Review: When set to true, Aria changes the status of the Master Plan Instance(s) to the value selected on the "Status on Fraud Scoring Review" drop-down menu; and, the Fraud Score response is "Review." "Change Status on Fraud Scoring Review" must be set to "True" to enable the "Status on Fraud Scoring Review" drop-down menu.
  3. Change Status on Fraud Scoring Review: When set to true, Aria changes the status of the Aria Account to the value selected on the "Status on Fraud Scoring Review" drop-down menu; and, the Fraud Score response is "Review." "Change Status on Fraud Scoring Review" must be set to "True" to enable the "Status on Fraud Scoring Review" drop-down menu.
  4. Status on Fraud Scoring Review: This parameter governs the behavior for changing the status when Fraud Scoring is enabled and Change Status on Fraud Scoring Review is set to "True."

    9051_fraudoptions_adyen.png

Enhanced Adyen Processor Integration to Process Responses for All Payment Methods (DEV-9058)

Aria has expanded its Adyen payment processor integration to process notifications from not only the iDeal and Boleto payment methods (pre-Release 19), but also from all other payment supported methods. These notifications include CAPTURE, REFUND, CANCELLATION, AUTHORIZATION, CAPTURE_FAILED and REFUND_FAILED events.


Delete a Customer's Personal Data (DEV-9077)

You can now use the Aria application to delete (anonymize) a customer's personal data in compliance with the General Data Protection Regulation (GDPR). When you use this feature, personally identifiable account information such as a name, user ID, and location data will be hidden in the Aria application as shown here.

 

Notes:

  • The changes made by anonymizing data are irreversible so, before completing that process, it is highly recommended that you:
    • Record the customer's consent/confirmation; and
    • Address any open charges, credits, unbilled usage, etc. with the customer.
  • If you anonymize a parent account, the child account is not anonymized and vice versa.

 


New Audit Log Pruning Behavior (DEV-9096)

When audit logs are pruned and not available for display, Aria displays the following message: "Due to the size of the API log data, your results have been pruned in order to display as much data as possible without exceeding threshold limits."


See Plans that Include a Particular Service (DEV-9155)

In a single, convenient view within the plan hierarchy diagram, you can now see the plans that include a particular service.

Note: Only the first 100 in-use plans that include the service will be listed. To see services included in any plan that is not listed, go to Products > Plans > click on a plan > click the Services tab.

 


Enhanced Rate Schedule Support (DEV-9187)

This feature enhances rate schedule functionality with support for a larger number of rate schedules during plan creation, which previously caused plan creation failures. 

The plan creation process itself has not changed; however, the Aria UI includes a separate rate schedule screen, accessible via the Plans list screen.

dev-8197_plan_list.png

Clicking the rate schedule icon loads a Rate Schedules list for the associated plan.

dev-8197_rate_schedule_list.png

  1. Click the New button to create a new rate schedule.
  2. Click an existing rate schedule to edit it.
     

Application Fixes 

  • Payment applications are no longer rounded when created in Aria batch processes. Previously, rounding errors were causing issues with downstream reporting. (TICKET-16664)
  • Date formats are now consistently and correctly displayed in the Aria UI Plan Instance Detail, All Service Rates, and Rate Schedule Detail pages based on the client-defined parameter setting in > Configuration > Client Settings > Miscellaneous Settings > Date Format Mask. (TICKET-16669)
  • $0 refund line items are no longer displayed on an invoice when you issue a full or partial refund that applies to an invoice:
    • With multiple charges; and
    • With or without service credits included.
      (TICKET-16671)
  • Your selection of either of these values for the Dispute Hold Expiration Action parameter is now correctly saved in Aria: Restore and Re-age or Restore or Do Not Re-age. Those values are no longer replaced with each other. (TICKET-16684)
  • An error no longer occurs when Aria adds queued services to plans. Instead, the queued services are added to the plans on your specified dates, as expected. (TICKET-16703)
  • An error message "Bulk Usage cannot exceed more than 1000 records" is now returned when a user tries to upload more than 1000 records via the Aria UI. (TICKET-16719)
  • Errors no longer result when scheduled reports are copied via Copy Config. (TICKET-16725)
  • The Universal Activity Loader (UAL) batch job now runs successfully via the Aria UI. (TICKET-16726)

API Features

Create Recurring Service Credit with Expiration (DEV-4426)

You can now create a recurring service credit with an expiration month/date as a goodwill gesture or for other business reasons. To do so, call the create_advanced_service_credit_m API and:

  1. Pass a number into the frequency_no field to specify the number of times the service credit should be applied to the account.
  2. Pass a value into the credit_expiry_type_ind field to specify whether the credit expiration is based on months (credit_expiry_months) or a specific date (credit_expiry_date).
  3. Based on your specified value in the credit_expiry_type_ind field, pass either the credit expiration month into the credit_expiry_months field or the credit expiration date into the credit_expiry_date field.
  4. Pass a value into the frequency_interval_type field to specify how often the credit should be applied.

Notes:

  • The expiration date must be after the application date of the last service credit applied based on your specified frequency_no. Example: If you create a service credit to be applied in the next 2 months, the expiration date must be more than 2 months away.
  • If you pass in an invalid credit_expiry_date, this error will be returned: "20038 Expiration date needs to be greater than application date of the last recurring service credit.”
  • If you pass in an invalid frequency_interval_type, this error will be returned: "20039 Invalid frequency interval type."

Assign a Collection Group to a Billing Group (DEV-8075)

  1. For cost savings or for other reasons, you may choose to have payments made with a particular payment method processed by a specific payment gateway. To do so, you can now assign a collection group to a billing group by:

Notes:

  • Aria will use the following order of precedence when selecting the payment gateway to use for processing a payment:
  1. Collection group assigned to the billing group associated with the master plan instance being invoiced;
  2.  Collection group to which the customer is assigned at the account level.
  • Aria does not currently support using collection groups at the billing group level when the tokenized credit card payment method is used. For this payment method, Aria will make collections using the payment gateway associated with the collection group at the account level.

 

  1.  You can now obtain information about any collection group assigned to a billing group from the <collections_group_bg_no>, <client_collections_ group_bg_id>, <collections_group_name>, and <collections_group_description> output fields in the following APIs:

 

  1. The error codes listed below can now be generated when you call the APIs identified in this table:
Error Code Error Message Affected APIs
1108 Invalid billing group, collection group directive.
  • update_acct_billing_group_m
  • update_acct_complete_m
  • update_acct_plan_multi_m
12012 Collection group does not exist. All of the APIs listed under number 1 above
12013 Collection group identifier does not exist. All of the APIs listed under number 1 above
12015 Collection group details missing.
  • assign_collections_acct_group_m
  • remove_acct_from_group_m
12016 Billing group belongs to collections based group using same payment method.
  • assign_acct_plan_m
  • create_acct_billing_group_m
  • create_acct_complete_m
  • update_acct_plan_multi_m

12017
Billing group is not assigned to this group.
  • remove_acct_from_group_m
  • update_acct_billing_group_m
  • update_acct_plan_multi_m
12018 Billing group already assigned to this group.
  • assign_collections_acct_group_m
  • update_acct_billing_group_m
  • update_acct_complete_m
  • update_acct_plan_multi_m
26041 Billing group details missing.
  • assign_collections_acct_group_m
  • remove_acct_from_group_m

You can also you the Aria application to assign a collection group to a billing group.


Deferred, Unapplied Payments (DEV-8957)

Users can now apply electronic or non-electronic payments to their accounts and defer their applications to anytime in the future via either API or UI; or, move a payment from one charge transaction to another via API or UI. Aria tracks accounts' Unapplied Payments and makes summary and balance information available via API, UI and statements.

Two new API calls were created:

Two new fields were added to get_acct_payment_history_m and get_refundable_payments_m:

  • Input field <include_unapplied_payments>: Whether or not to include the Unapplied Payments balance in the return.
  • Output field <unapplied_payment_summary>: The balance of the account's Unapplied Payments.

Two new input fields were added to collect_from_account_m and record_external_payment_m:

  • <payment_application_method>: How to apply the payment. You can specify FIFO (first in, first out); FDFO (first due, first out); or none (future manual allocation).
  • <specific_master_plan_instances_list> (array)
    • <master_plan_instance_no>: Aria-assigned master plan instance number against which to apply the payment.
    • <client_master_plan_instance_id>: Client-assigned master plan instance id against which to apply the payment.

Promotion Code Validity Check Parameter Honored (DEV-8994)

To change your setting for the Perform valid promo code check parameter, please contact Aria Customer Support.

  • In addition, the promo_cd field is no longer case sensitive. When you pass a promo_cd into an API without using lowercase, Aria will now convert the promo_cd to lowercase and assign it to the applicable plan.

Assign Custom Rates to Future Plans (DEV-9021)

  • If a customer has a future plan that is already scheduled to be assigned after a rollover from a currently-assigned plan, you can now assign custom rates to the future plan. This applies to a future plan that is scheduled to be assigned on the customer's anniversary date* or on any other chosen date. Example: You may choose to offer a customer a promotional rate for a future plan as a goodwill gesture or for other business reasons.

    To assign custom rates to a future plan, call the assign_custom_acct_plan_rates_m API and pass values into these new input fields: plan_scope and plan_queue_id.

    The selected customer will be charged the new rates for the identified plan on your specified date.
  • These error codes can now be generated by the assign_custom_acct_plan_rates_m API when there is an issue with obtaining plan information: 24016 and 24007.
     
  • When you use any of the APIs listed below to schedule a plan change, you can now use the same call to obtain information about the plan change. You can use this information for record-keeping purposes, for display to your customers, or for other business reasons.

    To obtain information about a scheduled plan change, pass true into a new input called include_plan_instance_queue in any of these APIs: assign_acct_plan_m, cancel_acct_plan_m, create_acct_complete_m, create_order_with_plan_m, replace_acct_plan_m, update_acct_complete_m, update_acct_plan_m, and update_acct_plan_multi_m.

    The information about the plan change will be returned in the new plan_instance_queue output array, which is available in the APIs listed above. 
  • The get_queued_acct_plans_m API has been deprecated. As an alternative, you can now use the get_acct_plan_queued_changes_m API to obtain the rates that are scheduled to go into effect on a customer's anniversary date* or on the activation date of a future plan. You can use this information for record-keeping purposes, for display to your customers, or for other business reasons.

    Pass acct_no or client_acct_id and any desired optional fields identified here into the get_acct_plan_queued_changes_m API to obtain the custom rate details. The details will be provided in the new queued_plan_custom_rates output array.

*The anniversary date assignment applies to a future plan change set up by:

  1. scheduling a plan subscription to go into effect on the customer's anniversary date using assignment_directive=1 or master_plan_assign_directive=1 in an API that supports either of those fields (examples: assign_acct_plan_m or update_acct_complete_m); or
  2. adding a subscription to a plan scheduled to roll over to another plan on the customer's anniversary date.

You can also use the Aria application to assign custom rates to a future plan.


New Output Parameters Introduced for Data-Type Consistency (DEV-9042)

Several APIs have been updated with new output parameters to correct inconsistencies in data types returned depending on the API call method. These are new versions of previously existing fields; changes are listed below.

API Name Deprecated Parameter New Parameter New Param Type
create_acct_billing_group_m stmt_contact_no, billing_group_no stmt_contact_no_2, billing_group_no_2 number
create_cm_m client_cm_seq_id client_cm_seq_id_2 string
create_order_m invoicing_error_code invoicing_error_code_2 number
create_order_with_plan_m invoicing_error_code, total_charges_before_tax,total_tax_charges,
total_charges_after_tax,total_credit
invoicing_error_code_2, total_charges_before_tax_2, total_tax_charges_2,
total_charges_after_tax_2, total_credit_2
number
get_acct_contacts_m address_verification_cd, bill_address_verification_cd, stat_address_verification_code address_verification_cd_2, bill_address_verification_cd_2,
stat_address_verification_cd_2
string
get_acct_coupon_details_m acct_locale_no acct_locale_no_2 number
get_acct_details_all_m address_verification_cd address_verification_cd_2 string
get_acct_details_all_m acct_no, acct_locale_no, acct_contact_no, legal_entity_no acct_no_2,acct_locale_no_2, acct_contact_no_2, legal_entity_no_2 number
get_acct_hierarchy_details_m acct_locale_no, legal_entity_no acct_locale_no_2, legal_entity_no_2 number
get_acct_message_size_m num_chars num_chars_2 number
get_acct_plan_history_m acct_locale_no acct_locale_no_2 number
get_acct_plan_queued_changes_m current_plan_inst_status, target_plan_inst_status current_plan_inst_status_2, target_plan_inst_status_2 number
get_acct_plan_unit_instance_all_m acct_no acct_no_2 number
get_acct_plans_all_m acct_locale_no acct_locale_no_2 number
get_acct_plans_m acct_locale_no acct_locale_no_2 number
get_acct_service_outage_credit_m acct_locale_no acct_locale_no_2 number
get_acct_surcharges_m acct_locale_no acct_locale_no_2 number
get_acct_universal_contract_m status_code status_code_2 number
get_all_acct_contracts_m acct_locale_no acct_locale_no_2 number
get_avail_plans_for_acct_m acct_locale_no acct_locale_no_2 number
get_cm_details_m orig_invoice_no, reason_code orig_invoice_no_2, reason_code_2 number
get_cm_list_m cm_reason_code cm_reason_code_2 number
get_credit_details_m out_acct_no, out_master_plan_instance_no, acct_locale_no out_acct_no_2, out_master_plan_instance_no_2, acct_locale_no_2 number
get_instance_contract_m length_months, type_no,acct_locale_no, status_code length_months_2, type_no_2,acct_locale_no_2, status_code_2 number
get_invoice_details_m is_pending_ind, billing_group_no, acct_locale_no is_pending_ind_2, billing_group_no_2, acct_locale_no_2 number
get_order_m plan_instance_no plan_instance_no_2 number
get_queued_acct_plans_m acct_locale_no acct_locale_no_2 number
get_recurring_credit_info_m out_acct_no, recurring_credit_no out_acct_no_2, recurring_credit_no_2 number
get_refund_details_m refund_transaction_id refund_transaction_id_2 number
get_unapplied_service_credits_m credit_id credit_id_2 number
issue_refund_to_acct_m out_transaction_id out_transaction_id_2 number
refresh_token_from_pmt_processor_m cc_expire_mm, cc_expire_yyyy,persistent_ind, pay_method_type, status cc_expire_mm_2, cc_expire_yyyy_2, persistent_ind_2, pay_method_type_2, status_2 number
reverse_authorized_electronic_payment_m applied_total_reversal_amount applied_total_reversal_amount_2 number
settle_dispute_hold_m rec_no rec_no_2 number
update_acct_billing_group_m billing_group_no, stmt_contact_no billing_group_no_2, stmt_contact_no_2 number
update_acct_complete_m acct_locale_no, acct_contact_no acct_locale_no_2, acct_contact_no_2 number
update_acct_plan_multi_m

bill_contact_details, statement_contact_details, other_contact_details

bill_contact_details_2, statement_contact_details_2, other_contact_details_2 number
update_contact_m contact_no contact_no_2 number
update_order_m invoicing_error_code invoicing_error_code_2 number
update_payment_method_m bill_contact_no bill_contact_no_2 number

3D Secure Authentication Support for Adyen Payment Gateway (DEV-9050)

The following API calls have two additional fields to support 3D Secure Authentication for the Adyen Payment Gateway:

The two new fields are:

<attempt_3d_secure>: This input field will manually trigger a 3DSecure check if the payment gateway/payment processor supports this feature. A "null" value allows the processor/gateway to dynamically decide whether 3DS is required based on rules configured for that processor/gateway. A "true" directive causes a 3DS authentication attempt; a "false" directive skips the 3DS authentication.

<proc_md>: This output field represents the payment session identifier returned by the card issuer.

New Fields for authorize_3dsecure_m

New Fields for authorize_3dsecure

Additionally, Aria has added the following input fields to the API call authorize_3dsecure_m authorize_3dsecure:

<end_user_ip_address>: The IP address used for placing an online order.

<proc_md>: Payment session identifier returned by the card issuer.
 


Support for Adyen Fraud Tools, RevenueProtect+ (DEV-9051)

Aria has enhanced its integration with the Adyen Payment gateway to support Adyen's RevenueProtect+, a fraud protection mechanism. The API validate_acct_fraud_scoring_m validate_acct_fraud_scoring includes a new input field that provides additional information about an account holder.

<bill_taxpayer_id>: Taxpayer ID of the billing contact.


Delete a Customer's Personal Data (DEV-9077)

The new API named delete_acct_data_m allows you to delete (anonymize) a customer's personal data in compliance with the General Data Protection Regulation (GDPR). When you call this API, personally identifiable account information such as a name, user ID, and location data will be hidden in the Aria application as shown here.

 

Notes:

  • The changes made by the delete_acct_data_m API are irreversible so, before calling this API, it is highly recommended that you:
    • Record the customer's consent/confirmation; and
    • Address any open charges, credits, unbilled usage, etc. with the customer.
  • If you anonymize a parent account, the child account is not anonymized and vice versa.

auth_key Not Included in Event Notifications by Default (DEV-9087)

  • For security reasons, you may decide to exclude your authorization key (auth_key) from your event notification messages. By default, the Include auth_key in Event Payload parameter is now set to False. This means that your auth_key will be excluded from your event notification messages.
  • If you already selected a value for this parameter, it will not change and the parameter will remain set to your chosen value.
  • If you did not already select a value for this parameter, it will be set to True for backwards compatibility.

To change your setting for the Include auth_key in Event Payload parameter, in the Aria application:

  1. Click Configuration > Notifications > Notification Settings > Include auth_key in Event Payload.
  2. Select your chosen Value.
  3. Click Save.

API Fixes 

  • You can now pass a valid date without a time into date fields in the following APIs: get_coupon_history_m, get_all_invoice_information_m, and get_invoice_history_m. When you do that, an error no longer occurs and the data matching your query is returned. (TICKET-8308)
  • XML Exception error: Unexpected element: CDATA was being displayed in authorize_electronic_payment_m API response instead of in the correct XML format (TICKET-16091)
  • $0 refund line items are no longer displayed on an invoice when you issue a full or partial refund that applies to an invoice:
    • With multiple charges; and
    • With or without service credits included.
      (TICKET-16671)
  • Plan unit instances are now successfully removed when plan instance units is downgraded via the update_acct_plan_multi_m API. (TICKET-16678)
  • You can now successfully create a surcharge having multiple rates schedules and rate tiers using create_surcharge_m. (TICKET-16685)
  • You no longer encounter an error when you call the validate_payment_information_m API and you pass in a cvv (card verification value) that is less than 3 characters long. This is because that field is now formatted correctly. When the payment method is American Express, Aria now adds zeros to the cvv to make the field 4 characters long. When the payment method is not American Express, Aria now adds zeros to the cvv to make the field 3 characters long. These changes apply to the following payment gateways:
    • Adyen     
    • BrainTree
    • Chase Paymentech
    • Merchant e-Solutions
    • First Data Payeezy
    • Paymetric
    • PayPal PayFlow Pro
    • First Data PayPoint
    • TNS

For supported payment gateways not listed above, the cvv field was already formatted correctly. (TICKET-16744)

  • API Live no longer prevents users from entering values in certain fields due to incorrect pick lists in some APIs. (TICKET-16746)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

US https://secure.ariasystems.net/api/AriaQuery/wsdl/19/integration_services_m-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/AriaQuery/wsdl/19/integration_services_m-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/AriaQuery/wsdl/19/integration_services_m-doc_literal_wrapped.wsdl
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.