New Revenue Payments API
Thursday, September 10, 2026
What it is
New public API endpoints that let customers, partners and third-party agents create payment records, retry failed payments and configure checkout page settings programmatically. Until now those actions were only possible inside the HubSpot UI. Public beta, all hubs and tiers.
Why it matters
Every action HubSpot exposes through a public API is an action an agent can take, whether that agent is Breeze, a partner integration or a model working from your terminal. Retrying a failed payment from an external app or creating a payment record from another system stops being a manual step. The daily emails about new API permissions are the same story from the other side.
The Take
ERP Lite is here.
Chris picked this one on purpose, and the reason is the qualifier. It is not a payments API, it is a revenue payments API, and revenue payments are the ones you receive. The obvious question is whether a bill payments API is coming someday, because that is the other half of an ERP. HubSpot has no purchase order system out of the box, though the team has built approximations for clients. Between contracts, orders, subscriptions and now programmatic payments and checkout settings, ERP Lite is here, and there is no reason a complete e-commerce experience cannot be built inside HubSpot.
If you have been getting a daily email about new API permissions and wondering what is happening, this is what is happening. Every portal gets the notice and every notice is one more thing an agent can do on your behalf. If the API is available, AI can access it. Breeze can access it. That is the frame to read every one of these announcements through.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
FAQ
What is the difference between a revenue payment and a bill payment?
Revenue payments are money you receive, accounts receivable. Bill payments would be money going out, accounts payable. This API covers the receiving side.
What can the API do that the UI could not expose?
Nothing new in kind. It exposes to code what was UI-only: creating payment records, retrying failed payments and configuring checkout page settings. The change is who can do it, which now includes integrations and AI agents.
Why am I getting daily emails about new API permissions?
Because HubSpot is opening its public API surface quickly and every portal gets a notice for each new scope. Each one is a capability an agent or integration can now use.
Produced by Value-First Media