Changelog

See this update published within our Backoffice API Reference: Review User Details by Email Address or Id.

See this update published within our Backoffice API Reference: Update Submerchant Risk Exception Parameters.

See this update published within our Backoffice API Reference: Review Paginated Submerchants v2.

See this update published within the Guides section: Webhook: ApplicationStatusChange.

See this update published within our Backoffice API Reference: Review Paginated Users.

We updated the routingNumber field used in the Backoffice API to prevent submissions of miskeyed bank routing numbers, which can impact funding deposits. In addition to the 9-digit character length, this field now also validates data using the routing number checksum algorithm. If a user attempts to submit an invalid routing number in their request, the API returns the following response: "400 Bad Request: Routing number is invalid."

See this update published within our Backoffice API Reference: Create a User.

See this update published within our API Reference: Review Paginated Transactions.

See this update published within our API Reference: Review Paginated Chargebacks.