Weavr
NOMINEE OVERVIEW
Weavr Docs is the developer portal for Weavr's embedded-finance toolkit, giving software teams regulated accounts, cards and payments as API building blocks — so they can add financial features to their product without becoming a bank themselves.
The portal is built around three core concepts (customers, instruments and transactions) and adapts to each reader: developers choose their use case, the instruments they'll issue and their customer type up front, and the documentation tailors its examples and guidance to that integration profile throughout. Inline glossary definitions demystify regulated-finance terminology exactly where it appears, an "Open with AI" entry point lets developers pull docs into their AI tools, and a full sandbox with a dedicated Simulator API lets teams build and test real money-movement flows before going live.
Around the guides sit four API references, SDKs for Web, iOS, Android and React Native, a live changelog, a status page and a glossary — one coherent home for everything an Embedder needs, from first read to production.
NOMINATION RATIONALE
1) BEST REIMAGINED ONBOARDING EXPERIENCE IN A DEVELOPER PORTAL
Why is this category a strong match?
Embedded finance is a conceptually alien context for most software developers, which makes onboarding the hardest problem this portal has to solve. Before writing a line of code, an integrator has to absorb concepts from regulated banking rather than software: verifying business or individual customers (KYB/KYC), Strong Customer Authentication, the difference between accounts that hold money and cards that spend it, and the many states a payment moves through before it settles. Weavr Docs was designed around exactly the "zero-to-hero across an alien domain" challenge this category rewards — taking a developer from "I've never built a financial product" to a tested, live integration without overwhelming them. Onboarding isn't a section of this portal; it's the organising purpose of it.
In what ways does the portal shine in this category?
The portal shines in four ways. First, it adapts to the reader: on the opening page, developers choose their use case (spend management, marketplace payouts, embedded banking, and more), the instruments they'll issue, the transaction types they need, and whether their customers are businesses or individuals — and that integration profile is saved and read by other pages, so examples and next steps reflect what each team is actually building. Second, it sequences a deliberate path from zero to live — understand how Weavr works, get sandbox access, generate keys and IDs, set up developer tools, complete a 15-minute quickstart, then go live and manage change — with each step scoped to give just enough to build confidence and move on. Third, it defuses jargon in place: regulated-finance terms carry inline glossary definitions exactly where they appear, and a plain "what we manage vs. what you manage" framing reassures both technical and non-technical readers about what they're taking on. Fourth, it lets developers learn by doing: a full sandbox with a dedicated Simulator API lets teams model real money-movement flows safely before anything reaches production. Together these turn a notoriously heavy first mile into a guided, hands-on runway.
