Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 6.45

Aria6 Release 6.45

Application Features

NetSuite Authentication Update (DEV-6076)

This feature implements NetSuite OAuth authentication in place of username/password when programmatically connecting to Netsuite. NetSuite authenticates Aria by using an OAuth with a pre-configured token key and token secret, and with customer key and customer secret.

Enable Token-based Authentication in NetSuite 

  1. In NetSuite, go to Setup > Company > Enable Features (SuiteCloud tab).
  2. Check Token-based Authentication. 

Obtain the Token Key and Token Secret

  1. In NetSuite, go to Setup > Integrations > Manage Integrations > New. 
  2. Check Token-Based Authentication. 
  3. Click Save. A token key and token secret display.
  4. Record the token key and token secret.

Configure OAuth in Aria

Getting Here: Click Configuration > Integrations > External Service > New

netsuite.png

  1. Enter the contact Email Address for NetSuite Connector-related communication.
  2. Enter the External URL provided by NetSuite.
  3. Enter the Account ID.
  4. Enter the Access Token ID and Access Token Secret.  
  5. Click Save. 

Two-way SSL Support for PHP and Ruby SDKs (DEV-6145)

This feature updates the PHP and Ruby SDKs to support two-way SSL authentication.

SEPA Direct Debit Support to Chase Paymentech Integration (DEV-6209)

This feature supports SEPA Direct Debit as a payment method to our current Chase Paymentech integration. SEPA supports the International Bank Account Number (IBAN) and Bank Identifier Code (BIC) structure. 

For more information about adding a payment gateway, refer to Processing Payments.

Support for Boleto Bancario (Brazil) Through Global Collect Integration (DEV-6210)

This features supports Boleto Bancario (Brazil) as a payment method as part of the Global Collect integration. This integration only supports one-time payments, and not recurring payments.

Note: These payments are not authorized immediately, and can take many days to be processed. Funds are transferred into the Aria client account depending on the payment processing policies of the third-party payment provider.

For more information about adding a payment gateway, refer to Processing Payments.

Support for Adyen as Payment Processor (DEV-6214)

This features integrates Adyen as a payment processor within Aria and supports the following:

Processes
  • Authorization
  • Capture
  • Authorization with capture
  • Account verification ($0 authorization)
Payment Methods and 
Card Types
  • Visa
  • MasterCard
  • American Express
  • Discover
  • JCB
  • Maestro (for one time payments only)
  • SEPA Direct Debit
  • iDeal
  • Boleto Bancario (Brazil)
Currencies
  • US Dollar
  • Canadian Dollar
  • Euro
  • British Pound
  • Brazilian Real
  • Australian Dollar
Additional Support
  • Tokenized Credit Cards
  • Account Updater (Visa & MasterCard only – not all European countries supported)

Add Adyen as Payment Processor

Consult with your Adyen Account Representative for the appropriate credentials and settings for your business. You will need the information captured below.

Getting Here: Click Configuration > Payments > Payment Gateway > Select Adyen from the drop-down

Adyen Payment.png

  1. Complete the above fields with the information provided by your Adyen representative. 
  2. Configure updates via Secure FTP (SFTP) from the Adyen options, if desired. 

​Options.png

  1. Select the errors for specific Card Verification Value (CVV) response codes. Note that you may need to contact the payment processor directly to ensure they are configured to not reject the result.
  2. Click Save.

Boleto Pay Method As External Payment (DEV-6762)

This feature updates the Boleto pay method from an electronic payment to an external payment.  

Application Fixes

  • Tax configuration was not displayed in destination client user interface after data import from the source client (TICKET-5393)
  • Unable to remove the 'credit template' from the coupon after opening the new credit template creation page (TICKET-10590)
  • Multiple issues in 'create notification template group' page (TICKET-10782)
  • Issue with pagination in configuration CSR activity search results page (TICKET-10798)
  • Usage rates were not calculated (TICKET-10843)
  • Provisioning daemon attempted to process clients regardless of 'active clients' status (TICKET-10878)
  • Not all supplemental plans were accessible accessible through user interface  (TICKET-11219)
  • Data tables error occurred when searching with date field in audit logs (TICKET-10901)
  • Issues with Starting Sequence Number field when creating functional account group (TICKET-10601)
  • Account CSR Activity tab was showing unexpected error (TICKET-11150)
  • Supplemental Plan was not billed in second invoice (TICKET-11153)
  • Refund Description - Tax Credit was Missing from description (TICKET-11252)
  • Old Aria Logo Appearing on Workflow Documentation site (TICKET-11374)
  • Javascript error from Direct Post (TICKET-11412)     

API Features

SEPA Direct Debit Support to Chase Paymentech Integration (DEV-6209)

This feature supports SEPA Direct Debit as a payment method to our current Chase Paymentech integration. SEPA supports the International Bank Account Number (IBAN) and Bank Identifier Code (BIC) structure.  

The following APIs are to be used to map to Chase SEPA Direct Debit parameters:

Aria Parameter Chase SEPA DD Parameter
bank_acct_no  Account Number
bank_country_cd Country Code
bank_id_cd Bank Sort Code
bank_check_digit RIB code
bank_branch_cd Bank Branch Code
mandate_id Mandate ID
iban IBAN
bank_swift_code BIC

Support for Boleto Bancario (Brazil) through Global Collect Integration (DEV-6210)

This features introduces the core API record_alternative_payment to support Boleto Bancario as a payment method as part of the Global Collect integration. This integration only supports one-time payments, and not recurring payments.

Note: These payments are not authorized immediately, and can take many days to be processed. Funds are transferred into the Aria client account depending on the payment processing policies of the third-party payment provider.

prov_push_invs Lock to Prevent Multiple Instances (DEV-6753)

The feature implements per-client lock for client-specific invoice paid event daemon. 

API Fixes

  • cop_acct_payment_method failed with parent/child relationship (TICKET-10861)
  • "Tax group cannot be blank" error when updating a service via API (TICKET-11237)
  • Definitions added for  alt_caller_id and optional_transaction_parameters (TICKET-11339)
  • Setting alt_bill_day to tomorrow does not apply correct supplemental plan dates (TICKET-11297)
  • Remove query logging from get_account_details object API (TICKET-11480)
  • Improve check_first_unit_instance_bill function in plan manager package (TICKET-11536)
  • Error message got displayed in edit_plan when passing the child plan in request (TICKET-11653)       
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
Powered by CXone Expert ®