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



 

Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 24

Aria6 Release 24


Application Features

Identify Transaction Type in Payment Transactions (DEV-9576)

If you use Chase Paymentech, you can now tell that payment gateway which transaction type is involved (examples: single or recurring transaction) when you process a customer's payment information. To do so, select a Transaction Type when you create a Direct Post configuration set.

You can also use APIs to specify the transaction type.


Voided/Out-Of-Band Electronic Credit Transaction Deprecated (DEV-9619)

The "out-of-band electronic credit" and "voided out-of-band electronic credit" transaction types are no longer in use and have been deprecated in any locations where one or both of them were previously available on the following screens in the Aria application:​

  • Configuration > Notifications > Events > Financial Transactions;
  • Configuration > Notifications > Statement Sending > Selected Transaction Typ​es
  • Configuration > GL Code Mappings > Transaction Types > New;
  • Configuration > Client Settings > Locale Settings > New.

Braintree Payment Processor Support for 3D Secure 1.0 (DEV-9676)

This feature enhances Aria's integration with the Braintree Payment Processor Braintree Payment Processor by adding support for 3D Secure 1.03D Secure 1.0.

3D Secure is a XMLprotocol that provides an additional security layer for online card transactions.


Application Fixes 

  • An error no longer occurs when you remove the activation fee while rebilling an invoice. (TICKET-15751)
  • An empty “Plan Details Modified” event payload (Event ID–614), if configured in the Products Event Group, is no longer triggered when a Plan is deleted from the Product Catalog. This is also applicable to the deletion of other Product Catalog objects including Services, Usage Types, and Non-Subscription Offerings. The following Product Event Group’s modify events, if configured, are no longer triggered when a Plan, Service, Usage Type, or Non-Subscription Offering is deleted from the Product Catalog: (TICKET-17463)

Event Name Event ID Description
Plan Details Modified 614 Existing Plan Details Modified
Service Modified 609 Existing Service is Modified
Usage Type Modified 612 Existing Usage Type is Modified
Non-subscription Offering Details Modified 618 Existing Non-subscription Offering Details is Modified

API Features 

Ability to Issue Concurrent Refunds for Different Open Payments (DEV-9536)

This feature allows concurrent calls to the API issue_refund_to_acct. Now, simultaneous refunds and reversals successfully complete for multiple open payments related to a single account. Previously, an internal database lock prevented completion of simultaneous calls for a single account. 


Identify Transaction Type in Payment Transactions (DEV-9576)

If you use Chase Paymentech, you can now tell that payment gateway which transaction type is involved (examples: single or recurring transaction) when you process a customer's payment information. To do so:

  • Pass the relevant transaction type into a new input array called <proc_field_override> in any of these APIs: create_acct_complete, create_acct_hierarchy, create_order, create_order_with_plans, manage_pending_invoice, modify_supp_plan, replace_supp_plan, settle_acct_balance, update_acct_complete, update_payment_method, validate_acct_fraud_scoring, and validate_payment_information; or
  • When you call the set_reg_uss_config_params API to create a Direct Post configuration, pass the relevant <transaction_type> into the <in_reg_uss_config_params> array.

    You can also use the Aria application to specify the transaction type when you create a Direct Post configuration.

Note: The transaction type that you pass into an API will override the default transaction type that you specified in your configuration settings for Chase Paymentech.

Please see the API documentation for more information.


Identify Cardholder Initiated and Merchant Initiated Transactions with Chase Paymentech (DEV-9578)

Aria's ​Chase Paymentech integration has been enhanced with support for the Cardholder Initiated Transaction​ (CIT)/Merchant Initiated Transaction (MIT) feature for the Mastercard and Discover credit cards. CIT/MIT support for Visa was introduced in Release 17 (8/16/2018). This feature applies to the credit card and tokenized credit ca​rd payment methods. If you use Chase Paymentech as your payment gateway and process a Mastercard or Discover payment, you can now specify whether the transaction was initiated by the cardholder or merchant. To do so, use the pre-existing ​input <recurring_processing_model_ind> and output <proc_initial_auth_txn_id> in these APIs:


Voided/Out-Of-Band Electronic Credit Transaction Deprecated (DEV-9619)

The "out-of-band electronic credit" and "voided out-of-band electronic credit" transaction types are no longer in use and have been deprecated as described below:

  • The allowable values "out-of-band electronic credit" (7) and  "voided out-of-band electronic credit" (-7) for the <transaction_type> field have been deprecated in these APIs that previously included that field as an input and/or output:
  • You can no longer subscribe to the "out-of-band electronic credit created" event (ID 313) or "out-of-band electronic credit voided" event (ID 314) using the <event_list> field in the subscribe_events API.
  • The list_transaction_types API no longer return the "out-of-band electronic credit" (7) and "voided out-of-band electronic credit" (-7) transaction types.

Object Query APIs list_payment_methods(_m) No Longer Return the “Click&Buy” and “PayByCash” Payment Methods (DEV-9624)

The object query APIs list_payment_methods_m and list_payment_methods ​no longer return the disabled Click&Buy and PayByCash​​ payment methods.​  Aditionally, ​those payment methods are no longer available for selection on the "​Create New Payment Method" screen in the Aria user interface. ​​With the introduction of the new 'disabled_ind' column, the screen  has been adjusted to display the records with "no_display_ind = 0 AND disabled_ind = 0".

clipboard_eb159e08e5b2933f089a0d679a6537958.png


Braintree Payment Processor Support for 3D Secure 1.0 (DEV-9676)

This feature enhances Aria's integration with the Braintree Payment Processor Braintree Payment Processor by adding support for 3D Secure 1.03D Secure 1.0.

To invoke 3D Secure authentication for payments:

  1. call the payment API authorize_electronic_payment_m authorize_electronic_payment or update_payment_method_m update_payment_method with the field <attempt_3d_secure> set to "true";
  2. pass the values of <client_auth_token> and <cc_single_use_token> values returned by the API call in step 1 to your custom Direct Post payment page; and
  3. pass the value of <client_3ds_nonce> returned by your payment page in a call to API authorize_3dsecure_m. authorize_3dsecure.

New Inputs For API Calls

API Call

New Input Fields

authorize_3dsecure

<proc_field_override>: Array of processor-specific fields.

  • <proc_field_name>: The name of the processor-specific field.
  • <proc_field_value>: The value associated with the proc_field_name.

API Call

New Input Fields

authorize_3dsecure_m

<proc_field_override>: Array of processor-specific fields.

  • <proc_field_name>: The name of the processor-specific field.
  • <proc_field_value>: The value associated with the proc_field_name.

New Outputs For API Calls

API Call

New Output Fields

<proc_3dsecure_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.

<proc_3dsecure_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.

authorize_3dsecure <processor_id>: The Payment Processor ID used for external collection or authorization.

API Call

New Output Fields

<proc_3dsecure_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.

<proc_3dsecure_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.

<proc_3dsecure_auth_data>: Array of 3D Secure processor-specific fields required for client-side integration.

  • <proc_3ds_field_name>: Processor-specific field name.
  • <proc_3ds_field_value>: Processor-specific field value.

<processor_id>: The Payment Processor ID used for external collection or authorization.

authorize_3dsecure_m <processor_id>: The Payment Processor ID used for external collection or authorization.

API Fixes 

  • If you use Chase Paymentech as your payment gateway, you no longer get an error when you complete a credit card authorization reversal. (TICKET-17510)
  • The API call get_invoice_information now returns the correct value for <aria_event_no>, a unique value associated with an Aria transaction, allowing additional lookups for transactions associated with a specified invoice. (TICKET-17536)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

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

Tags

This page has no custom tags.

Classifications

This page has no classifications.