Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 21

Aria6 Release 21

Overview

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

Release Date

Stage Future Release Date

4-April-2019

Production Release Date

25-April-2019

System Requirements

Supported Browsers

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

Screen Resolution

1024 x 768 or higher

Release 21 Contents

Application Features 

Improvements to Collection Groups Page Navigation and Loading Speed (DEV-9412)

This enhancement provides increased system speed when navigating to and loading the Configuration > Payments > Collection Groups page via the Aria UI.

Application Fixes 

  • Aria no longer displays the unwanted string " " in the Aria user interface under Account Overview > Recent Payments > Source column. (TICKET-17166)
  • Event 103 "Billing contact modification" is now successfully created and transmitted only when the billing contact information is modified via the UI or API. (TICKET-17169)
  • Your users at the View-only CSR (customer service representative) level cannot run/schedule reports, as expected. Access to reports functionality is now restricted to the user levels that you specified under Configuration > Security > Account Access. (TICKET-17331)

API Features 

CIT and MIT Support For Braintree Payment Processor Transactions (DEV-9313)

This feature enhances Aria's Braintree payment processor integration by sending flags distinguishing Cardholder Initiated Transactions (CIT) and Merchant Initiated Transactions (MIT) for Visa and MasterCard credit cards, to comply with Visa's Payment Card Industry Data Security Standards (PCI DSS).

The existing input field <recurring_processing_model_ind> and output field <proc_initial_auth_txn_id> support this feature in the following APIs: APIs:

  • assign_acct_plan_m
  • authorize_electronic_payment_m
  • cancel_acct_plan_m
  • collect_from_account_m
  • create_acct_billing_group_m
  • create_acct_complete_m
  • create_order_m 
  • create_order_with_plan_m
  • manage_pending_invoice_m
  • replace_acct_plan_m
  • settle_account_balance_m
  • update_acct_billing_group_m
  • update_acct_complete_m
  • update_acct_plan_m
  • update_acct_plan_multi_m
  • update_payment_method_m
  • validate_acct_fraud_scoring_m
Learn more about this feature.
  • assign_acct_plan
  • authorize_electronic_payment
  • cancel_acct_plan
  • collect_from_account
  • create_acct_billing_group
  • create_acct_complete
  • create_order
  • create_order_with_plan
  • manage_pending_invoice
  • replace_acct_plan
  • settle_account_balance
  • update_acct_billing_group
  • update_acct_complete
  • update_acct_plan
  • update_acct_plan_multi
  • update_payment_method
  • validate_acct_fraud_scoring
Learn more about this feature.

Adyen Integration Enhanced with Support for UnionPay ExpressPay Credit Card (DEV-9316)

If you use Adyen as a payment gateway, you can now accept payments made using the UnionPay ExpressPay credit card. ​

You can specify the authorization options for UnionPay ExpressPay in your collection group settings for Adyen (under Configuration > Payments > Collection Groups > Details > System Overrides).

To process a payment made with UnionPay ExpressPay, pass either of these inputs into the <pay_method_type> field in the API (example: create_acct_complete) that you are using to collect the payment:

  • 1 for credit card; or
  • 13 for tokenized credit card.

WorldPay Integration Enhanced with Support for Elo, Hipercard, and Maestro Credit
Cards (DEV-9317)

If you use WorldPay as a payment gateway, you can now accept payments made using these credit cards: Elo, Hipercard, and ​​International Maestro (also referred to as "​Maestro"). ​

You can specify the authorization options for those credit cards in your collection group settings for WorldPay (under Configuration > Payments > Collection Groups > Details > System Overrides).

To process a payment made with any of those credit cards, pass either of these inputs into the <pay_method_type> field in the API (example: create_acct_complete) that you are using to collect the payment:

  • 1 for credit card; or
  • 13 for tokenized credit card (currently supported only for Maestro).

Ingenico Integration Enhanced with Support for Elo, Hipercard, and Maestro Credit Cards (DEV-9318)

If you use I​ngenico as a payment gateway, you can now accept payments made using these credit cards: Elo, Hipercard, and ​​International Maestro (also referred to as "​Maestro"). ​ ​

You can specify the authorization options for those credit cards in your collection group settings for I​ngenico (under Configuration > Payments > Collection Groups > Details > System Overrides).

To process a payment made with any of those credit cards, pass either of these inputs into the <pay_method_type> field in the API (example: create_acct_complete) that you are using to collect the payment:

  • 1 for credit card; or
  • 13 for tokenized credit card.

 

Note: Aria does not store the CVV (Card Verification Value) for PCI (Payment Card Industry) compliance. However, in Ingenico's test environment, for Elo credit cards, each subsequent purchase does require a CVV. This means that if you are connecting to Ingenico's test environment end point/services, and a use case involves an existing customer who is paying for new orders or recurring subscriptions using Elo, you will need to pass in a CVV to process the payment.

Example: Pass the CVV into the <existing_pay_method_cvv> field in the create_order API.

The above does not apply to Ingenico's production environment.

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

US https://secure.ariasystems.net/api/AriaQuery/wsdl/21/integration_services-doc_literal_wrapped.wsdl
EUR https://secure.prod.cph.ariasystems.net/api/AriaQuery/wsdl/21/integration_services-doc_literal_wrapped.wsdl
AUS https://secure.prod.aus.ariasystems.net/api/AriaQuery/wsdl/21/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 ®