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



 

Home > Aria6 User Documentation > Aria6 Release Notes > Aria6 Release 14.1

Aria6 Release 14.1


Application Features 

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


Chase Paymentech Fraud Protection Options Available (DEV-8267)

If you use Chase Paymentech as your payment gateway, you now have access to fraud scoring and fraud filtering for additional fraud protectionfraud protection. To use these fraud protection features, you must have them enabled and configured with Chase Paymentech. In addition, you will need to use the applicable fraud merchant ID and division code(s) for the fraud protection features you need. Contact your Chase Paymentech representative for more information and additional documentation.

Fraud protection applies to these payment methods: credit card, direct debit, electronic check, and tokenized credit card.

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.

To use the fraud protection features in Aria, set up your fraud options as described in the table below, then make the desired API calls.

Feature Description Instructions
  • Fraud scoring








 

 

  • Fraud filtering

Allows you to obtain an account holder's fraud score or fraud score assessment, which is calculated using your criteria specified in Chase Paymentech

Example: when an account holder tries to make a purchase and the transaction is above your specified fraud score, you may choose to suspend the account (Aria 6) or master plan instance (Aria Crescendo).

 

 

 


Allows you to determine an account holder's fraud risk based on credit card numbers, credit card prefixes, and issuing countries that you identified in Chase Paymentech 

Example: When an account holder tries to make a purchase with a credit card number that is on your list of fraudulent credit cards, you may choose to decline the transaction.

Payment Gateway Setting:
To set the desired fraud options for Chase Paymentech in Aria:

  1. Click Configuration > Payments > Payment Gateways > Chase Paymentech > Gateway Options.
  2. Under Fraud Options, make selections based on your requirements.
    The fraud options are described in the screen tips.
  3. Click Save.
    The specified actions will be taken on accounts based on your selected fraud options and your configuration in Chase Paymentech.

Collection Group Setting:
To set the desired fraud options for a collection group in Aria:

  1. Do either of the following:

a.     Click Configuration > Payments > Collection Groups > New.

b.     Complete the required fields.

c.     From the Payment Processor list, select Chase Paymentech.

                       OR

d.     Click Configuration > Payments > Collection Groups.

e.     Click on a collection group for Chase Paymentech.

f.       Click Collection Group Options.

  1. Under Fraud Options, make selections based on your requirements.
    The fraud options are described in the screen tips.
  2. Click Save.
    The specified actions will be taken on accounts in the collection group based on your selected fraud options and your configuration in Chase Paymentech.
Note: The fraud options that you set for the collection group will be applied to accounts in the collection group instead of any fraud options that you set at the payment gateway level.
 
  • For improved fraud scoring, it is recommended that you send this data to Chase Paymentech when you create or update an account: customer IP (Internet Protocol) address, customer browser, fraud merchant ID, and customer gender. You can now optionally customize this data in Aria as follows:
  1. Do either of the following:
  1. Click Configuration > Payments > Payment Gateways > Chase Paymentech > Field Options.

       OR

  1. Click Configuration > Payments > Collection Groups.
  2. Select a collection group for Chase Paymentech.
  3. Click Advanced Options.
  1. Enter your chosen value to be sent to Chase Paymentech or select an account field whose specified value should be sent for the following fields:
  • customer_ip_address;
  • customer_browser;
  • fraud_merchant_id;  
  • customer_gender.

       The fields are described in the screen tips.

  1. Click Save.
  • You can select fraud scoring and fraud filtering options if you are using Direct Post. To set up fraud protection in a Direct Post configuration:
  1. Click Configuration > Client Settings > USS Reg Configuration > New Direct Post.
  2. Select the desired fraud options between Fraud Scoring Enabled and (MP) Status on Fraud Filtering CC Issuing Country Suspect.

    The options are described in the screen tips.
  3. Click Save.

Based on your selected fraud options and your configuration in Chase Paymentech, the specified actions will be taken on accounts handled by your applications that use Direct Post.

Note: The fraud options that you set in your Direct Post configuration will be applied instead of any fraud options that you set at the payment gateway or collection group level.


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 

  • 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)
  • The account holder's first name, middle initial, and last name were not sent with a payment request when your client parameter Copy Admin Contact To Empty Billing Contact Fields was set to True then the billing contact details were copied from the account contact details. (TICKET-14381)
  • 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) 
  • 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) 
  • For accounts with pay method = 13 (tokenized credit card), update_acct_complete was failing to correctly update new values passed for cc_expire_mm, and cc_expire_yyyy, instead erasing previously stored values (TICKET-15866)
  • When calling cancel_queued_service_plan on a scheduled termination date that matches the Billing Anniversary of the plan, the plan status retained the status "Terminate Pending" (rather than "Active"). (TICKET-15926)
  • 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)
  • An account's invoice was being collected prior to its due date when the first digit of the total account balance was lesser than the first digit of the currently due invoice amount. This was occurring due to an unnoticed implicit conversion of a number to a string value (TICKET-15996)
  • 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 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)

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 API response structure. (TICKET-15627)
  • 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)
  • When you called the assign_supp_plan_multi API, if a bill date reset happened for a supplemental plan during proration on an account and that supplemental plan had a rollover plan, then all other accounts with that same supplemental plan were getting marked as "termination pending". (TICKET-16037)
  • With Fraud Scoring enabled, creating a new account with a $0 Master Plan, and validating a payment method via Direct Post, no longer returns an error. (TICKET-16241)
  • The value of the Location parameter returned by Aria via a Direct Post configuration was causing the redirect URL to fail. (TICKET-16251)

WSDL File Locations

Stage Current

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

Stage Future

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

Production

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

Object Query WSDL Files

Stage Current

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

Stage Future

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

Production

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

Tags

This page has no custom tags.

Classifications

This page has no classifications.