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



 

Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 19

Aria6 Release 19


Application Features

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)
  • $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

get_reversible_invs_by_payment API Performance Improvement (DEV-9037)

The response time of the get_reversible_invs_by_payment API has been improved, even for calls that return a high number of invoice line items.


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 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 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.

API Fixes

  • You can now pass a valid date without a time into date fields in the get_coupon_history API. When you do that, an error no longer occurs and the data matching your query is returned. (TICKET-8308)
  • You cannot use the edit_plan API to change the billing interval of an active plan, as expected. (TICKET-16600)
  • If, on a non-anniversary date, you assign an account a supplemental plan set up to roll over to a new plan, the new plan is now made active on the anniversary date when you:
    • Set your Supp plan rollover date option parameter to 0 (Assign the rollover plan on anniversary date); and
    • Use any of these APIs:
      • create_acct_complete
      • assign_supp_plan
      • create_order_with_plans
      • assign_supp_plan_multi.

        (TICKET-16660)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

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

Tags

This page has no custom tags.

Classifications

This page has no classifications.