Partner Dashboard Changelog

For the complete documentation index, see llms.txt. Append .md to any page URL for its markdown version.

Release notes for the Banxa Partner Dashboard. API and SDK changes are tracked separately in the product changelogs.

A redesign of the whole dashboard. Every page uses the new layout, the sidebar is reorganised, and three pages have new names. Nothing about your integration changes: credentials, webhooks, settings and orders all work as before.

• New look on every page — The dashboard has a new design, with the same page layout, title size and spacing on every screen. The Developer, Assets, Webhooks, Settings, Orders, Analytics, Branding, Team and Profile pages have all been redesigned.

• Sidebar in three sections — Pages are now grouped by what you use them for:

  Section	Pages
  Build	Developer, Assets, Webhooks, Settings
  Operate	Orders, Analytics
  Account	Branding, Team

  Native API accounts see only the pages that apply to them, as before: Assets, Settings and Branding are Hosted Checkout only. The sidebar stays in place while the page scrolls, and the collapse control is at its foot.

• Three pages renamed — Dashboard is now Developer, Style is now Branding, and the page where you manage users and roles is now Team, reached from the sidebar. Role permissions use the same page names, so a permission reads Team, Developer, Assets, Settings, Branding or Webhooks.

• Environment always visible — The top bar shows whether you are in Sandbox or Production, and you switch between them from a menu there.

• Developer page reorganised — Getting started cards sit at the top and, for Hosted Checkout accounts, show your checkout URL. Sections are reached from links within the page instead of tabs, and the credentials for each integration you use are shown separately. The Checkout API credentials section is now headed Hosted Checkout, the product's current name. The introduction can be dismissed.

• More detail on API keys — The keys table shows when each key was last used, and each masked key ends in its last four characters, so you can tell keys apart without revealing them. The key that signs your webhooks is labelled Webhook signing key.

• Webhooks and Settings as forms — Both pages are now laid out as forms rather than cards.

• Team as a table — Your company's users are listed in a table.

• Account deletion moved — On the Profile page, deleting your account is now in a separate Danger zone section.

• Help links in the sidebar — The sidebar links to the documentation, to Build with Agents, and to System status, which replaces the Support link.

• New sign-in page and logo — The sign-in page is redesigned, and the dashboard uses the Banxa by OSL logo.

• Sandbox test data on the Developer page — The hardcoded test card and phone numbers are gone, because they went out of date whenever the values changed. The page links to the guides that keep them current. → Sandbox Test Data
• Checkout preview on Branding — Branding no longer shows a preview of the checkout.

• Display is now Assets — The Display item in the sidebar and mobile navigation is now Assets. Same page, same permissions, clearer name for what it manages. → Partner Dashboard

• Documentation links pointed at the old docs site — Links out of the dashboard now resolve to docs.banxa.com.

• Display settings moved into Settings — Checkout display options are now configured on the Settings page rather than on their own page. Permissions moved with them, so a role that could edit display settings keeps that access under Settings.

• Testing information panel — The dashboard home now shows the sandbox testing configuration for your account, so test card and test payment details are visible next to the environment you are using them in. → Sandbox Test Data

• Webhook URLs are validated before they are saved — A webhook URL must now use https on port 443 and resolve to a public IP address. URLs that resolve to private, loopback, link-local, multicast or carrier-grade NAT ranges are rejected when you save them, including IPv6 addresses with an IPv4 address embedded in them.

  This affects local development: a tunnel URL such as an ngrok HTTPS address works, but pointing a webhook at localhost, 127.0.0.1 or an internal hostname no longer saves. → Webhooks

• Mixed integration type — An account can now hold both Checkout API and Native API credentials at once. The dashboard issues credentials according to the integration type set on your account:

  Integration type	Credentials issued
  Checkout API	Checkout API only
  Native API	Native API only
  Mixed (Checkout + Native)	Both

  Native card, Apple Pay and Google Pay payments need Mixed, because the order is created through the Checkout API while identity and eligibility run through the Native API. → Authentication & Environments

• Clicking an order did not open its details — Orders in some statuses failed to expand when selected. All order statuses now resolve.

• Checkout-only pages are hidden for Native API accounts — Accounts on the Native API integration type no longer see dashboard pages that only apply to Hosted Checkout.

• Orders table pagination — Paging through the orders list returned the wrong page of results.