Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 15.0

Aria6 Release 15.0

Overview

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

Release Date

Stage Future Release Date

 3-May-2018

System Requirements

Supported Browsers

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

Screen Resolution

1024 x 768 or higher

Application 

Features

Fixes

List of Application Fixes

API

Features

Fixes

List of API Fixes

Application Features 

Service Period and Plan Type Identified in Rebill Statement Template (DEV-8587)

The rebill statement template can now include the service start date and service end date. In addition, the template can now identify whether a line item applies to a master plan or supplemental plan so that the applicable data for each plan can be displayed or hidden in the rebill statement. Please contact Aria Customer Support if you want to include any of this new information in your rebill statement template.

Collection Amounts in JPY or INR Sent to Vantiv Correctly (DEV-8620)

If you use Vantiv as your payment gateway and you attempt to collect a payment in JPY (Japanese yen) or INR (Indian rupee), the correct amount is now requested. No decimal point is added to the payment amount. Example: if you attempt to collect 1600 JPY, now 1600 JPY is collected instead of 160000 JPY.

Vantiv (Litle) Fraud Integration (DEV-8698)

Vantiv (Litle) has partnered with ThreatMetrix to further assist you with limiting fraudulent transactions. If you use Vantiv (Litle) as your payment gateway in Aria, you now have access to fraud scoring settings. Fraud scoring applies to card, direct debit, electronic check, and tokenized card payment methods.

To use these fraud protection features, you must first enable and configure them within Vantiv. You can then update your Vantiv Payment Gateway settings in Aria.

Setting Up Fraud Options In Aria For Your Vantiv (Litle) Payment Gateway

Getting here: Configuration > Payments > Payment Gateways > Vantiv (Litle)

  1. If you have not yet configured your Vantiv (Litle) payment gateway, 
  2. Configure the fraud fields as desired. On the Processor Details tab, add the ThreatMetrix Prefix provided to you by Vantiv when you enabled Fraud Scoring:

    gateway_processor_details.png
     
  3. On the Gateway Options tab, update the Fraud Options fields as desired: 

    gateway_options.png

    Send Fraud Scoring Request: When enabled, Aria will send a request for a fraud score to Vantiv (Litle).

    Change Status on Fraud Scoring Failure: When set to true, Aria will update the status of the if the fraud score is below the threshold, or if the Fraud Score response is unsuccessful, to the status chosen for Status on Fraud Scoring Failure.

    Status on Fraud Scoring Failure: Choose a status from this list of Statuses.

    Change Status on Fraud Scoring Review: When set to true, Aria will update the status of the if the fraud score is "Review," the status chosen for Status on Fraud Scoring Review.

    Status on Fraud Scoring Review: Choose a status from this list of Statuses.

 

Note: If you are using Direct Post and you are running a $0 authorization, then Aria will skip any steps in your configuration that involve fraud scoring.

Support for Vantiv Insights Marketing Tools (DEV-8699)

This feature adds Aria support for Vantiv Insights, which provides additional information to merchants to improve authorization approval rates and lower the total cost of payments. This additional information falls into four categories: Prepaid Indicator, Affluence Indicator, Issuer Country Indicator, and Card Type Indicator.

To use Vantiv Insights, you must have a pre-existing relationship with the Vantiv payment gateway, with Insights configured within your Vantiv instance; and, you must enable this feature in Aria.

Add Vantiv (Litle) Payment Gateway

Getting here: Configuration > Payments > Payment Gateways

  1. Click the New button
  2. Select Vantiv (Litle)
  3. Complete
  4. Enable Vantiv Insights via the new configuration field, Vantiv Insights:

    vantiv_gateway_enable_insights.png

    Enabled: New Insights data points can be viewed within the Aria Account Overview for customers whose payments will be collected via the Vantiv payment gateway, and Insights data can be retrieved via supported API calls and Direct Post.

    Disabled: Insights data will not be retrieved.
Configuring Vantiv Insights Via a Collection Group

Getting here: Configuration > Payments > Collection Groups

  1. Click the New button.
  2. Configure a
  3. Select a value from the Insight Options drop-down menu:

    vantiv_collgroup_enable_insights.png

    Use Payment Gateway Setting: Aria will follow the directive that is configured for your Vantiv (Litle) Payment Gateway.

    Enabled: Regardless of whether Vantiv Insights is enabled in your Vantiv (Litle) Payment Gateway, API calls that collect payments for accounts associated with this Collection Group will be able to retrieve Vantiv Insights data.

    Disabled: Regardless of whether Vantiv Insights is enabled in your Vantiv (Litle) Payment Gateway, no Vantiv Insights data will be retrieved via API calls.
Viewing an Account's Insights Data in the Aria UI

When an account is associated with the Vantiv (Litle) payment gateway and Insights is enabled, this icon will appear when viewing an account's card (credit card, tokenized credit card, or pre-paid card) payment method within the Payment Methods tab of the Account Overview:

insights_pay_method_tab.png

If there are Insights data associated with that card, mousing over this icon will show that data:

insights_sample.png

If there are no Insights data available, mousing over this icon will cause a message to popup, "No card type detail available."

New Payment Method: Merchant Specific Gift Card (DEV-8700)

This feature adds Aria support for a new payment method, "Merchant Specific Gift Card," for Vantiv clients only. This pay method shares data fields with credit cards, with the additional ability to request the remaining balance via supporting API calls and Direct Post configurations.

To take advantage of this feature, you must first enable this feature on the Vantiv side of your configuration. Once configured in both Vantiv and Aria, Aria sends gift-card-related data to, and receives gift-card-related data from, Vantiv via API calls.

Add Vantiv (Litle) Payment Gateway

Getting here: Configuration > Payments > Payment Gateways

  1. Click the New button
  2. Select Vantiv (Litle)
  3. Complete

Adding "Merchant Specific Gift Card" Pay Method

Getting here: Configuration > Payments > Payment Methods

  1. Click the New button.
  2. Select Merchant Specific Gift Card from the Select a Method drop-down menu.
    new_payment_method_40.png
  3. Complete

Configuring Direct Post Behavior for "Merchant Specific Gift Card"

Getting here: Configuration > Client Settings > USS Reg Configuration

  1. Click the New button.
  3. Choose "True" or "False" for the new field, Perform balance inquiry.
    USS_Reg_balance_inq.png
    True: The return from a Direct Post call will include the remaining balance for Pre-paid/Gift cards.
    False: The return from a Direct Post call will not include the remaining balance for Pre-paid/Gift cards.

Specifying "Merchant Specific Gift Card" as an Account's Pay Method

You can specify "Merchant Specific Gift Card" as an account's pay method in the following ways:

  1. Via API calls.
  2. Via the UI, on the Payment Methods tab on the Account Overview of an existing account.
  3. Via the UI, on the Collect Payment Electronically screen.
  4. Via the UI, on the Create New Account screen.

Recurring Flag Sent to Braintree only after Successful Payment ​(DEV-8710​)

Aria now sends the recurring flag (to identify a transaction associated with a subscription billing model) to the Braintree payment gateway only after a successful payment transaction. This is required to comply with Visa and MasterCard's rules that apply to Braintree.

Application Fixes 

  • When you cancel or replace a plan, any prorated credits applied for taxes on the previous plan are now calculated correctly. (TICKET-15919)

API Features 

Vantiv (Litle) Fraud Integration (DEV-8698)

One API was updated to support Vantiv (Litle) Fraud Integration:

API Updates
validate_acct_fraud_scoring
  • Added 6 new input fields:
    session_id: Value used with ThreatMetrix to identify Fraud Scoring Session.
    cust_field_1, cust_field_2, cust_field_3, cust_field_4, cust_field_5: Configurable values to be used with ThreatMetrix.
  • Added 1 new output field:
    proc_faud_score_result: Fraud score response provided by the payment processor. Used when automatically configured at payment processor to return pass, fail, or verify/suspect/unknown.

Vantiv Insights Marketing Tools (DEV-8699)

Several APIs were updated to support requests for card-related marketing information, per the below table:

API Updates
update_payment_method
  • Added new input field perform_marketing_insights_inquiry. Returns marketing information if your payment processor supports it and it is configured in Aria.
  • Added new output fields:
    proc_prepaid_indicator: Additional information passed back from processor identifying this card as a prepaid card (if available).
    proc_prepaid_available_balance: Additional information passed back from processor for available balance on prepaid card (if available).
    proc_prepaid_reloadable: Additional information passed back from processor identifying whether or not the prepaid card is reloadable (if available).
    proc_prepaid_card_type: Additional information passed back from processor to categorize the type of prepaid card (if available).
    Proc_affluence_indicator: Additional information passed back from processor indicating if card is affluent.
    Proc_issuing_country: Additional information passed back from processor indicating issuing country for the card.
    Proc_card_product_type: Additional information passed back from processor indicating whether the submitted card is a commercial or consumer card, providing you with additional data useful when analyzing sales patterns and/or planning marketing campaigns.
authorize_electronic_payment
validate_payment_information 
set_reg_uss_config_params Added new input field perform_marketing_insights_inquiry. Returns marketing information if your payment processor supports it and it is configured in Aria.

Support For New Payment Method: Merchant Specific Gift Card (DEV-8700)

Several APIs were updated to support the new payment method, "Merchant Specific Gift Card" (Pay Method 40), per the below table:

API Updates
create_acct_complete New Allowable Value added for field pay_method: 40 (Merchant Specific Gift Card).
update_acct_complete New Allowable Value added for field pay_method: 40 (Merchant Specific Gift Card).
update_payment_method New Allowable Value added for field pay_method: 40 (Merchant Specific Gift Card). 
authorize_electronic_payment
  • Added new input field perform_balance_inquiry. When supported, this will provide a balance inquiry that reflects the current balance for prepaid cards and gift cards. 
  • Added new output field proc_gift_card_available_balance. This output field indicates the available balance on a gift card if available.
validate_payment_information 
  • Added new input field perform_balance_inquiry. When supported, this will provide a balance inquiry that reflects the current balance for prepaid cards and gift cards. 
  • Added new output field proc_gift_card_available_balance. This output field indicates the available balance on a gift card if available.
set_reg_uss_config_params Added new input field perform_balance_inquiry. When supported, this will provide a balance inquiry that reflects the current balance for prepaid cards and gift cards. 

In addition, the following API calls support the ability to collect against an account's specified alternative payment method, and will honor that directive when "Merchant Specific Gift Card" has been specified as such:

Dynamic Soft Descriptor Field For Non-Credit-Card PayPal Payments (DEV-8728)

This feature enables the following API calls to pass dynamic data in the soft_descriptor field that will be associated with PayPal non-credit-card payment transactions and displayed to customers on their PayPal statements:

  • create_order
  • create_order_with_plans
  • collect_from_account
  • settle_account_balance

Note: This is in addition to the already supported feature when the PayPal Express Checkout end user is using a credit card as their "PayPal Method of Payment" (external/unknown to Aria).

API Fixes 

  • Correct error message is now displayed when passing an invalid surcharge_no in delete_surcharge. (TICKET-15159)
  • The delete_bundle API is now executing as expected when a valid bundle_nos input parameter is passed in the call. (TICKET-15506)
  • A discrepancy has been resolved wherein an input variable passed in update_acct_complete was resulting in inconsistent behavior in the Stage Current, and Stage Future environments. (TICKET-16034)

  • Updated API calls to consolidate arrays and conform to field name standards.

    • For API create_acct_complete:
      Deprecated the array enable_usage_pooling_plan_no. 
      Added the array create_usage_pooling_data, with fields usage_pooling_plan_no, client_usage_pool_plan_id, and usage_threshold_applicability_cd.
    • For API create_acct_hierarchy:
      Deprecated arrays a1_enable_usage_pooling_plan_no, a2_enable_usage_pooling_plan_no, a3_enable_usage_pooling_plan_no, a4_enable_usage_pooling_plan_no, a5_enable_usage_pooling_plan_no.
      Added the array create_usage_pooling_data, with fields usage_pooling_plan_no, client_usage_pool_plan_id, and usage_threshold_applicability_cd.
    • For API update_acct_complete:
      Deprecated arrays enable_usage_pooling_plan_no, disable_usage_pooling_plan_no.
      Added the array update_usage_pooling_data, with fields usage_pooling_plan_no, client_usage_pool_plan_id, usage_pooling_action_directive, and usage_threshold_applicability_cd

    (TICKET-16038)

  • Expected error message "invalid client plan id" is now being returned for create_acct_complete when an invalid client plan id is passed in the client_usage_pool_plan_id input field. (TICKET-16276)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

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

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by CXone Expert ®