On this page
In brief
- Compare ClearBank, Griffin, Modulr, Railsr and Weavr by their banking, payment and platform roles, including services delivered through partners.
- Calculate total cost using setup fees, minimum commitments, usage charges and internal operating costs under realistic volume forecasts.
- Verify the relevant UK entities and permissions, distinguish deposit protection from safeguarding, and document compliance responsibilities.
- Test complete customer and payment journeys, including exceptions and reconciliation, before treating an integration as ready to launch.
- Validate service commitments, liability provisions and practical exit arrangements against written proposals and contractual terms before signing.
1.1 Compare UK BaaS providers and platforms
UK BaaS providers offer different foundations for embedded financial products. ClearBank and Griffin provide banking infrastructure under their own banking licences. Modulr supplies regulated e-money accounts and payment services. Railsr combines an embedded-finance platform with regulated issuing services, while Weavr packages financial functionality supplied through a regulated partner. The right shortlist therefore depends on whether your product needs bank deposits, payment accounts, card issuing or a managed combination.
ClearBank Limited (FRN 754568) and Griffin Bank Ltd (FRN 970920) appear on the PRA's list of UK banks authorised to accept deposits. That distinction matters: an account number and sort code alone do not establish whether a customer holds a bank deposit or electronic money.
Provider | Target customers | UK account capabilities | Payment rails | Card issuing | Delivery model |
|---|---|---|---|---|---|
ClearBank | Established fintechs, financial institutions and platforms embedding banking products. | Branded current and savings accounts, plus operating accounts; eligibility and functionality depend on the account product. | UK payment scheme access, including Faster Payments and CHAPS; confirm the scheme coverage of the selected account. | Current-account documentation supports debit cards against accounts, but this does not establish an inclusive card-issuing package. Confirm issuer, processor and programme arrangements separately. | Direct banking infrastructure from ClearBank Limited, integrated into your customer proposition. See its embedded banking offering and account documentation. |
Griffin | Fintechs, payment platforms and businesses embedding savings or managing client funds. | Embedded bank accounts, savings accounts, safeguarding accounts and client money accounts. | Faster Payments and internal transfers; technical documentation specifies inbound Bacs credits and inbound CHAPS. Direct Debits can be taken from accounts, but collecting them from other banks is not supported. | Debit-card issuing is listed on its public roadmap; do not assume production availability. | Bank accounts and payment APIs supplied by Griffin Bank Ltd, with onboarding tools. See its product range, payment specifications and card roadmap. |
Modulr | Software platforms, lenders and businesses automating collections, supplier payments or payroll. | E-money payment accounts supporting embedded payment flows and reconciliation. | Faster Payments, Bacs and CHAPS infrastructure. Available payment directions and additional services depend on the contracted configuration. | Physical and virtual cards; Visa and Mastercard capabilities are advertised, subject to programme selection. | API and portal delivery. Modulr's disclosures identify Modulr Finance Limited (FRN 900699) as an EMD agent of Modulr FS Limited (FRN 900573), which issues UK e-money accounts. See its entity disclosures, payment types and card offering. |
Railsr | Fintechs and brands building account, wallet and card propositions. | E-money accounts and wallets; obtain confirmation of current UK account identifiers and programme availability. | UK payment arrangements require programme-specific confirmation; do not infer a complete rail set from the platform's global offering. | Card programmes are advertised; confirm current UK scheme, issuer and physical or virtual options. | Embedded-finance platform. Published UK end-user terms identify PayrNet Limited, trading as Railsr (FRN 900594), as the EMI. Confirm the separate platform contracting entity. Onboarding restriction: Railsr's website states that new agents or distributors cannot be onboarded without prior written FCA consent. Confirm the current regulatory requirements and whether any necessary consent covers your proposed arrangement before shortlisting. See the platform overview and onboarding notice and published issuer terms. |
Weavr | Software businesses embedding expenses, employee benefits, accounts payable or other B2B payment workflows. | Managed payment accounts through its issuing partner, rather than deposits at Weavr. | GBP Faster Payments; other currencies and transfer methods depend on the configured programme. | UK Mastercard cards issued by Paynetics UK. | Packaged embedded-finance platform. Weavr's disclosures identify Weavr Ltd as a distributor of Paynetics UK Limited (FRN 942777), which supplies regulated UK accounts and cards. See its partner disclosures and transfer documentation. |
The following best-fit assessments reflect those capabilities, rather than an overall ranking:
- ClearBank: A strong candidate for established businesses seeking branded deposit products and banking infrastructure. Account-specific restrictions and separate card arrangements can materially affect the proposition.
- Griffin: A useful shortlist choice for embedded savings, account infrastructure and client-fund use cases. Inbound-only CHAPS and Bacs credit support, together with unconfirmed live card issuing, limit its suitability for some transactional products.
- Modulr: Well suited to payment automation and account-linked card programmes. Its e-money model does not supply a bank deposit product, and scheme participation does not mean every payment function is enabled by default.
- Railsr: Potentially suitable for a combined wallet-and-card proposition. Treat it as a conditional shortlist entry until the current UK product schedule, contracting entities and onboarding eligibility, including any required FCA consent, are confirmed.
- Weavr: A good fit for software businesses seeking packaged financial workflows. Product scope depends on Weavr's configuration and Paynetics' issuing terms, creating an additional provider relationship to assess.
Verification status: Provider disclosures were reviewed on 3 November 2026. The EMI and agent details above reflect published provider or issuer disclosures, not independently verified live FCA records. The Financial Services Register could not be retrieved during this review. Current permissions, requirements and relevant agent relationships for Modulr FS Limited (FRN 900573), Modulr Finance Limited (FRN 900699), PayrNet Limited (FRN 900594) and Paynetics UK Limited (FRN 942777) therefore remain a pre-publication verification requirement. Railsr's onboarding restriction is reported from its website; its current regulatory application also requires confirmation.
Once the required account type, payment directions and issuing model are clear, compare commercial proposals for the same service configuration. Otherwise, a lower platform fee may cover a materially narrower product.
1.2 Pricing, minimum commitments and total cost
Compare BaaS providers using the total cost of delivering your proposed product at realistic volumes. A monthly platform subscription, a minimum usage commitment and a transaction tariff are different charging mechanisms. Establish which charges are additive and which count towards a minimum before comparing quotations.
The following public pricing provides starting points, reviewed on 3 November 2026. It does not establish a like-for-like price ranking: banking infrastructure, payment automation and packaged embedded-finance programmes include different services.
Provider | Published pricing position | Implication for your budget |
|---|---|---|
ClearBank | Its embedded banking page directs prospective partners to sales without publishing a complete programme tariff. | Request an itemised quotation covering implementation, account charges, payment fees and minimum commitments. Do not interpret unpublished fees as zero. |
Griffin | Platform banking pricing lists onboarding from GBP 15,000 and monthly minimum-spend packages of GBP 4,000, GBP 6,000 and GBP 10,000, plus custom enterprise pricing. Eligible account, payment and onboarding usage draws down the package. | The lowest published package implies GBP 63,000 for onboarding and 12 monthly minimums, before additional charges: GBP 15,000 plus 12 payments of GBP 4,000. This assumes the starting onboarding fee and a full year of billing. Its separate business-account tariff is not the embedded platform price. |
Modulr | Modulr offers custom platform pricing alongside published business payment plans. | Obtain a quotation for your embedded account or card programme. Standard payroll and accounts-payable subscriptions should not be used as a proxy for the cost of serving your own end customers. |
Railsr | Its public website describes subscription stages but does not provide a complete current UK production tariff. | Request current setup fees, recurring commitments and account, payment and card charges. Free testing offers do not establish production pricing or entitlement to launch. |
Weavr | Launch pricing displays GBP 1,947 per month for approved B2B payment use cases in the UK and EU. Consumer payments are listed under Scale, which requires a pricing discussion. The footnote excludes initial setup, financial-product usage and compliance-service charges, while the plan description mentions included account and payment usage thresholds. | The displayed Launch subscription totals GBP 23,364 over 12 months, before extras. Confirm that your use case qualifies for Launch and obtain a written allowance schedule resolving which usage is included, which is separately billed and when overage charges apply. |
Model minimum commitments month by month. A minimum spend normally creates a billing floor against specified eligible charges; a platform subscription may instead sit on top of all usage fees. The contract's fee schedule must define the arrangement. Confirm whether unused allowances expire, which services count towards the minimum, and whether discounts apply to all transactions or only volumes above each threshold.
For illustration, a GBP 3,500 monthly minimum with GBP 2,000 of eligible usage produces a GBP 3,500 charge, plus any excluded fees. If the same GBP 3,500 is an additive platform subscription, the equivalent bill is GBP 5,500. These are hypothetical charging structures, not additional provider quotations.
Require each proposal to address the same cost categories:
- Setup and implementation: Programme onboarding, configuration, card design, certification and professional services. Identify payment milestones, refundable amounts and charges for changes to the agreed scope.
- Recurring charges: Platform subscriptions, programme-management fees, support packages and charges per open or active account. Define "active" and establish whether dormant accounts remain billable.
- Payment usage: Separate inbound and outbound Faster Payments, Bacs, CHAPS and other required rails. Include returns, investigations, failed instructions, currency conversion margins and third-party charges where applicable.
- Cards: Virtual and physical issuance, manufacturing, delivery, replacement, processing, ATM use, disputes and scheme fees. Specify which issuer or processing charges are included in the platform price.
- Customer checks and servicing: Identity and business verification, repeat checks, manual reviews and ongoing monitoring. Budget for your own customer-support and reconciliation staff as well as provider charges.
- Tax and liquidity: Request the VAT treatment of each charge and include irrecoverable VAT where applicable. Record prefunding and reserve requirements separately: tied-up cash affects funding needs, even when it is not an expense.
Calculate first-year total cost as one-off expenditure plus the sum of monthly provider bills, separately charged partner services, internal delivery and operating costs, and applicable irrecoverable tax. Avoid counting usage twice when it already draws down a monthly minimum. Show any contractual interest, commission or interchange revenue separately, using the amount retained after deductions rather than gross revenue.
Run a delayed-launch case, a conservative adoption case and an expected-volume case. Confirm when billing starts, how long minimum commitments last, whether they increase during the term, and whether annual price uplifts apply. A discounted unit rate can still produce higher total expenditure if customer volumes fall below the committed level.
Finally, calculate cost per active customer using the same definition across all proposals. Assess revenue-sharing assumptions separately from the core cost case, particularly where returns depend on balances, interest rates or card spend. The resulting comparison should show both the cash required to launch and the recurring cost of operating the product, with compliance-service fees mapped to clearly assigned responsibilities.
1.3 Regulation, safeguarding and compliance responsibilities
A BaaS platform's brand is not a regulatory permission. Establish which legal entity accepts deposits, issues electronic money, provides payment services and issues cards for your UK programme. The technology supplier, commercial contracting party and regulated provider may be different entities. FCA authorisation covers specified activities; it does not automatically cover every product offered under a group's brand.
ClearBank and Griffin operate through UK banks. Modulr identifies Modulr FS Limited as its UK electronic money institution (EMI), with Modulr Finance Limited acting as an EMD agent. Weavr identifies Paynetics UK Limited as the issuer of its UK payment accounts and Mastercard cards, with Weavr Ltd acting as a distributor. These distinctions determine which entity owes the customer regulated obligations. See the PRA bank list, Modulr disclosures and Weavr disclosures.
Check the exact entity and firm reference number against the Financial Services Register, including permissions, limitations, requirements and relevant agent relationships. An authorised status alone does not establish unrestricted onboarding capacity. For example, the Railsr website displays a notice requiring prior written FCA consent to onboard new agents or distributors. Its current application to a proposed programme needs confirmation against the live regulatory record. Provider disclosures should not be presented as independent verification of current permissions.
Bank deposits and safeguarded funds provide different protection. The distinction should be explicit in customer terms and account descriptions:
Account model | Protection mechanism | Material limitation |
|---|---|---|
Eligible deposit at a UK-authorised bank | FSCS deposit protection is generally up to GBP 120,000 per eligible depositor, per authorised firm, following the increase on 1 December 2025. | Balances under the same banking licence are aggregated, including across different brands. Protection is not a separate allowance for every account or app; depositor and product eligibility must be established. |
E-money or relevant payment funds at a non-bank provider | Applicable safeguarding rules require protection through segregation or qualifying insurance or a comparable guarantee. | Safeguarding does not provide FSCS compensation for the EMI or payment institution's failure. Recovery can take time, and insolvency costs or a shortfall can reduce the amount returned. |
These distinctions follow the FSCS deposit rules and FCA guidance on non-bank payment providers. Do not describe an e-money balance as an FSCS-protected bank account merely because the issuer places safeguarded funds with a bank.
Safeguarding requires evidence, not just a policy statement. The UK framework includes the Payment Services Regulations 2017, Electronic Money Regulations 2011 and supplementary FCA rules effective from 7 May 2026. Relevant firms face requirements covering reconciliation, safeguarding records, reporting, audits and resolution information. Ask which safeguarding method applies, where relevant funds are held, how customer entitlements are recorded and how discrepancies are resolved. Request evidence of applicable audit findings and remediation, rather than assuming that authorisation proves every control is operating effectively. The FCA safeguarding guidance explains the current framework.
Your own regulatory position depends on your activities. A software-only role, e-money distribution and providing payment services as an agent are different arrangements. An agent provides its principal's services and must have the required registration; distributor status does not itself authorise independent payment services. If your business operates outside the agreed model, it may need its own authorisation or another valid legal basis. Document that perimeter assessment for the actual customer journey and movement of funds. See the FCA guidance on payment agents and e-money distributors.
Translate the operating model into a written responsibility schedule. For each activity, identify who performs it, who approves decisions, what evidence must be retained and where exceptions are escalated:
- Customer due diligence: Allocate identity and business verification, beneficial-ownership checks, risk classification, enhanced due diligence and account-acceptance decisions. Define when additional source-of-funds evidence is required.
- Financial-crime controls: Assign sanctions and politically exposed person screening, transaction monitoring, alert investigation, periodic reviews and suspicious-activity escalation. Identify the responsible money laundering reporting officer and preserve each party's statutory reporting obligations.
- Fraud and payment disputes: Specify who can restrict an account, investigate unauthorised transactions and APP scams, assess the applicable reimbursement obligations and communicate decisions. Contractual cost allocation must be distinguished from duties owed to customers.
- Customer protection: Allocate approval of terms, account-protection disclosures, complaints handling and applicable Financial Ombudsman Service signposting. Customers should understand which entity provides each regulated service.
- Records and oversight: Define access to due-diligence records, monitoring evidence and customer communications, alongside retention, audit access and data-protection responsibilities.
APP scam reimbursement is separate from unauthorised-transaction protection. APP scams involve customers being deceived into authorising transfers. Mandatory protections cover qualifying individuals, microenterprises and charities making eligible UK Faster Payments or CHAPS transfers on or after 7 October 2024. The standard maximum is GBP 85,000 per claim, with reimbursement normally due within five business days; permitted investigation pauses can extend the process to 35 business days. Eligibility, reporting deadlines and exceptions apply, and an optional excess of up to GBP 100 may apply, subject to protections for vulnerable consumers. Identify the payment service provider responsible for reimbursing customers and assign ownership of claim intake, investigation, evidence exchange, customer communications and reimbursement funding. Document how costs are allocated between the parties without reducing customers' applicable rights. See the FCA's fraudulent-payments guidance and the PSR's APP reimbursement guidance.
Outsourcing operational checks does not remove the regulated provider's applicable obligations, nor does it eliminate your business's own duties. For products within the Consumer Duty's scope, responsibilities also depend on each firm's role and influence over customer outcomes. Relevant manufacturers and distributors must exchange information about product performance, value, communications and support; a B2B label alone should not substitute for a scope assessment. The FCA's Consumer Duty guidance explains this distribution-chain approach.
The resulting compliance model should identify the regulated provider, the customer's legal claim to funds and the owner of every material control. Those decisions establish which checks, approvals and records the product must support.
1.4 APIs, integration effort and launch readiness
A successful API connection is only one part of launching an embedded financial product. Your integration must support customer onboarding, account creation, payment authorisation, transaction tracking and reconciliation, including cases that require manual intervention. Compare BaaS platforms by how much of that workflow they provide and how much your engineering, finance and operations teams must build.
For businesses considering a packaged implementation, Framnex's financial infrastructure solutions include white-label banking, embedded finance, wallets, card programmes and payment orchestration. Its platform supports launching an individual capability and adding connected services as the product grows. Framnex supplies B2B software and infrastructure, while applicable licensed third-party partners perform regulated activities. For a UK launch, confirm which partners, account types and payment services are available for the proposed programme.
Start with a defined UK use case: the customers you will onboard, the accounts they need, the direction of each payment and any card functionality. An endpoint appearing in documentation does not establish that the corresponding service is enabled for your contracted programme.
Provider | Documented integration approach | Practical implication |
|---|---|---|
ClearBank | Its UK developer guide describes simulation access supplied during onboarding, with an authentication profile including a digital certificate and API token. | Plan for credential management and signed requests as part of the build. Confirm access to the specific account and payment products your proposition requires. See ClearBank's getting-started guide. |
Griffin | A self-service sandbox supports early technical evaluation. Production onboarding also includes commercial, compliance, product and marketing reviews. | Engineering can assess the API before commercial onboarding is complete, but sandbox success does not constitute approval to launch. See Griffin's sandbox explanation. |
Modulr | The default sandbox is configured for a direct customer. Partner functionality and features such as Direct Debit collections or virtual cards require enablement. Production uses HMAC request authentication. | Request a sandbox matching your partner model and test production-compatible authentication early. Additional product onboarding may be necessary. See Modulr's sandbox guide. |
Railsr | Its website advertises sandbox and live API stages with differing usage restrictions. | Obtain current UK documentation, enabled features and production acceptance criteria directly. Public testing offers do not establish current onboarding eligibility. See the Railsr platform information. |
Weavr | APIs and SDKs cover accounts, cards and payments. Sandbox access is arranged with its team; moving an app to production requires business verification and integration review. | Assess which supplied components fit your customer journey. Allow for Weavr's approval process, including subsequent configuration changes promoted from sandbox to live. See its developer documentation and go-live process. |
Test a complete money movement, including exceptions. A useful proof of concept should create a customer, complete the applicable verification flow, open an account, receive funds, make a payment and reconcile the resulting entries. It should also demonstrate what happens when verification needs more information, a payment is rejected or the application loses its connection after submitting an instruction.
- Payment coverage: Confirm inbound and outbound support separately for Faster Payments, Bacs and CHAPS. Check transaction limits, cut-off times, beneficiary validation and Confirmation of Payee where relevant. Bacs credit receipt and Direct Debit collection are separate capabilities.
- Duplicate prevention: Test the provider's documented retry and idempotency behaviour, which should prevent a repeated instruction from creating an unintended second payment. A timeout must not automatically trigger a new payment instruction.
- Transaction status: Map submitted, pending, completed, rejected and returned payments to appropriate customer messages and accounting treatment. An accepted API request does not necessarily mean the beneficiary has received funds.
- Reconciliation: Match your internal ledger against provider transactions, balances, fees and statements. Test available versus booked balances, card authorisation holds, reversals and unmatched receipts where those features apply.
- Security and approvals: Validate secure credential storage, access permissions, payment-approval workflows and applicable customer authentication. For cards, establish how sensitive card data is handled and which security obligations remain with your business.
Webhooks, which notify your application of events, require particular attention. Griffin documents that notifications can arrive more than once or out of order and provides an Events API to recover missed events. Your integration therefore needs to recognise duplicates and retrieve authoritative transaction information when notifications are missing. These behaviours should be demonstrated in testing, not left as assumptions. See Griffin's webhook guidance.
Separate technical completion from production approval. Ask each provider which outcomes its sandbox simulates, which checks require production testing and which services need partner or scheme approval. Artificial balances cannot prove real settlement timing or the behaviour of every external bank. Build the delivery plan around named dependencies and acceptance criteria, with separate milestones for commercial onboarding, technical testing, operational preparation and production access.
Published timelines should be treated as conditional estimates. For example, Griffin's onboarding page aims for launch within eight weeks assuming checks proceed smoothly. That is not an unconditional delivery commitment. Assign internal owners for engineering, financial-crime operations, reconciliation and customer support, and confirm which implementation support the provider supplies.
Before releasing the product broadly, complete an approved, limited production pilot. Confirm that real payment statuses reconcile, customer-support staff can investigate exceptions, required approvals are recorded and the team can pause new activity if balances or transaction records diverge. Launch readiness is demonstrated when both the technology and the operating team can manage customer money accurately.
1.5 Reliability, contractual protection and exit arrangements
A BaaS provider's reliability should be assessed against the financial services your customers depend on: accessing balances, receiving funds, making payments and using cards. An available API does not necessarily mean every payment rail or issuing service is functioning. Assess service performance, contractual remedies and the feasibility of moving the programme together.
Request evidence of recovery, not just an uptime percentage. Review historical incidents, their customer impact, restoration times and completed corrective actions. Ask for relevant disaster-recovery and capacity-test results, including how the provider handles peak payment volumes and clears transaction backlogs after an interruption. A public status page is useful evidence, but it may aggregate services or omit programme-specific incidents.
The FCA's operational-resilience framework requires firms within scope to identify important business services, set impact tolerances and test their ability to remain within them during severe but plausible disruption. An impact tolerance concerns the maximum tolerable disruption before unacceptable harm occurs; it is not the same as a contractual uptime commitment or a promise to compensate your business.
Map dependencies across the platform, regulated account provider, settlement bank, card issuer and processor. Establish who coordinates recovery when a partner fails. Two suppliers do not provide independent redundancy if they rely on the same underlying infrastructure. The FCA similarly emphasises understanding the resources and third parties needed to deliver important services in its outsourcing guidance.
Check the financial viability of the provider and critical regulated partners. Review their latest available accounts, any accompanying auditor's report and material going-concern disclosures. Assess liquidity, recurring losses and reliance on further funding or parent-company support. Where published accounts are dated or incomplete, request current financial information and clarification of material changes. Use the findings to inform provider selection, ongoing monitoring and exit planning.
Contract area | What to establish | Commercial significance |
|---|---|---|
Service-level agreement | Covered services, measurement periods, availability calculations, payment-processing targets and exclusions for maintenance or third-party failures. | A broad availability figure can conceal an outage affecting a critical payment function. Distinguish API response time from payment execution and settlement. |
Incident management | Severity definitions, support hours, acknowledgement and escalation targets, update frequency and delivery of root-cause reports. | A fast acknowledgement is not a restoration commitment. Your operations team needs timely information to manage customer funds and communications. |
Remedies and liability | Service-credit calculations, claim deadlines, liability caps, exclusions and whether credits are the exclusive remedy for service failures. | A fee credit may cover only a small part of the loss from disrupted payroll, failed collections or unavailable cards. |
Suspension and termination | Triggers, notice, cure periods, emergency powers and rights following repeated material service failures. | Understand when the provider can stop onboarding or transactions, and what happens to existing customers and balances. |
Changes and subcontracting | Notice and approval arrangements for material service, API, issuer or subcontractor changes, together with any associated termination rights. | A change in the delivery chain can alter your operating model even when the platform brand remains unchanged. |
Transition assistance | Data-export scope, continued access, migration support, charges and the duration of assistance after notice or termination. | A termination right has limited practical value if the business cannot recover records or move customers in an orderly way. |
Review these provisions in the actual master services agreement and incorporated schedules, including any separate account or issuing terms. Establish which document takes precedence if provisions conflict. Have legal counsel assess liability caps and indemnities against plausible losses, including misdirected payments, data incidents and failures by subcontractors. Identify any customer-facing liabilities your business could incur without a corresponding right of recovery from the provider.
Suspension rights need particular care. A regulated provider may need to act immediately because of suspected financial crime, a legal obligation or a regulatory direction. Seek clear escalation and communication arrangements where legally permitted, rather than assuming notice can always be guaranteed. The agreement should distinguish restrictions on an individual account from suspension of an entire programme.
Design an exit that works operationally. Prepare both an orderly migration plan and a stressed-exit plan for prolonged disruption, withdrawal of a critical partner or provider failure. The PRA's outsourcing guidance treats business continuity and exit planning as material risk-management considerations for firms within its scope.
- Customer money: Specify how balances will be reconciled and transferred or returned, with responsibility for pending payments, unsettled card transactions, refunds and disputes.
- Accounts and cards: Do not assume account numbers, sort codes, payment mandates, card numbers or wallet tokens are portable. Establish which identifiers must change and which customer actions are required.
- Records: Secure usable exports of transaction history, statements, customer records and relevant compliance evidence, subject to lawful access and retention requirements. Confirm whether a replacement provider will accept existing verification evidence or require fresh checks.
- Transition resources: Assign owners, milestones, customer communications and reconciliation controls. Budget for parallel operation, migration support and any continuing minimum commitments.
- Completion: Define when access ends, how residual balances and later claims are handled, and how data is retained or deleted after statutory obligations have been met.
Test the exit plan through a sample data export and a documented migration walkthrough. A backup provider is useful only if it has approved the required programme and can receive the relevant business. Contractual assistance cannot guarantee continuity during insolvency or regulatory intervention, so the plan should identify dependencies your business cannot control and the practical steps available if they fail.
1.6 Validate your shortlist before signing
Turn your shortlist into a comparison of written proposals for the same UK programme. The strongest BaaS provider is the one that can support your required product, demonstrate workable delivery and offer acceptable commercial terms. A sales demonstration or indicative quotation alone does not establish those conditions.
Send each shortlisted provider a common requirements brief. Define your customer types and jurisdictions, account model, payment directions, card requirements, forecast active accounts, transaction volumes and expected balances. Include your launch window, internal resources and proposed division of compliance responsibilities. Ask providers to identify exclusions and partner dependencies explicitly.
- Confirm eligibility and the regulated delivery chain. Obtain written confirmation that the provider can onboard your business sector and serve the proposed UK customers. Identify the contracting entity, account provider, card issuer and any regulated partners. Match legal names and firm reference numbers to the FCA's authorisation-checking guidance and relevant register records, including permissions, restrictions and agent relationships. Record the date and evidence of each check; unresolved regulatory questions are a condition to resolve, not a scoring disadvantage to offset with price.
- Request an itemised commercial proposal. Require setup charges, subscriptions, minimum commitments, usage tariffs, partner fees and applicable tax treatment. Ask the provider to calculate bills against your conservative and expected-volume scenarios, including delayed launch. Confirm the quotation's validity period, billing commencement date and which assumptions would trigger repricing.
- Demonstrate your actual customer journey. Arrange a technical session with the implementation team and test a representative flow in the appropriate sandbox configuration. Cover onboarding, account creation, incoming funds, outgoing payments and reconciliation. Include rejected instructions, duplicate submissions and missing notifications. Record which capabilities are demonstrated, which require further approval and which remain roadmap items.
- Validate the operating model. Obtain a responsibility schedule covering customer checks, financial-crime alerts, fraud, complaints, reconciliation and support. Identify the staff and systems your business must supply. Request a delivery plan with named owners, dependencies and production acceptance criteria, rather than relying on a headline launch estimate.
- Review service evidence and references. Request relevant incident history, recovery-test summaries and customer references with comparable UK account or payment flows. Ask references about implementation delays, exception handling and support during disruption. Treat reference calls as supporting evidence alongside contractual commitments and documented controls.
- Reconcile the proposal with the contract. Have finance, legal, compliance and engineering review the same final document set. Ensure agreed services, allowances, responsibilities, service levels and transition assistance appear in the binding agreement or incorporated schedules. Resolve discrepancies between sales statements and contractual exclusions before approval.
Use a decision matrix that separates mandatory requirements from preferences. Regulatory eligibility, essential payment capabilities and an affordable minimum commitment should be pass-or-fail conditions. Score qualifying providers on total cost, implementation effort, operational support and contractual protection, using weights agreed before reviewing final offers.
Label every material finding as verified, contractually committed or unresolved. A planned feature should not receive the same score as a live service available to your programme. Where evidence remains incomplete, assign an owner and deadline and state whether the gap prevents selection, signing or production launch.
Approve the provider only when the decision record explains the expected total cost, delivery dependencies, residual risks and practical exit route. Any remaining conditions should be explicit, with agreed consequences if they are not met. This gives the business a defensible purchasing decision and a clear basis for holding both parties to the agreed scope.
Independent research
Ask AI whether Framnex fits your business.
Research Framnex with your preferred AI assistant and see where the platform may fit your client base, product and launch model.
The prompt will be prefilled. Review it before sending.