Release 19

• You can now pass a valid date without a time into date fields in the following APIs: get_coupon_history_m, get_all_invoice_information_m, and get_invoice_history_m. When you do that, an error no longer occurs and the data matching your query is returned. (TICKET-8308)
• 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)
• $0 refund line items are no longer displayed on an invoice when you issue a full or partial refund that applies to an invoice:
  • With multiple charges; and
  • With or without service credits included.
    (TICKET-16671)
• Plan unit instances are now successfully removed when plan instance units is downgraded via the update_acct_plan_multi_m API. (TICKET-16678)
• You can now successfully create a surcharge having multiple rates schedules and rate tiers using create_surcharge_m. (TICKET-16685)
• You no longer encounter an error when you call the validate_payment_information_m API and you pass in a cvv (card verification value) that is less than 3 characters long. This is because that field is now formatted correctly. When the payment method is American Express, Aria now adds zeros to the cvv to make the field 4 characters long. When the payment method is not American Express, Aria now adds zeros to the cvv to make the field 3 characters long. These changes apply to the following payment gateways:
  • Adyen
  • BrainTree
  • Chase Paymentech
  • Merchant e-Solutions
  • First Data Payeezy
  • Paymetric
  • PayPal PayFlow Pro
  • First Data PayPoint
  • TNS

For supported payment gateways not listed above, the cvv field was already formatted correctly. (TICKET-16744)

• API Live no longer prevents users from entering values in certain fields due to incorrect pick lists in some APIs. (TICKET-16746)

Stage Current

Stage Future

Production

Stage Current

Stage Future

Production