Skip to main content

Dynamic UI

Build Your Own UI — or Use Ours​

Our Dynamic UI API gives you full control over your frontend while removing the complexity of handling conditional, ever-evolving payment flows.

With a single API, you can:

  • Build and own your UI, while still benefiting from backend-driven logic. The API adjusts dynamically to each user’s context, returning only the steps and data strictly required — and never asking for data we already have.
  • Use our hosted UI, which is powered by the exact same API. This is the fastest way to get started, and because the logic is shared, you can switch to your own UI later without re-integrating.
  • See it in action — our own app uses this API too. You can demo or even dogfood the full user experience exactly as your customers would.

Powered by Dynamic Channels​

Behind the scenes, everything is driven by our channel framework — a flexible model that lets us continuously integrate and expose new payment methods and routing options.

That means we can offer your business (and your users) faster, cheaper, and more efficient payment paths — without needing you to rebuild your frontend or integration every time something changes.

That’s where forms become critical: they act as a dynamic contract between our system and your UI. If a channel requires different data tomorrow — say, a new field for a payout method or a different step for KYC — you won’t need to update your code. The API will simply reflect the new requirements, and your integration will adapt automatically.

Learn more about channels and how we use them:

Flexible by Design​

You don’t have to go all-in from day one:

  • Start with our hosted UI to test demand or get to market quickly.
  • Then gradually migrate one flow at a time — for example, keep using our onboarding and KYC experience while taking full control of the payouts UI.

Not More Complex — Just Less Work​

Dynamic UIs are designed to simplify, not complicate:

  • No need to model business rules or flow logic.
  • No need to handle ever-changing requirements.
  • Just render what’s needed, when it’s needed.

For full control and audit ability, we also publish static schemas to a public GitHub page so you can always know exactly what to expect — even if you choose to build everything yourself.