Every firm that adds savings to its proposition makes the same decision early on. Do you take a finished, branded savings platform and point clients to it, or do you build the savings experience yourself and plug into the deposits underneath?
Both routes run on the same Bondsmith platform. The bank panel, the trust structure, the operations and the FSCS treatment are identical. What differs is how much of the client experience you own, and how much engineering you take on to own it.
Start with who owns the customer experience
The decision is not really about technology. It is about where savings sit in your business.
If savings is a product you want to offer alongside what you already do, a white-label platform gets you there quickest. Your clients see your brand, you keep the relationship and the distribution, and Bondsmith runs the platform, onboarding, KYC, rates, customer service and the bank panel behind it. There is little or no build on your side. The platform can sit behind your single sign-on so clients move between your core service and their savings without noticing a seam.
If savings is part of a product your own team is building, the API is the better fit. You already own the customer experience. You want deposits to appear inside it, in your interface, following your design and your flows. The API gives your engineers the bank panel, account operations, money movement, AML and KYC, reconciliation and reporting as services they call, rather than as a front end they adopt.
Two ways in, one platform underneath
| Comparison | White-label savings platform | Savings platform API |
|---|---|---|
| Who it is for | Wealth managers, adviser platforms, building societies and friendly societies that want a branded savings offering live fast | Fintechs, platforms and banks whose product team owns the customer experience and wants deposits inside it |
| What you own | Your brand, your clients and your distribution | The customer experience and the product the deposits sit inside |
| What Bondsmith runs | The platform, onboarding and KYC, rates and the bank panel, customer service, the trust structure and FSCS treatment | Everything behind the API: the bank panel, account operations, money movement, AML and KYC, reconciliation and reporting |
| Typical time to launch | 6 weeks, with no build on your side | 8 to 10 weeks, depending on your own build |
| How you integrate | Little or no engineering. We provide the branded front end, which can sit behind your single sign-on (SSO), and you point clients to it | Your engineers integrate the REST API, with webhooks and typed SDKs |
Four questions that settle it
Do you have a product and engineering team with capacity? If the honest answer is no, or not for this, take the white-label route. The API is only an advantage if someone is going to use it.
Does the savings experience need to look and behave differently from a standard savings platform? A standard flow, well branded, is what most advised and member-based businesses need. If your proposition depends on savings being woven into something else, a budgeting tool, a cash management view, a mortgage overpayment flow, you need the API.
How quickly do you need to be live? White-label is weeks with no dependency on your roadmap. API is also weeks from our side, but the timeline is yours to control, and yours to slip.
Who do you want handling clients day to day? With white-label, Bondsmith provides the customer service for the savings product. With the API, you typically front the client and we support you behind it.
You can start on one and move to the other
The platform underneath is the same, so this is not a one-way door. Firms that launch on white-label to prove demand can move the experience in-house later without changing banks, trust structure or client accounts. Firms building on the API sometimes use the white-label front end for a segment they do not want to build for.
Choose on where you are now, not where you might be in three years.
Contact us
If you are not sure which route fits, we will tell you. Most conversations settle it within half an hour, and we would rather point you to the simpler option than sell you a build you do not need.