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



 

Home > Aria Crescendo Documentation > Aria Crescendo Release Notes > Release 14.1

Release 14.1

This article applies to:Aria Crescendo

Application Features 

Revenue Recognition Enhancement (DEV-7475)

The Revenue Recognition invoice transformation process has been expanded to include invoices when an accounts' billing group's primary payment method is payment terms.

 


Do Not Send Emails' Option As Dunning Final Notification Template (DEV-8043)

This enhancement allows clients to select NOT to send a final notification email template to an account, billing, or statement contact as a final step in a Dunning process.

No Email Option for Final Dunning Step.jpg


New and Updated APIs Available for Chase Paymentech Fraud Protection (DEV-8267)

After setting your fraud options in Chase Paymentech and in Aria, you can use API calls for fraud protection as described below. Click on the links for the API calls listed below for new or updated documentation. 

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, fraud filtering, or 3D Secure authorization.

  • You can use the new API call validate_acct_fraud_scoring validate_acct_fraud_scoring_m to obtain a fraud score from Chase Paymentech when an account holder tries to make a purchase.

    Based on the fraud score, your specified fraud scoring actions will be taken on an account according to the fraud scoring options you set and your configuration in Chase Paymentech.
  • The API calls listed in the table below contain a new input and a new output to support fraud filtering:
  • The input fraud_filter allows you to enable or disable fraud filtering when an account holder tries to make a purchase.
  • The output proc_fraud_filter_response contains the fraud filter response provided by Chase Paymentech.

Based on the fraud filter response, your specified actions will be taken on an account according to the fraud filtering options that you set and your configuration in Chase Paymentech.

Affected APIs


Refund Notices Display all Required Information (DEV-8537)

Refund notices display the payment type and masked credit card number when the insertCCTypeWOParentheses and insertMaskedCCNumber strings are used. Example: if you process a refund for a Visa credit card with the number "4444-4444-4444-4448" and the previously-mentioned strings were used in the notice template, then the refund notice will display the payment type "Visa" and the masked credit card number "************4448".


New Payment Methods and Payment Features Available when Using WorldPay (DEV-8575) 

If you use WorldPay as your payment gateway, you now have access to the features described in the table below. Contact your WorldPay representative for more setup information and additional documentation.

Feature Description Instructions
New payment methods

You can now accept the following payment methods:

  • ApplePay—Indirect; 
  • PayPal Express Checkout—Indirect; 
  • SEPA (Single Euro Payments Area) Direct Debit (listed as “Direct Debit” in Aria);
  • Tokenized credit card.  

The API calls required to accept ApplePay and PayPal Express Checkout are identified in the API Features section below (DEV-8575).

To see the list of new payment methods, in Aria:

  • Click Configuration > Payments > Payment Gateways > WorldPay > Accepted Payment Methods.

To accept payments from customers using SEPA Direct Debit, you must first specify your merchant number, which you can obtain from your WorldPay representative. You can specify only one merchant number at the payment gateway level and create multiple collection groups with different merchant numbers based on your requirements. Specify your merchant number(s) as described below:

Payment Gateway Setting

  1. Click Configuration > Payments > Payment Gateways > WorldPay.
  2. Enter your Merchant Number.
  3. Complete the remaining information based on your requirements.
  4. Click Save.

Collection Group Setting

Do either of the following:

  1. Click Configuration > Payments > Collection Groups > New.
  2. Complete the required fields.
  3. From the Payment Processor list, select WorldPay.

OR

  1. Click Configuration > Payments > Collection Groups.
  2. Click on a collection group for WorldPay.
  3. Click Processor Details.
  4. Enter your Merchant Number.
  5. Click Save.

Your specified merchant number will be used for accounts in the collection group.

Note: Because of a limitation associated with SEPA Direct Debit, Aria does not recommend using authorize and capture in the same API call for payments made using that payment method. Instead, you should first make an authorize API call, confirm that the order has been moved into the authorized status, then attempt to make a capture API call). This will ensure a payment is authorized before the payment is captured and the account balance is reduced.
$0/$1 authorization

Allows you to perform $0/$1 authorizations to check the validity of a credit card before processing a payment

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, fraud filtering, or 3D Secure authorization.
Contact your WorldPay representative to enable this feature.
Provides you with immediate updates about changes to the status of payments. You can then take your chosen action on an order such as fulfilling the order or providing the account holder with the order status.

To see the status of a payment that was just made by an account holder, in Aria:

  1. Find the account holder.
  2. Under Accounts > Account “XYZ”, click Payments & Credits.

The current payment status is displayed in the Status column.


Application Fixes 

  • When you created a service credit for specific plan instances, the credit was applied to all plan instances on an invoice instead of only the selected plan instances. (TICKET-11921)
  • When using an electronic payment method for collection, and selecting specific charges to pay, the specific charges were not being collected, instead the collection on charges was based on FIFO. (TICKET-12433)
  • The account holder's middle initial was not copied from the account contact details to billing contact details when your client parameter Copy Admin Contact To Empty Billing Contact Fields was set to True(TICKET-14381)
  • Accounts with a master plan instance whose next bill date was one year after the bill through date had their next bill date set to the incorrect year. (TICKET-15643) 
  • When updating Processor Details for a Collection Group (e.g. login credentials) in the UI, the updated data was not saved in the database and the changes would disappear. (TICKET-15676) 
  • A monthly anniversary invoice for charges was not including a recurring fee charge on a plan billed quarterly. (TICKET-15691)
  • When assigning to an account a Master Plan with a "recurring" flag set to "no" (that is, not billable), and Supplemental Plan was subsequently assigned to an account with "prorated invoice" specified, the Master Plan's "no" recurring flag was not honored, and an invoice was generated. (TICKET-15736) 
  • An existing multi-plan contract was getting discarded when a new multi-plan contract was created for the same Master Plan instance, even though the "Auto Discard" checkbox was left unchecked (TICKET-15772)
  • When you removed a payment method from an account, incorrect validity dates were displayed for the disabled payment method. (TICKET-15815)
  • When assigning a plan to an account, specifying an override_bill_thru_date of the 29th or 30th (i.e. the bill date of the plan is the 30th or 31st), and an alt_start_date of 28-February, an error was received (rather than an expected one-day charge for the plan). (TICKET-15845)
  • Duplicate invoices were generated when you replaced an account's inactive plan (never invoiced before) with an active plan. (TICKET-15918)
  • When a queued billing frequency change occurred on the billing anniversary, the service period for the anniversary invoice was incorrect. E.g., updating a monthly Master Plan and monthly Supplemental Plan to bill annually on the next billing anniversary resulted in only monthly charges on the billing anniversary. (TICKET-15949)
  • Contracts scheduled to roll over to a different plan and/or rate schedule did not roll over after their bill through/anniversary dates. (TICKET-15968
  • Account was being invoiced twice after plan assignment. The overlapping bill period charges resulted when the plan assigned has mandatory plans being assigned at the same time resulting in the bill dates for the mandatory plans being lost, and the "parent" plan's bill dates to be misaligned. (TICKET-15981).
  • Errors occurred during encryption/decryption of a credit card number, bank account number, or IBAN (International Bank Account Number) that was 18 characters long. (TICKET-15984)
  • Clicking the left-hand navigation under Account before the Account Overview loads, after clicking an account number from the search screen, resulted in a "Data Table Warning." (TICKET-15988)
  • If you used Chase Paymentech as your processor, the tax type applied was incorrectly displayed as a number on invoices instead of as the applicable tax type (examples: FED or STA). (TICKET-16001)
  • Supplemental plans that were set to "Inactive" status showed "Inactive" as expected on plan detail screens, but showed "Active" on the plan hierarchy screen. (TICKET-16039)
  • When performing collections using the Braintree payment processor, the actual processor status, and status text was not populating and displaying in Aria (TICKET-16041)
  • When a Master Plan had mandatory plans to be assigned at the time of plan assignment, proration charge amounts were not correct if the mandatory Child Plans' recurring billing interval was longer than one month. (TICKET-16062)
  • An error occurred when you tried to use an alternate one-time payment method to make a payment for an account without an existing payment method. (TICKET-16073)
  • insertCCType" and "insertMaskedCCNumber" statement template replacement strings did not pull CC data onto statement template when Orders were invoiced immediately. (TICKET-16074)
  • When the usage unit threshold is lowered on a plan, Aria will now send the usage unit threshold email to customers, rather than returning a "too many rows fetched" error. (TICKET-16156)
  • After approving a pending invoice for an account that includes a Master Plan Instance with multiple supplemental plans, more than one of which have both queued custom rate changes and different services, bill dates among the supplemental plans are no longer out of sync. (TICKET-16280)

API Features 

New and Updated APIs Available for Chase Paymentech Fraud Protection (DEV-8267)

After setting your fraud options in Chase Paymentech and in Aria, you can use API calls for fraud protection as described below. Click on the links for the API calls listed below for new or updated documentation. 

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, fraud filtering, or 3D Secure authorization.

  • You can use the new API call validate_acct_fraud_scoring validate_acct_fraud_scoring_m to obtain a fraud score from Chase Paymentech when an account holder tries to make a purchase.

    Based on the fraud score, your specified fraud scoring actions will be taken on an account according to the fraud scoring options you set and your configuration in Chase Paymentech.
  • The API calls listed in the table below contain a new input and a new output to support fraud filtering:
  • The input fraud_filter allows you to enable or disable fraud filtering when an account holder tries to make a purchase.
  • The output proc_fraud_filter_response contains the fraud filter response provided by Chase Paymentech.

Based on the fraud filter response, your specified actions will be taken on an account according to the fraud filtering options that you set and your configuration in Chase Paymentech.

Affected APIs


New and Updated APIs Available for New WorldPay Payment Methods and Fraud Protection Features (DEV-8575) 

If you use WorldPay as your payment gateway, you now have access to the features described below. Contact your WorldPay representative for more setup information and additional documentation. Click on the links for the API calls listed below for new or updated documentation. 

  1. To accept payments from customers using ApplePay or PayPal Express Checkout, pass the values for either of those payment methods to the pay_method_type field in record_alternative_paymentrecord_alternative_payment_m.
  1. Aria returns Error Code 4040 (Could not find a processor for this payment method) when you call the following APIs with unsupported payment methods specified:
  2. The 3D Secure (3DS) authentication feature provides additional fraud prevention when transactions are processed. This feature requires account holders to enter a password when they make an online purchase using a credit or debit card. You may choose to require 3DS for only certain transactions. Example: orders over a particular amount that you specify. 3DS applies to Visa and MasterCard in any region, and American Express and JCB (Japan Credit Bureau) in supported regions. 

To authenticate account holders with 3DS:

  1. Use the new inputs and outputs that have been added to the API calls listed below:
     

    API Calls

    New Inputs and Outputs

     New Inputs:

    • end_user_session_id
    • end_user_ip_address
    • end_user_browser_accept_header
    • end_user_browser_agent

     New Outputs:

    • proc_payer_auth_request
    • proc_redirect_issuer_url
  1. Call the new API authorize_3dsecure. authorize_3dsecure_m.
    These APIs allow you to authorize a card if you specified that 3DS is required for a particular transaction.

Example:

  1. When an account holder makes a purchase using a using a credit or debit card, call the authorize_electronic_payment(_m), update_payment_method(_m), or validate_acct_fraud_scoring(_m) API.
    If the card is enrolled in 3DS and you specified that 3DS is required for the transaction, Worldpay prompts the account holder to enter a password.
  2. After the account holder enters a password, call the API authorize_3dsecureauthorize_3dsecure_mWorldpay then authorizes the payment.
  3. Fraud scoring allows you to obtain an account holder's fraud score, which is calculated using your criteria specified in WorldPay. Example: when an account holder tries to make a purchase and the transaction is above your specified fraud score, you can take your chosen action on the account based on your requirements.

    For non-3DS credit or debit cards, use the new API call validate_acct_fraud_scoring validate_acct_fraud_scoring_m to obtain a fraud score from WorldPay when an account holder initiates a purchase.

API Fixes 

  • Documentation mismatches were reported and resolved in the get_discount_bundle_details_m API response structure. (TICKET-15637)   

  • When you assigned a supplemental plan using the assign_supp_plan_multi_m API, the generated prorated invoice did not include the tax date. (TICKET-15702)

  • Statement was not being generated when creating an order using create_order_m (TICKET-15931)

  • When you assigned a master plan using the update_acct_plan_multi_m API and provided a date in the override_bill_thru_date field, if the account was eligible for a combined invoice, multiple invoices were generated for the master plan instance instead of one combined invoice. (TICKET-15936) 

  • When creating an account with a combined invoice using create_acct_complete_m, the statement provisioning events were not triggered, and "create user" was not populated in the database. (TICKET-15977)
  • Creating an order using create_order_m was throwing an unexpected error when associated with a Master Plan Instance that is part of a Billing Group with a payment association of payment terms, and the payment term has an associated surcharge (TICKET-16036)
  • When you used the update_acct_plan_multi_m API to replace a plan that has an alternate bill day, a full invoice was generated instead of a prorated invoice reflecting the alternate bill day. (TICKET-16048)
  • update_acct_plan_m was throwing an unexpected error when updating the plan instance status without passing the plan units (TICKET-16072)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

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

Tags

This page has no custom tags.

Classifications

This page has no classifications.