New Features

Payment API

• Transactions can now be directly routed by specifying the processor in the request body. If unspecified, the transaction will be routed based on the configuration of the routing plan assigned to the merchant
  • Note that the processor must be part of the routing plan that the merchant is assigned to
  • Responses now also include the processor.routingSource property to track if the transaction was routed by either plan or direct.
  • For supported enumerations, please review our Transaction API endpoint

# Improvements

Dashboard

• Various styling updates to make pages and modals more consistent.
• Merchant Details - Certain tabs in the merchant detail, like transactions and loans, will display as disabled if the merchant does not have records associated with the tab
• Merchants can quickly be added from the sidebar navigation
• AI Merchant Data
  • Now displays status of the connection
  • Merchants can now be boarded from the AI Merchant Data tab

Payments API

• Order and Description fields have been mapped for the following connections. Character length has been expanded to 255 characters and is trimmed if the connection supports a lower character count.
  • Affinipay
  • Payflow Pro
  • AuthorizeNet
• Affinipay
  • ACH transactions are now supported on Affinipay
    • NOTE - In order to properly route transactions, when configuring the affinipay merchant connection please include the achMid to specify the merchant ID at affinipay where ACH transactions should be routed.

Idempotency Keys

• Idempotency keys are now supported on most API endpoints. Please review API documentation for supported endpoints.

Bugs

Forms

• Resolved an issue where address fields may display 'undefined' if tab key was entered