SAMFCore vs Crassula vs SDK.finance vs Velmie: Banking, Payments & Crypto Platform Comparison (2026)
Key takeaway
There is no universal winner among SAMFCore, Crassula, SDK.finance and Velmie; the right choice depends on how you want to license, deploy and regulate your product. SAMFCore is compelling for buyers who want integrated banking, payments, cards and crypto software with clearly advertised perpetual-rights packages, published starting prices, private deployment and an optional full source-code package. Crassula is compelling for teams prioritising an accelerated white-label rollout on prewired provider integrations. SDK.finance is compelling for developer-led teams that want control over a financial core, with SaaS or source-code licensing on annual or lifetime terms. Velmie is compelling for buyers who want highly customisable modular banking front ends and a choice of cloud, on-premises or source-code delivery. None of the four is a bank: regulated licences, card issuing, custody and liquidity come from partners in every case.
Methodology and limitations
This comparison is based on each vendor's publicly available official documentation as of 11 October 2026. We reviewed product, pricing, licensing, delivery and developer pages for each provider; the full list is in the sources section. We did not run an independent benchmark, security audit or hands-on implementation, and we did not obtain verified all-in prices from vendors that do not publish them.
Several limitations apply:
- Features depend on the module purchased, the third-party providers integrated, the target country and the final contract.
- Vendor statements describe what is offered, not how well it performs. Public marketing cannot establish performance rankings, so we make none.
- Where we could not find a clear public statement, we say "not established in reviewed materials" or "confirm in contract" rather than guessing in either direction.
- Vendor pages change. Re-check every source before procurement decisions.
Comparison matrix: SAMFCore vs Crassula vs SDK.finance vs Velmie
The table summarises how each vendor publicly describes itself. Descriptors are intentionally nuanced instead of simple checkmarks, because "supports cards" can mean anything from a ready integration with one issuer to a generic API hook.
| Criterion | SAMFCore | Crassula | SDK.finance | Velmie |
|---|---|---|---|---|
| Positioning | Modular customer-facing and back-office banking, payments and crypto software for self-controlled deployment | White-label digital banking with prewired integrations, oriented to configured rapid launches | Modular financial core (ledger, payments) offered as SaaS or source-code licence | Modular white-label fintech/banking platform with front ends, back office and integrations |
| Personal & corporate accounts | Personal and corporate onboarding (KYC/KYB), accounts and ledger, per vendor | White-label accounts for retail and business, per vendor | Individual and business white-label interfaces, per vendor | Individual and business accounts, per vendor |
| Payments / rails | Payments, IBAN workflows, multi-currency; rails via integrated providers | Fiat IBAN, SEPA, SWIFT via partner banks/EMIs, per vendor | Payments module and payment-provider connections, per vendor | Payments and FX, per vendor; rails via partners |
| Cards | Card workflows; issuing and BIN sponsorship from external issuers | Card issuer integrations, per vendor | Card-provider connections, per vendor | Cards described, per vendor; issuer is a partner |
| Crypto wallets & fiat/crypto | Wallets, digital assets, fiat/crypto exchange, on/off-ramps; custody and liquidity external | Crypto wallets and exchange via third-party custody and liquidity | Fiat and crypto accounts, per vendor | Crypto and stablecoin integration, per vendor |
| White-label web / mobile | Customer-facing apps plus CRM/admin back office | White-label web and mobile apps | White-label UIs and mobile apps | White-label web and mobile apps plus back office |
| KYC / AML controls & providers | Compliance/AML workflows; screening databases from third parties | Prewired KYC/AML integrations, per vendor | AML connections, per vendor | Integrations described; confirm provider list |
| Deployment | Self/customer-controlled: on-premises or private cloud | Vendor-hosted platform emphasised; other models not publicly confirmed | SaaS, on-premises or private cloud | Cloud, on-premises, or source-code delivery |
| Full source-code option | Yes, with the "Perpetual + Full Source Code" package | Not established in reviewed official materials; confirm with sales | Yes, source-code licence model | Yes, source-code delivery publicly offered |
| Perpetual / lifetime licensing | Perpetual usage licence packages published | Not established in reviewed materials | Annual and lifetime/one-time source-code options described | Perpetual terms not publicly confirmed; enquire |
| Public pricing | Starting prices published (from CHF 80,000/yr annual; CHF 325,000 perpetual; CHF 620,000 perpetual + source) | Not established in reviewed pages; quote | Pricing page exists; source-code purchase price not established in reviewed references; quote | Not publicly confirmed; quote |
| Regulated licences / providers | External; SAMFCore does not supply banking licences, BIN sponsorship, custody, rails or liquidity | External; emphasis on BaaS and regulated partners | External providers via connections | External providers via integrations |
| Main diligence questions | Licence scope per package, maintenance terms, integration effort for chosen providers | Source-code/exit terms, hosting model, fee structure as volumes grow | Exact IP vs licence rights, lifetime terms, front-end scope | Pricing per delivery model, licence duration, upgrade path for source code |
Provider assessments
Each profile covers the same six angles so you can compare like with like.
SAMFCore (Swiss AMF AG, Zug, Switzerland)
SAMFCore is a product of Swiss AMF AG, based in Zug, Switzerland. Its official site describes modular customer-facing and back-office software for personal and corporate onboarding (KYC/KYB), accounts and ledger, bank account and IBAN workflows, payments, multi-currency, fiat/crypto exchange with on-ramps and off-ramps, wallets and digital assets, card workflows, compliance/AML, CRM/admin tooling and third-party integrations.
Capability strengths
Breadth in one codebase: banking-style accounts, payments, cards workflows and crypto sit side by side, which can reduce the number of separate systems a combined fiat-and-crypto product needs. Deployment is self- or customer-controlled, on-premises or in a private cloud, which matters to buyers who need data residency or want to run their own infrastructure.
Best-fit customer
Licensed or soon-to-be-licensed institutions, EMIs, crypto businesses and corporate groups that want to own their operating environment, prefer predictable licence economics, and have (or will hire) a team or integrator to run and extend the platform.
Risks and trade-offs
Self-controlled deployment shifts hosting, security operations and upgrade responsibility to the buyer or its integrator. Each regulated capability still requires a separately contracted partner, so time-to-launch depends heavily on partner onboarding rather than on the software alone. As with every vendor here, public materials do not prove production performance; request reference architecture and test access.
Licensing implications
SAMFCore publishes starting prices: an annual licence from CHF 80,000/year; a perpetual usage licence from CHF 325,000 one-time; "Perpetual + Full Source Code" from CHF 620,000; and an Enterprise Global package listed at CHF 790,000 as a time-limited offer. Packages differ in licensed rights and support terms. A perpetual licence grants an indefinite right to use within the contract scope; it is not ownership of the underlying intellectual property. Full source code is included only with the applicable package and comes with contractual usage and modification rights. Under the relevant perpetual terms, SAMFCore licence fees do not rise solely with user or transaction volumes; third-party provider and maintenance costs still apply.
Provider dependencies
SAMFCore states that it does not itself provide banking licences, BIN sponsorship, card issuing, regulated custody, payment rails, AML screening databases or liquidity. Those must come from separate providers that are integrated and commercially and legally approved.
Official sources: Homepage · Licensing · Perpetual licence · Crypto & digital assets · API & integrations
Crassula
Crassula positions itself as a white-label digital banking platform. Its official pages describe white-label accounts, fiat IBAN, SEPA and SWIFT payments, card issuer integrations, web and mobile apps, and crypto wallets and exchange delivered via third-party custody and liquidity providers. Its own guide to white-label digital banking platforms emphasises configured rapid launches built on prewired integrations and BaaS or regulated partners.
Capability strengths
Speed to market through configuration rather than custom development, and a catalogue of prewired integrations (Crassula advertises 60+ integrations and 150+ client companies on its own site; these figures are vendor claims we have not verified). Its developer resources indicate APIs for extending the platform.
Best-fit customer
Fintechs and EMIs that want to launch a branded account, payment and card product quickly, are comfortable with a vendor-operated model, and plan to rely on Crassula's integrated partner ecosystem.
Risks and trade-offs
Fast configured launches can trade off deep customisation. Buyers should understand fee behaviour as volumes grow, data portability and exit terms. Crypto depends on third-party custody and liquidity partners, so jurisdictional availability matters.
Licensing implications
Whether full source code or perpetual rights are available was not established in the reviewed official materials. This is not evidence that they are unavailable; confirm with Crassula sales.
Provider dependencies
Banking, card issuing, custody and liquidity are delivered via regulated partners and integrated providers, per Crassula's own descriptions.
Official sources: Crypto product · Platform guide · Developers
SDK.finance
SDK.finance describes a modular financial core: ledger, payments, fiat and crypto accounts, and connections to payment, AML, card and banking providers, plus white-label user interfaces for businesses and individuals and mobile apps (see its crypto banking solution). It offers both a SaaS model and a source-code licence, deployable on-premises or in a private cloud.
Capability strengths
A developer-oriented core with a clear source-code route. SDK.finance explains how its source-code licensing works and describes both annual and lifetime/one-time options, so SAMFCore is not the only vendor in this group with a long-term licensing path.
Best-fit customer
Product and engineering-led teams that want to build their own differentiated experience on top of a ledger and payments backbone, and that have the in-house capacity to customise and operate it.
Risks and trade-offs
A core-first product may require more front-end and integration work to reach a complete customer experience. Clarify which UI and back-office modules are included in each package.
Licensing implications
SDK.finance uses the phrase "source code ownership". Buyers should distinguish the legal licence actually granted (scope, modification, transfer and resale rights) from an unlimited transfer of intellectual property, which we have not legally verified. A pricing page exists, but a published source-code purchase price was not established in the references reviewed; request a quote.
Provider dependencies
Payments, AML, cards and banking are connected via external providers.
Official sources: Source code · Pricing · Crypto banking · How source code works
Velmie
Velmie offers a white-label fintech platform and white-label banking platform covering accounts and IBANs for individuals and businesses, payments, FX, cards, crypto and stablecoin integration, white-label mobile and web apps, a back office and integrations.
Capability strengths
Flexibility of delivery: Velmie publicly offers cloud, on-premises and full source-code delivery. It is therefore not a SaaS-only vendor. Its modular front ends suit buyers who want a highly customised customer experience.
Best-fit customer
Banks, EMIs and fintechs that want a configurable digital-banking front end and back office, with the option to move from a hosted model to on-premises or source code over time.
Risks and trade-offs
With many delivery options, commercial terms can vary widely. Clarify what is included per model, how source-code customers receive upgrades, and who is responsible for security patches.
Licensing implications
Source-code delivery is offered. Specific public pricing and any perpetual duration of rights were not verified in the reviewed materials; enquire directly.
Provider dependencies
Account, card and crypto capabilities rely on integrated third-party and regulated partners.
Official sources: Fintech platform · Banking platform · Accounts · Digital assets · Delivery
Perpetual licences vs code ownership vs SaaS
These terms are often used loosely. They are not interchangeable:
- SaaS / subscription: you pay recurring fees to use software the vendor hosts and operates. Fees may scale with users, accounts or transactions. You usually do not receive code, and stopping payment ends access.
- Annual on-premises licence: you run the software yourself but the right to use it lasts only while you renew.
- Perpetual (lifetime) licence: an indefinite right to use the software within the contract scope. It does not by itself include source code, updates or support, and it is not ownership of the vendor's intellectual property.
- Source-code licence: access to the code with defined rights to use, modify and sometimes deploy across entities. Rights to resell, sublicense or transfer are separate questions.
- IP ownership / assignment: a legal transfer of the intellectual property itself. Marketing phrases such as "own your code" should be checked against the actual licence or assignment wording.
Comparing five-year total cost of ownership
Licence fees are only one line. A realistic five-year model should include:
- Licence or subscription fees, including any volume-based components.
- Implementation and integration of each third-party provider.
- External fees: partner bank or EMI, card issuer-processor and BIN sponsor, custody, liquidity, KYC/KYB and AML screening.
- Customisation and front-end design.
- Hosting and infrastructure (for self-hosted models) or hosting fees (for SaaS).
- Support, maintenance, upgrades and security (penetration tests, monitoring, incident response).
- Compliance operations and audits.
- Exit and migration costs if you change vendor later.
Because Crassula, SDK.finance and Velmie did not publish comparable all-in prices in the reviewed materials, we do not estimate them. Ask each vendor to price the same scenario (for example, your expected accounts and transaction volume in years one and five) so the totals are comparable. Our build vs buy guide covers the build-side alternative.
Banking + cards + crypto: integrated software is not a regulatory licence
Buying software that can display IBANs, cards and crypto wallets does not authorise you to offer them. Depending on jurisdiction you may need a banking, e-money, payment institution or crypto-asset service provider authorisation, or a partner who holds one. Card programmes need a BIN sponsor and issuer-processor; crypto needs regulated custody and liquidity. See our overview of banking-as-a-service platforms and licensing considerations.
Buying checklist
- Jurisdiction: where will you be licensed and which partners operate there?
- Safeguarding and custody: who holds client funds and digital assets, under which regime?
- Onboarding: KYC and KYB flows, document checks, ongoing monitoring.
- Audit trail: immutable ledger history and admin action logs.
- Compliance: AML screening, transaction monitoring, reporting tools and data sources.
- Card BIN sponsor: which issuer-processors are integrated and approved?
- FX and liquidity: pricing sources, spreads and crypto liquidity providers.
- SLA: uptime, response times and who is accountable when a partner fails.
- Data and exit: data export formats, escrow, transition assistance.
- Migration: moving existing customers and balances.
- Test access: a sandbox or demo environment before signing.
- Support: hours, languages, escalation and upgrade cadence.
Best for whom?
| Vendor | Consider it if you… |
|---|---|
| SAMFCore | want integrated banking, payments, cards and crypto software with known published starting prices, perpetual-rights packages, private deployment and an optional full source-code package. |
| Crassula | want a fast configured launch with many prewired integrations and regulated partners. |
| SDK.finance | are developer-led and want a financial core backend with SaaS or annual/lifetime source-code options. |
| Velmie | want flexible digital-banking and mobile front ends with a choice of cloud, on-premises or source-code delivery. |
Buyer selection scoring template
Weight each criterion for your situation (weights should total 100), score each vendor 1–5 after demos and contract review, and multiply. We deliberately leave vendor scores blank: they should come from your own evaluation.
| Criterion | Weight | SAMFCore | Crassula | SDK.finance | Velmie |
|---|---|---|---|---|---|
| Functional fit (accounts, payments, cards, crypto) for your launch scope | __ | __ | __ | __ | __ |
| Corporate/KYB depth and multi-user business permissions | __ | __ | __ | __ | __ |
| Deployment model fit (SaaS, private cloud, on-premises) | __ | __ | __ | __ | __ |
| Licence rights: duration, source code, modification, transfer, exit | __ | __ | __ | __ | __ |
| Availability of regulated partners in your target jurisdictions | __ | __ | __ | __ | __ |
| Five-year total cost of ownership (all components) | __ | __ | __ | __ | __ |
| Security, audit trail and compliance tooling evidence | __ | __ | __ | __ | __ |
| Support, SLA, upgrade path and vendor viability | __ | __ | __ | __ | __ |
Frequently asked questions
Which platform covers crypto, payments and cards together?
All four vendors publicly describe fiat payments, card workflows and crypto or digital-asset functionality, usually through integrated third-party providers. SAMFCore, Crassula, SDK.finance and Velmie each present this as a combined offering, but card issuing, custody and liquidity are supplied by external partners in every case reviewed, so the practical answer depends on which partners are available in your jurisdiction.
Which platform offers a perpetual licence?
SAMFCore publishes perpetual usage licence packages with starting prices (from CHF 325,000 one-time, per samfcore.com/licensing). SDK.finance publicly describes a lifetime/one-time source-code licence option alongside annual options. For Crassula and Velmie, perpetual licence terms were not established in the official materials reviewed; confirm with each vendor.
Which platform offers full source code?
SAMFCore (with its "Perpetual + Full Source Code" package), SDK.finance (source-code licence model) and Velmie (source-code delivery option) all publicly reference source-code access. For Crassula, source-code availability was not established in the reviewed official materials; ask sales. In every case, the contract defines the exact usage and modification rights.
Do any of these vendors provide a banking licence?
No software licence is a banking, e-money or payment licence. Based on the reviewed materials, all four vendors supply software; regulated activities rely on your own authorisation or on licensed partners such as banks, EMIs, BaaS providers, card BIN sponsors and custodians. Confirm in contract which regulated partners a vendor can introduce.
Are card issuing and crypto custody native to these platforms?
Not in the regulated sense. The platforms provide card and wallet workflows, but card issuing and BIN sponsorship come from card issuer-processors, and regulated custody and liquidity come from specialist providers. SAMFCore explicitly states it does not itself provide card issuing, regulated custody or liquidity; Crassula describes crypto via third-party custody and liquidity partners.
How do the costs differ?
SAMFCore publishes starting prices: annual licence from CHF 80,000/year, perpetual usage licence from CHF 325,000 one-time, and Perpetual + Full Source Code from CHF 620,000. Comparable all-in prices for Crassula, SDK.finance and Velmie were not established in the reviewed pages and require a quote. Total cost also includes integration, third-party provider fees, hosting, compliance and support, so compare five-year totals rather than licence fees alone.
Which is best for serving both personal and business clients?
All four describe individual and business (corporate) customer support in some form, including onboarding flows. The deciding factors are usually KYB depth, multi-user business permissions, and which account and payment providers support corporate clients in your target markets. Request a demo of a full corporate onboarding and payment approval flow from each vendor.
How should I choose between SAMFCore, Crassula, SDK.finance and Velmie?
Start from your licensing and deployment requirement (SaaS, private cloud, on-premises, source code), then your regulated partners, then feature fit. Score each vendor against the same criteria, request test access, and have counsel review licence scope, source-code rights, exit terms and support SLAs before signing.
Next steps
Write down your licensing, deployment and partner requirements first, then request the same scenario-based demo and quote from each vendor. To review SAMFCore, see the SAMFCore overview and licensing packages. To review the alternatives, start with Crassula, SDK.finance and Velmie.
Original sources and further reading
All vendor pages below were reviewed on 11 October 2026.
SAMFCore (Swiss AMF AG)
- SAMFCore homepage (reviewed 11 October 2026)
- SAMFCore licensing & pricing (reviewed 11 October 2026)
- SAMFCore perpetual software licence (reviewed 11 October 2026)
- SAMFCore crypto & digital assets (reviewed 11 October 2026)
- SAMFCore API & integrations (reviewed 11 October 2026)
Crassula
- Crassula crypto product (reviewed 11 October 2026)
- Crassula guide: top white-label digital banking platforms (reviewed 11 October 2026)
- Crassula developers (reviewed 11 October 2026)
SDK.finance
- SDK.finance source code (reviewed 11 October 2026)
- SDK.finance pricing (reviewed 11 October 2026)
- SDK.finance crypto banking solution (reviewed 11 October 2026)
- SDK.finance: how source code licensing works (reviewed 11 October 2026)
Velmie
- Velmie white-label fintech platform (reviewed 11 October 2026)
- Velmie white-label banking platform (reviewed 11 October 2026)
- Velmie accounts (reviewed 11 October 2026)
- Velmie digital assets (reviewed 11 October 2026)
- Velmie delivery options (reviewed 11 October 2026)