The programme runs on licensed EU banking infrastructure from our vetted network, selected for your model at onboarding. Crosswire designs it, negotiates the commercials and coordinates onboarding through go-live - so you can embed banking without the licensing burden.
Paid by the infrastructure partners - no Crosswire margin on the infrastructure price. Advisory or implementation work is quoted separately.
Your brand, one programme, an account for every user - virtual accounts in your users' names, not pooled.
Last reviewed: 19 August 2026
Pick your capabilities, design your card and set your own pricing. The model shows what the programme would earn your platform each month, over the first year, line by line. Share the exact model you built with a permalink.
User wallets and fiat accounts under one programme.
Seller payouts and sub-accounts with clean reconciliation.
Embedded IBANs without holding a banking licence.
Treasury, multi-currency accounts and optional cards.
IBAN-as-a-service, virtual IBANs for platforms and card issuing for platforms, delivered as one programme rather than three integrations.
Virtual accounts in your users’ names - not pooled.
EUR, USD, GBP and more, settled in one ledger.
Send and receive across Europe and globally.
White-label virtual and physical cards issued on a licensed partner's BIN, tied to user balances.
Funds move on rails, not on batch windows.
Open, create, fund and reconcile from your stack.
EU card issuing is priced from its own schedule in EUR, quoted per programme rather than from a list on this page. Each line is billed on its own unit, and the lines are never added together into a single figure or a rate.
BIN registration where you are eligible, and dedicated card branding. One-off.
Card maintenance, charged monthly on active cards.
Card issuance, transactions and 3DS authorisation, each on its own unit.
Applied on card FX usage, never folded into a single rate.
Where one applies, creditable against usage.
Card issuing prices standalone and as a tagged line set inside a BaaS programme offer. Prices are subject to onboarding, verification and network approval. US card programmes are priced from a separate schedule in US dollars and the two are never combined into one total. BIN registration is available to regulated entities only, and that condition travels with the line wherever it is quoted.
The US programme is quoted from its own schedule in USD, and the schedule travels with your offer rather than sitting on this page. What is public is the structure.
EU and US programmes price from separate schedules and are never combined into one total.
A one-off, set at scoping against programme scale.
Monthly, on the accounts your programme actually runs.
Payments, verification and returns, each billed on its own unit.
Applied on converted value, never added into a headline rate.
Creditable against usage: usage is billed, the minimum applies where usage falls short.
Manual review and enhanced due diligence, and any operational or fraud reserve, are quoted or agreed separately and never carry a standing price. The Master FBO and programme account is a structural line set on the offer.
The licensed provider holds the licence, operates the accounts, ledger and rails, and holds the client contract. Crosswire designs the programme, negotiates commercials, coordinates onboarding and stays as the point of contact. Providers are selected and locked by Crosswire, and named to you when your provider application is prepared for signature.
Users, volumes, regions and what you want to offer - accounts, cards, payments.
The right provider, compliance scope and negotiated pricing for your model, matched across the vetted network. You contract with the licensed provider.
Integrate the API, launch to your users. We stay in as your point of contact.
A white-label front end can be part of the programme: your brand, your users, a working interface you did not have to build. Test a market in weeks rather than committing an engineering roadmap to it, then move to your own interface later if the market answers.
Typically two to four weeks, subject to scope and provider onboarding.
It is an option within Banking-as-a-Service, not a separate product. Pricing is quoted with your offer.
We are not a BaaS provider. We are the orchestration layer that selects an EU BaaS programme for your model, negotiates it and coordinates it to go-live.
The programme is matched to your model across a vetted network of licensed EU providers, not routed to whoever we signed first.
Banking, acquiring and digital assets - not just BaaS - through one team.
Exchanges, marketplaces and payment platforms. We place them routinely.
The white-label front-end route launches typically two to four weeks, subject to scope and provider onboarding.
Crosswire is paid by the infrastructure partners, so the infrastructure price carries no Crosswire margin. Advisory or implementation work is quoted separately and agreed in advance.
Anonymised, labelled as an achieved outcome and reported against a defined methodology.
Full API-driven Banking as a Service infrastructure with dedicated user accounts, cards and real-time, 24/7 crypto settlement. Replacing a previous multi-provider, hard coded legacy vIBAN setup.
One figure is withheld from this card until its measurement period and source are on file. It is named in the methodology below rather than quietly dropped.
Banking-as-a-Service lets a company offer regulated banking products to its own users without holding a banking licence. A licensed institution provides the accounts, IBANs, payment rails and card issuing; the platform provides the brand, the interface and the customer relationship, and integrates over an API.
No. Under a Banking-as-a-Service programme the licensed institution holds the permissions and the regulatory obligations for the accounts. Your platform still carries duties: onboarding standards, monitoring obligations and contractual commitments defined in the programme. The scope of those duties is set during programme design, before you contract.
A business account serves your company. A Banking-as-a-Service programme lets you issue accounts to your users, in their names, under your brand, controlled programmatically. You get an API, a rulebook and an operating perimeter rather than a single account, and you take on programme-level responsibilities in exchange.
Typically dedicated multi-currency IBAN accounts in their own names, SEPA and SWIFT payments in and out, currency conversion, and virtual or physical cards where the programme includes issuing. Everything is available programmatically, so accounts can be opened, funded, reconciled and closed from your own systems.
Yes. A white-label front end can be included in the programme, so your users get a branded interface you do not have to build. Timelines are typically two to four weeks, subject to scope and provider onboarding. It suits platforms testing a market or without frontend engineering to spare, and it is an option within BaaS rather than a separate product.
Timelines are driven by three things: your regulatory footprint, the depth of diligence the licensed partner runs on your model, and how much of the integration you build in parallel. Programme design takes days. Diligence and contracting dominate the calendar. Integration is usually not the bottleneck.
Programmes are priced per programme, not from a list. The structure is consistent: a setup fee, recurring platform or per-account fees, per-transaction pricing on payments and cards, FX margin, and a monthly minimum. Volume, risk profile and capability mix drive the numbers. Model your own economics in the BaaS revenue model.
Yes, on a narrower set of programmes and with deeper diligence. Licensed partners assess licensing status, source of funds controls, transaction monitoring and the jurisdictions you serve. Crypto exchanges, marketplaces and payment platforms are models Crosswire places routinely, which is why the design work happens before any application.
A BIN is the card range a scheme allocates to a licensed issuer. BIN sponsorship means an issuer lets your programme issue cards on its BIN under its scheme membership, so you can put branded cards in front of users without becoming a principal member of Visa or Mastercard yourself.
The licensed institution does. Funds sit under its permissions and safeguarding arrangements, and it holds the client contract for the accounts. Crosswire designs the programme, negotiates the commercials and coordinates onboarding; it never takes custody of client funds at any point in the flow.
Programmes are renegotiated as volume changes, and pricing tiers usually move with it. If the model outgrows the partner entirely, the options are adding a second programme for redundancy or capability, migrating to a larger institution, or pursuing your own licence. Crosswire runs that comparison with you.
Model your own programme economics in the BaaS revenue model
Cost shape, timelines and the obligations you keep either way.
Setup, per-account, per-transaction, FX margin and minimums explained.
What licensed partners assess, and why dedicated IBANs are the norm.
One is the customer outcome, the other is the licensed supply underneath.
How branded cards ship without joining a scheme as a principal member.
IBAN-as-a-service on its own, where accounts are the whole requirement.
See virtual IBAN infrastructureTell us the programme you want. We prepare a tailored BaaS offer - modules, indicative programme economics and a clear path to go-live - and email it to you.
Indicative programme economics. Commercial assumptions reflect the selected programme design and applicable partner frameworks. Subject to KYC/KYB. Paid by the infrastructure partners - no Crosswire margin on the infrastructure price. Advisory or implementation work is quoted separately.
No prices shown on this page - your offer is prepared and sent to your work email.
Your provider is selected and locked by Crosswire - and named when your application is prepared for signature. See the network →