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



 

Home > Aria Crescendo Documentation > Aria Crescendo Release Notes > Release 21

Release 21

This article applies to:Aria Crescendo

Application Features 

Support for Dunning on Order Invoices (DEV-9306)

This enhancement adds support for dunning on unpaid order invoices. This feature allows an Aria client to deliver a one-off product (Non-Subscription Offering) to a customer, who uses an electronic or net-terms form of payment. If the customer’s electronic payment fails, or the customer fails to pay by the Net Terms due date, then the client can initiate the dunning process on the customer’s Master Plan Instance that is associated with the order.

To implement this enhancement, two new client parameters have been added:

  • Dun on Orders for Electronic Payment Methods - Honored when electronic collection attempt fails. This setting governs the behavior to employ when generating an order that is not paid (delinquent) and the Payment Method is electronically collected.  The default value of True will cause a delinquent order invoice to result in dunning.  A value of False will cause a delinquent order invoice to not result in dunning.
  • Dun on Orders for Non-Electronic Payment Terms - Honored when the non-electronic payment terms meet the due date. This setting governs the behavior to employ when generating an order that is not paid (delinquent) for Non-Electronic Payment Terms (note that this will also include deprecated Non-Electronic Payment Methods (e.g. Net Terms 30)). The default value of True will cause a delinquent order invoice to result in dunning. A value of False will cause a delinquent order invoice to not result in dunning.

Getting Here: Configuration > Payments > Payment Settings

clipboard_ee388e2dffe93ebc2560fb317f3465a9d.png

Note: For dunning on orders to work for customers using electronic forms of payment, Auto-Void Order on Electronic Collection Failure MUST be set to False and Auto-Collect on Order Invoicing MUST be set to True. Immediate dunning for orders for customers using electronic forms of payment is NOT currently supported. Instead, the dunning process is triggered as part of the nightly batch process. 

The following inputs have also been deprecated from the following API's: 

Additionally, this ticket introduces several feature enhancements which support the dunning process.

Getting Here: Configuration > Payments > Dunning Processes > New

Dunning Process - Screen 1.jpg

Dunning Process - Screen 2.jpg

  1. Type in a Process Name.
  2. Type in a Client Defined Identifier.
  3. Type in a Description.
  4. Click (or CTRL-Click) to select Payment Types  (Electronic and/or Net Terms forms of payment).
  5. Type in a Plan Number, Name, Client Defined Identifier, or use the Browse button to select plans. Click on the red X to remove plans as needed.

Note: Use the yellow highlighted screen tips area for the allowable combinations of Payment Types, and/or Plans.

  1. Click on the Add Assignment button.

Dunning Process - Screen 3.jpg

  1. The Payment Types and Plans selected for the Dunning Process are displayed.

Note: If no payment types are selected and the Add Assignment button is clicked, the system will default to selecting All Payment Types.

  1. Configure Dunning Steps by selecting dunning email templates using the drop-down arrow, step duration, email contact, and any dunning fees for a step.
  2. Click on the Add Step button to add additional steps to the dunning process.
  3. Click on the Save button to save the dunning process.

Note: You cannot have two dunning processes that use the same combination of Payment Types and/or Plans. An error will display if the same combination of Payment Type and/or Plans are already in use by another Dunning Process.


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 

  • A Supplemental Plan’s next bill date, which has usage services billed semi-annually, is now calculated correctly when assigning both a Master Plan and Supplemental Plan via update_acct_plan_multi_m with an Assignment Directive of 4 (Perform the requested plan change immediately, ignoring the client's pre-configured universal rule for performing or not performing proration and forcing PRORATION. Applicable when plan_directive = 1, 2, 3, 4.) and <combine_invoice> = True. (TICKET-16604)

  • These five fixes have been implemented (TICKET-16668):
    1. When you make changes under Configuration > Security > Account Access > Payments & Credits, the Create a Dispute Hold link now remains visible to authorized users at the Minimum CSR (customer support representative) Level that you specified.
    2. You can now manage authorization to create write-offs using a new link called Create a New Write-off, which you can access under Configuration > Security > Account Access > Payments & Credits.
    3. The Lock/Unlock Account feature has been discontinued and its link is no longer visible under:
      • Configuration > Security > Account Access > Account Overview; and
      • Accounts > select an account > Account Security.

        This means that now you do not see the "mod_plsql" error message which previously appeared when you clicked on the Lock/Unlock Account link. You can use the Reset (Assign System-Generated) Password link under (Accounts > select an account > Account Security) to lock/unlock an account instead. 
    4. The Make Payment button (under Accounts > select an account > Plans > select a plan), is no longer visible to unauthorized users who do not have access to the Apply a Payment or Unapply a Payment link. Access to the Make Payment button is now limited to users at the Minimum CSR Level that you specified (under Configuration > Security > Account Access).
    5. As expected, the confirmation message correctly displays "&" instead of "&amp;" when you save your changes made under Configuration > Security > Account Access.
  • Event notifications are no longer sent for your inactive event groups (under Configuration > Notifications > Events). (TICKET-16738)
  • A Data Table warning error is no longer thrown ​when accessing an account's plan(s) (including suspended) service rates via the > Accounts > Account Overview > Plans > All Service Rates tabs. (TICKET-16787)
  • Aria no longer displays the unwanted string "&nbsp;" in the Aria user interface under Account Overview > Recent Payments > Source column. (TICKET-17166)
  • Your users at the View-only CSR (customer service representative) access 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 

XML Changes for get_rate_schedules_for_plan_m (DEV-7478)

The get_rate_schedules_for_plan_m API's output has been changed to XML format to facilitate better performance. There are no changes to the existing output of fields for this API. (DEV-7478)


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_m) 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_m) 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_m) 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 ccreate_order_m API.

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



Maximum Length Validation Updated for delete_acct_data_m (DEV-9418)

When you call the delete_acct_data_m API, these fields are now validated for compliance with the maximum allowed length rules: <client_acct_id> and <userid>. If you pass in a value that is above the maximum allowed length, the API will now return this error: "1016 invalid input".


API Fixes 

  • Aria now validates the API fields <country_cd> and <state_prov> in API calls update_acct_complete_m, create_acct_complete_m, update_acct_billing_group_m, create_order_m, and create_order_with_plan_m. Now, if invalid values are passed in these fields, Aria returns an error message. (TICKET-13724)
  • All the Master Plan Instances associated with a statement are now being returned in the <statement_master_plan_instances> row when calling get_acct_statement_history_m. (TICKET-15274)
  • XML Exception error: Unexpected element: CDATA was being displayed in authorize_electronic_payment_m API response instead of in the correct XML format (TICKET-16091)
  • The following fixes regarding get_refund_details_m have been implemented (TICKET-16236):
    • When passing Aria6 <client_no>, and <auth_key> input parameters to an Aria Crescendo client, the system no longer throws a “Missing required parameters”. Now, if Aria 6 credentials are passed as an input, the API returns error code "26003" and the following error message: "The API execution is not supported because your client parameter Account_EOM_Enabled is set to False. Please contact Aria customer support with questions about the Account_EOM_Enabled client parameter". 
    • The issue where passing invalid <aria_event_no> in get_refund_details_m returned 0 and OK has been corrected.  The API now returns error code "2001" and the error message "transaction does not exist".
    • The issue causing missing fields in get_refund_details_m when reversing multiple line items in a single call using issue_refund_to_acct_m  (remember to link to API)  has been correctedThe API now returns <service_no> and <client_service_id> for all invoice line items instead of only for the recurring service. The <reversed_line_start_date> and <reversed_line_end_date> are only returned for "recurring" service and not for the order service. The <bill_email> is only returned if the payment method is "11" (ie. PayPal Express Checkout).
  • Aria now returns the output field <service_code_to_use> for API call get_discount_rule_details_m. (TICKET-17071)
  • These two fixes/changes have been implemented (TICKET-17157):
    1. An error no longer occurs when you call the create_acct_complete_m API and:
      • pass in custom rates, a future <alt_start_date>, an <override_bill_thru_date> or <status_until_alt_start_date>; and
      • set the <invoicing_option> field to 2 (prorated invoice).
    2. If you try to create an account or assign a plan with a non-provisioned status (status other than active) and assign custom rates without specifying an <alt_start_date>, this new error is now returned by the APIs listed below: "14132 Custom rates cannot be assigned for this non-provisioned status":
  • get_refund_details_m now returns tax line items in the <invoice_reversals> output array when the invoice(s) being reversed have a coupon applied. (TICKET-17289)
  • When you call the get_discount_rule_details_m API, any available <service_code_to_use> is returned, as expected. (TICKET-17291)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

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

Tags

This page has no custom tags.

Classifications

This page has no classifications.