Fintech Specialist or Generalist Agency? How a Retailer or Platform Should Choose a Partner to Launch a Wallet, Card or BNPL Product

Fintech Specialist or Generalist Agency? How a Retailer or Platform Should Choose a Partner to Launch a Wallet, Card or BNPL Product

The short answer: choose a fintech specialist when the product moves money, extends credit or holds customer funds, because compliance, partner models and platform choice shape the build from the first week. A generalist agency can be the right choice when the financial element is light and a regulated partner carries the obligations. The deciding question is who will carry the regulatory complexity.

More retailers and platforms are becoming financial-product businesses, whether through a wallet, a branded card or a buy now, pay later option at checkout. Most of them already work with a capable digital agency, which makes the obvious next step feel natural: ask the same team to build it. Sometimes that is the right call. Often it is where a launch quietly acquires risks that nobody on the team has met before. This guide offers a neutral way to decide, including a checklist you can apply to any partner, ourselves included.

Why this decision is harder than a normal agency selection

Choosing an agency to build a loyalty app or a new storefront is a familiar exercise. You look at portfolio, craft, process and fit. The failure modes are well understood and mostly recoverable: a late delivery, a design that misses the brief.

A wallet, card or BNPL product behaves differently, for three reasons.

• The product is regulated, or depends on someone who is. Holding customer funds, issuing a card or offering credit all sit inside regulatory perimeters. Even when a licensed partner carries the licence, your product has to behave in ways that keep that partner compliant.
• You are assembling a chain, not buying a build. A typical launch involves a regulated provider, a platform or processor, identity and fraud tooling, and your own systems. The agency's job is to make those pieces work together and to know which ones to choose.
• Mistakes are expensive to reverse. A design decision about how customer funds are held, how a customer is verified or how a repayment is collected can be hard to change once customers are using the product.

None of this means a generalist agency cannot do the work. It means the selection criteria need to change from "can they build it?" to "do they know what building it involves?"

What a specialist knows that a generalist has to learn

The case for specialist expertise is a case about learning curves. Innovify's own embedded finance and digital wallets work sits on the specialist side of this comparison, so weigh our view accordingly. Every team can learn these subjects. The question is whether you want your launch to be the place where they learn them. In our view, four areas matter most.

Compliance and the regulatory perimeter

A specialist will recognise early which of your product decisions pull you into a regulatory perimeter and which do not. Verifying customers, monitoring for financial crime, protecting customer money, authenticating payments and meeting UK expectations on treating customers fairly are not features to add at the end. They shape the flow of the product.

Innovify's stated approach is to design compliance in from day one, and that is the right question to put to any partner: at what point in the plan does compliance enter, and who owns it? If the answer is "once the build is complete", you are likely to find constraints at the most expensive moment. A good specialist will also be clear about where its role ends and your regulated partner's begins.

Platform and provider choice

Retailers rarely build financial infrastructure from nothing. They use platforms and regulated providers for issuing, accounts, payments or credit, and the choice among them carries consequences: how much control you have over the customer experience, how quickly you can launch, what the economics look like and how hard it is to change later.

A specialist has usually seen how those choices play out in delivery. A generalist is more likely to rely on vendor documentation and sales conversations, which describe what a platform can do and say less about what it is like to build on. This is the area where an agency's experience across several platforms is most useful, because it lets them compare approaches rather than defend one. Innovify describes itself as an implementation partner across multiple fintech platforms, offering a fast, compliant route to launching financial products. We deliberately do not name platforms here, and you should be cautious of any partner that recommends one without explaining the alternatives.

Partner models

Who sits behind the product matters as much as what the customer sees. In broad terms, a retailer can launch under a regulated partner's permissions, partner with an authorised institution that provides the regulated service, or pursue its own authorisation. Each choice allocates obligations, control and cost differently, and each affects what the agency has to build.

We have written elsewhere about the entry decision for embedded finance and about build-versus-buy choices, so we will not repeat those arguments. The point for agency selection is narrower: your development partner should be able to explain how the model you choose changes the design, the integration work and the operating responsibilities, and should do so without needing a long discovery phase to learn the vocabulary.

Delivery risks specific to financial products

Some delivery risks are particular to this category. Reconciliation between your systems and a provider's, handling of failed or disputed payments, onboarding drop-off caused by verification steps, fraud controls that block good customers, and the operational processes that sit behind support and complaints are examples. A team that has shipped financial products tends to design for these from the start. A team that has not will often meet them in testing or, less happily, in production.

When a generalist agency is the right choice

A fair comparison has to say where the generalist wins, and there are real cases.

• The financial element is light. If your product adds a loyalty balance, a stored-value gift feature administered by a regulated partner, or a branded front end on a partner-run wallet, the heavy regulatory and infrastructure work sits elsewhere. Strong product design and front-end craft may matter more than financial depth.
• A specialist already sits in the chain. If a regulated provider or platform supplies the financial engine and its own implementation support, a generalist agency can handle your customer-facing layers well.
• The scope is exploratory. If you are testing demand before committing to a launch, a small build by a team you already trust may be a sensible first step.
• Your internal team has the financial expertise. If you employ people who have launched regulated products before, you may need an agency for capacity and craft rather than for domain knowledge.

In each case the generalist works because the missing knowledge is held somewhere else in the chain. When it is not, the cost shows up in the schedule, in rework and in risk.

A decision checklist you can use with any partner

The checklist below is deliberately partner-neutral. We suggest asking each shortlisted agency, Innovify included, the same questions and comparing the answers in writing.

1. Show us what you have launched. Which financial products have you taken from design to live customers, and what was your role? Ask for specifics about the problems that arose, not only the successes.
2. Where does compliance enter the plan? Ask them to point to the stage at which regulatory requirements shape design decisions, and to name who is responsible for them.
3. Which partner models have you worked with? Look for an answer that compares models and explains trade-offs, rather than recommending one by default.
4. Which platforms have you built on, and why would you not use them? A partner who can only describe the benefits has probably not seen the limits.
5. How do you handle the unglamorous parts? Probe reconciliation, disputes, failed payments, support tooling and operational runbooks.
6. What do you need from us and from our regulated partner? A partner who understands the chain will have a clear list of dependencies.
7. What would make you advise us not to proceed? The ability to say no is a useful signal of judgement.
8. How is the team structured, and who is accountable? Understand who you will work with day to day and who owns delivery outcomes, and ask how service levels are agreed.
9. What will we own at the end? Clarify code, documentation, configuration and the knowledge needed to operate the product without dependence.
10. How do you work with our existing agency or internal team? Retailers often have established partners. The right choice may be a specialist alongside them rather than a replacement.

A useful way to score the answers is to weight the first five more heavily if the product holds funds or extends credit, and to weight the last five more heavily if the financial component is light.

Signs you may be underestimating the task

Some patterns suggest that a launch is being scoped as ordinary software when it is not.

• The project plan has no named owner for regulatory questions.
• The partner model has not been chosen, but the build has started.
• Verification, fraud and dispute handling appear in the plan as "later phases".
• The agency speaks confidently about the front end and vaguely about the provider integrations.
• Nobody can say which of the product's features depend on a regulated partner's permissions.

If two or more of these apply, pause and review the scope before the build commits you to decisions that are hard to reverse.

Where Innovify fits

Innovify is a technology partner with deep expertise in banking, financial services, fintech and insurance. We help mid to large businesses build AI-native products, modernise their technology stack and launch fintech products, including for retailers and platforms that are new to financial services. As an implementation partner across multiple fintech platforms, we aim to give businesses a fast, compliant route to launching financial products, and we design compliance in from day one.

Our view is that the right partner depends on your product, and we would rather you used the checklist above than took our word for it. If you are weighing a wallet, card or BNPL launch, our work on embedded finance and digital wallets describes how we approach it, and we are glad to talk through where a specialist adds value and where it does not.

FAQ

Should a retailer use a fintech specialist or a generalist agency to launch a wallet?

A retailer should use a fintech specialist when the wallet holds customer funds or sits close to regulated activity, because compliance, provider choice and delivery risks shape the design from the start. A generalist agency can be appropriate when the financial engine is supplied and administered by a regulated partner and the agency builds customer-facing layers.

What does a fintech specialist know that a generalist agency does not?

A fintech specialist usually knows how regulatory requirements shape product flows, how platforms and partner models compare in practice, and where financial products tend to go wrong in delivery, such as reconciliation, disputes and fraud controls. A generalist can learn these areas, but the learning then happens during your launch.

Can a generalist agency build a BNPL product?

A generalist agency can build parts of a BNPL product, particularly customer-facing screens, but BNPL involves credit-related obligations, affordability and repayment handling that differ from a wallet's. The rules have been evolving, so confirm the current position with your legal advisers and make sure your delivery partner has experience of the credit side.

What questions should I ask a wallet development partner?

Ask which financial products they have launched, where compliance enters their plan, which partner models and platforms they have worked with and what they would advise against. Ask how they handle reconciliation, disputes and failed payments, and what you will own at the end. Compare written answers across shortlisted partners.

How do I know if my project needs a fintech specialist?

Your project probably needs a fintech specialist if it holds customer money, issues a card, offers credit, or depends on a regulated partner's permissions. If nobody on your team can say which features rely on those permissions, that is also a sign. A light financial component supplied by a provider may not.

Can I use a specialist alongside my existing agency?

Yes, and for many retailers this is the most practical arrangement. A specialist can own the financial architecture, provider integrations and compliance-sensitive design, while your existing agency continues to own brand, storefront and customer experience. Agree the boundaries and responsibilities in writing before work begins.

Conclusion

The choice between a specialist and a generalist is not a question of quality. It is a question of where the financial knowledge sits and who carries the regulatory complexity. When the product moves money or extends credit, that knowledge should be in your delivery partner from the start. When the financial work is held elsewhere in the chain, a strong generalist may be enough. Use the same checklist on every candidate, weigh the answers against the nature of your product, and treat vague answers on compliance and delivery risk as a signal in their own right.