Platform comparison

SDK.finance vs SAMFCore

Both give you source code. The bigger question is what you can build with it.

SDK.finance and SAMFCore both give financial-services companies more control than a conventional closed SaaS platform. Both support source-code licensing, customer-controlled infrastructure, payments, cards, fiat and crypto, APIs and back-office operations.

SAMFCore goes further by structuring its licensing around the business the customer wants to build, including territorial rights up to global operation, multiple or unlimited white-label brands, unlimited end customers under applicable licensing, additional legal entities and perpetual software rights.

Where SAMFCore stands apart is built-in crypto, digital-asset and card-issuing workflows delivered inside one perpetual licence. SDK.finance delivers crypto and card capabilities through third-party vendor integrations — such as Marqeta for cards and Fireblocks for crypto custody — that each customer must contract with and connect separately.

Explore SAMFCore Configure Your Licence Schedule a Call

Comparison based on publicly available SDK.finance information and current SAMFCore product documentation. Product and commercial terms may change.

Quick answer

What Is the Difference Between SDK.finance and SAMFCore?

SDK.finance and SAMFCore both offer source-code financial infrastructure with payments, cards, crypto, APIs and customer-controlled deployment. SAMFCore differs most in how the platform can be licensed around the buyer’s business, with territorial options up to global rights, multiple or unlimited white-label brands, unlimited end customers under applicable licensing, additional legal entities and perpetual software rights.

At a glance

SDK.finance vs SAMFCore at a Glance

The two platforms overlap substantially in technology. The clearest differences concern the scope of the operating environment and how software rights can be configured around growth.

Area

SDK.finance

SAMFCore

Source code

Available.

Permanent licence

Lifetime licence available.

Perpetual licence available.

Own infrastructure

Supported.

Payments

Supported.

Cards

Supported via third-party card-issuer integration (e.g. Marqeta).

Built-in card-issuing workflows under one perpetual licence.

Card Provider Support

Provider integrations available (e.g. Marqeta).

Customer-selected card issuer; card-management workflows built into the platform.

Crypto / digital assets

Supported via third-party custody/liquidity integrations (e.g. Fireblocks).

Built-in crypto & digital-asset workflows under one perpetual licence.

Fiat-to-crypto / crypto-to-fiat

Supported via third-party integrations.

Built-in exchange workflows under one perpetual licence.

KYC / KYB

Supported.

AML / compliance workflows

Supported.

CRM / back office

Supported.

APIs

Extensive API architecture.

Extensive API and integration architecture.

White-label capability

Supported.

Supported, with defined multi-brand and unlimited-brand licence options.

Territorial rights

Country-based source-code licensing.

Single-country through global territorial options.

Unlimited end customers

Not specified publicly.

Unlimited.

Per-customer transaction software fee

Check vendor commercial terms for the selected source-code package

None

Share of transaction revenue

Check vendor commercial terms

None

Additional legal entities

Not specified publicly.

Additional legal entities can be licensed.

Own developers

SDK.finance

Customer-managed under source-code model.

SAMFCore

Customer may use Swiss AMF, its own team or appointed developers.

Compare the licence around your business

Configure territory, source code, legal entities and white-label brand rights.

Configure Your Licence

Commercial rights

Both Offer Source Code. SAMFCore Is Designed Around Broader Business Rights.

Source-code access alone does not determine how much freedom a financial-services company has. The licence also needs to support the commercial structure the company intends to build.

How many countries can you operate in?

How many customer-facing brands can you run?

How many end customers can you serve?

Can you add legal entities?

Are software costs tied to transaction volume?

Can you keep operating permanently?

Can your developers maintain it?

Can the business grow without renegotiating core rights?

SAMFCore is designed to make territory, brands, legal entities, end-customer scale, development control and permanent software usage rights part of the licensing structure from the beginning.

Global and multi-country licensing

Build for One Market or Build Globally

SDK.finance documents country-based source-code licensing. SAMFCore offers territorial licensing options ranging from a single country to global operating rights. For a financial-services group planning to expand across several markets, this can materially simplify the long-term software structure.

Territory configured for the growth plan

Select rights for one country, up to five countries, up to fifteen countries or global operation within the licensed scope.

White-Label Financial Platforms

SDK.finance supports white-label use cases. SAMFCore provides defined licensing options for one, multiple or unlimited white-label brands.

One platform. Multiple brands. One operating environment.

Explore white-label customization

Unlimited customers and growth economics

Growth Should Not Automatically Increase Your Core Software Bill

Under applicable SAMFCore licensing, end customers are unlimited. Across all licensing models, SAMFCore does not charge a software fee for customer transactions or take a percentage of your transaction fees or transaction revenue. As transaction volumes grow, your SAMFCore software licence cost does not increase merely because customers transact more. For high-volume businesses, this can make a substantial difference to long-term operating costs and retained revenue.

External banking, card, custody, payment, blockchain, liquidity, infrastructure and other third-party provider fees remain separate.

Assess the five-year cost model for finance leaders Review what the perpetual software licence includes

Financial-services operating platform

More Than a Transaction Engine

SDK.finance covers many of the same categories and is a serious financial-technology platform. SAMFCore’s positioning is broader: it is designed as the operating environment for the licensed financial-services business itself.

Accounts & Transactions

Payments

Cards

Crypto & Digital Assets

Fiat-to-Crypto

Crypto-to-Fiat

KYC / KYB

AML & Compliance

CRM

Back Office

Reporting

Administration

White-Label Brands

APIs & Integrations

Lifetime vs perpetual licensing

Build Around Technology Your Company Can Keep

Both platforms offer a permanent-use route. SAMFCore perpetual licensing gives the licensed company permanent software usage rights. The business does not have to remain on an indefinite SAMFCore software subscription simply to keep using the licensed version.

With qualifying source-code licensing, the company can also use its own or appointed developers for its licensed deployment. This can make the software part of the company’s long-term technology base rather than an ongoing access dependency.

Review perpetual and source-code licensing

Source code and development control

Control the Software Your Business Depends On

SDK.finance and SAMFCore both offer meaningful source-code control. SDK.finance customers can modify and operate their source-code deployment.

Inspect and modify the licensed SAMFCore deployment
Use internal developers
Appoint third-party developers
Maintain independently
Operate under customer-controlled infrastructure

The distinction is not that one platform has source code and the other does not. SAMFCore combines source-code access with a broader configurable commercial-rights model.

Built-in crypto and cards

Built-In Crypto Workflows and Card Issuing Under One Perpetual Licence

Both platforms touch crypto and cards. The difference is how. SAMFCore brings crypto/digital-asset and card-issuing workflows inside the platform under a single perpetual licence. SDK.finance delivers crypto and card capabilities through third-party vendor integrations that each customer must contract with and connect separately.

Crypto & digital-asset workflows

SAMFCore includes crypto and digital-asset workflows — fiat-to-crypto, crypto-to-fiat, wallets, transfers and compliance handoffs — as built-in platform capabilities under one perpetual licence. The customer selects and integrates the external custody, liquidity and blockchain providers it needs; these workflows are native to the platform.

SDK.finance provides crypto functionality through pre-integrated third-party vendors such as Fireblocks (custody) and Currencycloud (exchange rates). Clients must become customers of the relevant provider and connect the integration to use these capabilities.

Card issuing

SAMFCore includes card-programme workflows — card lifecycle, limits, wallets, funding and spend controls — as a built-in module under the perpetual licence. The customer connects its chosen card issuer or BIN sponsor.

SDK.finance delivers card issuing through a third-party integration with Marqeta. Clients must contract with Marqeta and connect the integration to issue cards.

External banking, custody, liquidity, exchange, card-issuing and payment infrastructure is selected and integrated by the customer in both platforms. The distinction is that SAMFCore’s integration layer is built into the platform under one perpetual licence, whereas SDK.finance relies on separate third-party vendor integrations that the customer must contract with and connect.

Provider independence and integrations

Build Around the Providers Your Business Needs

SAMFCore uses a provider-independent architecture. Customers select the external providers appropriate for their business, jurisdiction and deployment.

Banks

Payment providers

Card issuers

BIN sponsors

Card processors

KYC/KYB providers

AML providers

Custody providers

Liquidity providers

Exchanges

Blockchain infrastructure

SAMFCore provides the software environment and integration framework. Provider availability and integration scope depend on each provider’s technical capabilities and the customer deployment.

Licensed financial-services companies

The Software Has to Support the Business You Are Building

For a company that already holds a financial-services licence, the software is not simply an IT purchase. It becomes part of the infrastructure used to commercialise that licence.

Enter several countries

Operate several brands

Add crypto and cards

Serve a large customer base

Connect different providers

Add legal entities

Use your own developers

Support a future company sale

SAMFCore is designed so the software rights can be structured around those objectives. Regulatory permissions, approvals and external regulated providers remain the responsibility of the customer.

Where SDK.finance Is Strong

SDK.finance is a serious competitor with a mature source-code model. A buyer looking for a customizable fintech development platform with source code should consider it seriously.

source-code licensing
lifetime licensing
customer-controlled deployment
extensive APIs
accounts and payments
card functionality
crypto and fiat functionality
compliance workflows
documented provider integrations
customer-facing web and mobile application foundations
a documented source-code acquisition process

Where SAMFCore Goes Further

Global Territorial Options

Licence SAMFCore for one country, several countries or global operation.

Multi-Brand Flexibility

Operate multiple or unlimited white-label brands.

Unlimited End Customers

Scale the customer base without per-user SAMFCore licensing under the applicable model.

No Per-Transaction Fees. No Revenue Share.

Across all licensing models, SAMFCore charges no software fee per customer transaction and takes no share of transaction fees or transaction revenue. Provider and infrastructure fees remain separate.

Built-In Crypto & Digital-Asset Workflows

Crypto and digital-asset workflows — fiat-to-crypto, crypto-to-fiat, wallets and compliance handoffs — are native to the platform under one perpetual licence, rather than assembled from separate third-party integrations.

Built-In Card-Programme Workflows

Card lifecycle, limits, funding and spend-control workflows ship inside the platform under the perpetual licence. The customer connects its chosen card issuer or BIN sponsor.

Broader Commercial Configuration

Configure rights around territory, legal entities, white-label brands, source code and deployment.

SDK.finance alternative

Is SAMFCore an SDK.finance Alternative?

Yes, particularly when the buying decision extends beyond source-code access into the commercial rights needed for a multi-brand or international financial-services business.

Who Should Consider SDK.finance?

source-code fintech infrastructure
lifetime licensing
customer-controlled deployment
extensive APIs
payments and wallet functionality
crypto functionality
documented provider integrations
a mature development platform

Who Should Consider SAMFCore?

a broader financial-services operating platform
fiat and crypto in one environment
perpetual software rights and optional full source code
global territorial licensing
multiple or unlimited white-label brands
unlimited end customers under applicable licensing
no per-customer transaction software fees or transaction revenue share across all SAMFCore licensing models
customer-controlled infrastructure
their own or appointed developers
flexibility across customer-selected financial-service providers
a platform designed around the long-term structure of the business

The best alternative to SDK.finance depends on the infrastructure and business rights required. If the priority is a source-code banking or fintech platform with a global licence option, configurable brands and legal entities, unlimited customers and permanent usage rights, SAMFCore offers a distinct model.

Do Not Compare Only the Software. Compare the Business Rights.

If the requirement is simply, “We need a customizable fintech platform with source code,” SDK.finance is a serious option.

If the requirement is, “We want to build a multi-brand, potentially international financial-services business around technology we can permanently control and scale,” SAMFCore is designed around that broader requirement.

What will your company still be free to build with it five years after purchase?

Configure Your SAMFCore Licence

FAQ

SDK.finance vs SAMFCore FAQ

Is SAMFCore an alternative to SDK.finance?

Yes. Both platforms target financial-services companies that need payments, accounts, cards, digital assets, APIs, integrations and greater control over their technology. SAMFCore differs most in its broader commercial-rights structure, including territorial options up to global rights, white-label licensing, perpetual licensing and configurable business scope.

Does SDK.finance provide source code?

Yes. SDK.finance offers commercial source-code licensing.

Does SAMFCore provide source code?

Yes. Full source code is available with qualifying SAMFCore perpetual licensing.

Does SDK.finance offer lifetime licensing?

Yes. SDK.finance offers a lifetime source-code licensing option.

Does SAMFCore offer a perpetual licence?

Yes. SAMFCore offers permanent, non-expiring software usage rights within the licensed scope.

Can SDK.finance be deployed on-premises?

Yes. SDK.finance states that its source-code deployment can be hosted on premises, in a dedicated data centre or in a private cloud.

Can SAMFCore be deployed under customer-controlled infrastructure?

Yes. SAMFCore can be deployed within infrastructure controlled by the customer or its appointed infrastructure provider, depending on the agreed deployment.

Does SDK.finance support crypto?

Yes. SDK.finance supports crypto functionality through pre-integrated third-party vendors such as Fireblocks (custody) and Currencycloud (exchange rates). Clients must contract with the relevant provider and connect the integration to use these capabilities.

Does SAMFCore support crypto?

Yes. SAMFCore includes crypto and digital-asset workflows — fiat-to-crypto, crypto-to-fiat, wallets and compliance handoffs — as built-in platform capabilities under one perpetual licence. External custody, liquidity and blockchain providers are selected and integrated by the customer.

How do crypto and card capabilities differ between SDK.finance and SAMFCore?

SAMFCore brings crypto/digital-asset and card-issuing workflows inside the platform under a single perpetual licence. SDK.finance delivers these capabilities through third-party vendor integrations — for example Marqeta for card issuing and Fireblocks for crypto custody — that each customer must contract with and connect separately.

Does SDK.finance support card issuing?

Yes. SDK.finance supports card issuing through a third-party integration with Marqeta. Clients must become a Marqeta customer and connect the integration.

Does SAMFCore support card issuing?

Yes. SAMFCore includes card-programme workflows — card lifecycle, limits, funding, wallets and spend controls — as a built-in module under the perpetual licence. The customer connects its chosen card issuer or BIN sponsor.

Can SAMFCore be licensed globally?

Yes. SAMFCore offers territorial licensing options up to global operating rights.

Does SAMFCore support multiple white-label brands?

Yes. SAMFCore provides multiple and unlimited white-label options depending on the selected licence.

Does SAMFCore limit the number of end customers?

No. Unlimited end customers are included.

Does SAMFCore charge transaction-volume software licence fees?

Across all licensing models, SAMFCore does not charge a software fee per customer transaction or take a share of transaction fees or transaction revenue. Third-party provider and infrastructure charges remain separate.

Comparison Methodology

Last reviewed: September 2026

SDK.finance information on this page is based on publicly available SDK.finance product and documentation materials reviewed in September 2026. Product functionality and commercial terms may change. SAMFCore information reflects the current SAMFCore product and licensing model.

Source-code acquisition Source-code deployment model Pricing and lifetime licensing Technology and APIs Documented provider integrations Back-office capabilities

SDK.finance is a trademark of its respective owner. References are for identification and factual comparison only; no affiliation or endorsement is implied.

Also evaluating SaaS core banking? See Mambu vs SAMFCore.

Evaluating a move from SDK.finance? Explore the SAMFCore migration approach.

Compare the Rights, Not Just the Feature List

Both SDK.finance and SAMFCore offer serious financial infrastructure with source-code options. The difference may be what your business is allowed to build around the platform over the long term. See how SAMFCore can be configured around your countries, brands, customers, legal entities and development model.

Configure Your Licence Schedule a Call Explore SAMFCore