Release Notes

Updates



September 11, 2019



  • All transaction endpoints now accepting billToPhone and shipToPhone parameters. This information is especially helpful for Fraud Checks.
  • All eCheck transactions now accepting secCode
  • New transaction status: fraudReject.

September 7, 2019



  • 3D Secure now available for switch transactions run through the API.

July 10, 2019



May 29, 2019



  • Updated webhook request body message when a TRANSACTION_CAPTURED event type has resulted in an error or decline.
    • data.gatewayProcessingError is now data.error

May 23, 2019



  • New options have been added to allow greater control over the hideBilling UI Option for iframes.
    • You may now include any of the following keys:
      "hideBilling": {
          "hidePostal": true,
          "hideCountry": true,
          "hideAddressOne": true,
          "hideAddressTwo": true,
          "hideCity": true,
          "hideState": true
      }
    • Note: hideBilling will continue to accept true and false if you wish to hide all billing fields. (Default continues to be false).

May 22, 2019



  • When card information is manually provided to run a transaction for a card that has already been saved:
    • If the saved expiration date is better than the provided expiration date:
      • The saved card will be used and the provided card information date will be disregarded.
    • If the new expiration date is better than the saved expiration date:
      • The provided card information will be used.
      • A new card token will be created and returned in the response.
      • If applicable, webhooks will be fired.
      • The old card token will still be valid.

May 09, 2019



  • You may now choose to prevent a card token from being saved when a transaction is run using the Run Credit Card Transaction iframe.
    • To do so, set processingOptions.saveCardToken to false in your request for a One-time Use Token.
    • (Note: If you do not provide this option a card token will be saved by default.)
  • Option to return an HTML response when an iframe returns an error. (By default error response content-type will be application/json.)
    • To use this option, send shouldReturnHtml=true as a query parameter to your GET request.

May 8, 2019



  • Recently added features:
    • Ability to configure Webhooks in order to retrieve real-time data regarding events that occur in your Payment Service iframes
    • New Simple Login endpoint: allowing trusted users to proceed directly to the retail/MOTO Iframe without the necessity of entering in a Nexio username and password.

January 28, 2019



  • The following deprecated response objects have now been removed from the Run Credit Card Payment endpoint:
    • foreignProcessingCurrency
    • cardDetails
    • customFields
    • customerInfo
    • cart
  • The following deprecated response object has now been removed from the Save Card and Run Credit Card Payment endpoints:
    • kountResponse.kountData

December 12, 2018



  • Additional fields being passed along to Nexio's fraud tools:
    • Customer created at date (data.customer.createdAtDate)
    • Shipping Address (data.customer.shipTo)
    • This information is useful for customizing your fraud rules

November 7, 2018



  • New processing option allows users to choose which merchant to use to process a transaction.

October 10, 2018



  • AVS results (avsResults) returned in response object.
  • EnsureBill account updater now available. (Documentation for this feature coming soon.)
  • Nexio Dashboard:
    • Merchant ID selector filtering: you may now filter merchants by name, merchant ID, and currency code.

October 3, 2018



  • Address Verification Service (AVS) now enabled.
  • Nexio Dashboard:
    • Chargeback widget added.
    • Currency selector changes all charts and widgets.
    • Column filtering on tables can now search for partial amounts.
    • Merchant ID selector widens to fit merchant name.
    • Now importing Customer ID from Gateway responses.
    • Chargeback page now shows Cardholder Name when linked to a transaction.

September 26, 2018



  • Additional Auth.net features now available in Nexio Dashboard: ability to void transactions, approve or decline auth only transactions, and refund settled transactions.
  • Processor Management: Clients with multiple merchants can now choose which merchants to process with, or to balance their processing equally across all merchants. This feature works by checking each merchant's processing volume at the time of the transaction and then running the transaction against whichever merchant has less volume.
  • Nexio Dashboard:
    • Merchant ID selector now accommodates long merchant names.
    • Merchant ID selector now lists merchant names alphabetically.
    • New widgets: Transactions, Sales, Approvals & Declines.

September 19, 2018



  • Client-side Encryption now available
  • The following response objects are now deprecated and will be removed in the future: kountResponse.kountData (Save Card & Make Payment endpoints) and foreignProcessingCurrency, cardDetails, customFields, customerInfo, and cart (Make Payment endpoint)
  • Bug fix: Decline and Error responses now include gatewayResponse and merchantId
  • Nexio Dashboard:
    • Reserve Tab now displays top 4 merchant reserve amounts. (Or all merchant reserves if 5 or less merchants are selected.)

September 12, 2018



  • Gateway Failover: Merchants set up with more than one gateway are now able to choose a backup gateway in case of primary gateway failure
  • Option to limit country list in the Make Payment and Save Card iframes
  • Option to choose default country in the Make Payment and Save Card iframes
  • Nexio Dashboard:
    • New Reserve Tab for merchants with a reserve account.

September 5, 2018



  • Integration with Auth.net
  • Refund disabled on transactions with pending chargeback

August 22, 2018



  • Added Order ID to Refunds in the Transactions Tab of Nexio
  • Added the ability to delete tokens in the API

July 16, 2018



  • Fixed bug where View Only users were able to run transactions. This functionality is now limited to Admin and Standard users