SDK.finance FAQs: products, pricing and implementation

SDK.finance offers a backend, a backoffice for your team, customer-facing web and mobile applications, and merchant tools. These components serve different users and workflows. Review the components included in your proposal, along with any branding, configuration, and integration work required for launch.

Yes. You can build your own customer experience and connect it to the SDK.finance Platform through APIs. The Platform provides 650+ APIs, allowing your team to integrate financial functionality into an existing application or develop a new frontend. The integration scope depends on the workflows and external services your application needs.

With SaaS, SDK.finance hosts and maintains the application, while your team connects its interfaces and external services through APIs and integrations. SaaS does not include direct access to the backend source code.

A source code licence gives your team access to modify the licensed code and deploy it on your own infrastructure. Your team manages the deployment and its customisations, with support and update arrangements defined in your agreement.

SDK.finance offers SaaS pricing and source code licensing. SaaS pricing combines a recurring platform fee with transaction-based charges. Source code licensing offers annual and lifetime options.

Your overall project budget may also include implementation, custom development, infrastructure, and third-party services. See the current SaaS pricing and source code licensing options.

The SaaS model includes transaction-based charges. Source code licensing follows a different commercial model, described on the source code pricing page.

Banks, payment processors, card issuers, verification providers, and other external services may charge separately. When reviewing your proposal, confirm which operations are billable and which provider fees apply to your planned workflows.

Yes. A source code licence allows your team to modify and extend the licensed software, including changes to its core functionality. You can develop features and integrations around your requirements.

The licence agreement defines the components and usage rights included. Access to source code should not be confused with an open-source licence or unrestricted rights to redistribute the software.

Hosting responsibilities depend on the delivery model. With SaaS, SDK.finance manages application hosting, while your organisation manages its databases under the agreed deployment setup.

With a source code licence, your organisation manages the application and database infrastructure, whether on-premises or in a cloud environment. Hosting location, access, backups, and operational responsibilities should be defined during deployment planning.

Yes. The approach depends on your requirements and delivery model. Configuration adapts available settings and workflows. APIs, webhooks, and middleware connect external systems and extend the product experience.

A source code licence also allows changes to the core code. Before implementation, distinguish the requirements covered by existing functionality from those needing configuration, integration, or additional development.

SDK.finance supports pre-built integrations and custom connections through APIs, webhooks, or middleware. For an available pre-built integration, you need the provider relationship, credentials, and configuration required for your use case.

A provider outside the pre-built list requires a technical assessment and integration work. Provider contracts, onboarding, and service availability are handled separately from the software connection. Explore the integration options.

SDK.finance provides software and is not a bank or payment institution. Buying or subscribing to the software does not itself provide a financial licence, bank accounts, IBANs, or a card programme.

These services require arrangements with the relevant financial providers. Availability depends on your business model, operating markets, provider requirements, and approvals.

Start with the workflows your product needs, including user roles, money movement, interfaces, external providers, and reporting. Compare these requirements with the product documentation and relevant demos.

For requirements that need clarification, contact our team. Distinguish built-in functionality, configuration, integration, and custom development before agreeing on the implementation scope.

The process starts with a review of your requirements and a commercial proposal. It then includes a code audit and evaluation stage before the decision to proceed and transfer the code.

The evaluation, acceptance, handoff, and engineering support arrangements are defined for your project. Read more about the source code acquisition process.

You can choose from three implementation models:

• Your internal development team. Your engineers handle the agreed configuration, integrations, customisation, testing, and release work. This suits organisations with the required technical skills and payments experience.
• A specialised SDK.finance development partner. Work with a team experienced in the Platform’s architecture, APIs, and financial workflows. The partner delivers the implementation services agreed for your project.
• A hybrid team. Your engineers and a specialised partner share delivery responsibilities. The partner can provide additional expertise and capacity, with knowledge transfer to your internal team.

SDK.finance provides the Platform, documentation, and implementation guidance. The right approach depends on your team, project scope, and long-term operating model. Define responsibility for infrastructure, integrations, releases, and post-launch support alongside your SaaS or source code arrangement.

Read our SDK.finance implementation guide for the models, stages, and team requirements.

Implementation time depends on the product scope, delivery model, required integrations, customisations, and your team’s availability. Projects involving data migration or external financial providers also depend on testing and provider onboarding.

A useful estimate starts with agreed launch requirements and a clear division of responsibilities. Separate the software implementation schedule from the approvals and operational work needed to launch your service.

Support depends on your delivery model and agreement. For SaaS, SDK.finance manages platform maintenance and scheduled updates. Source code offers include support and update arrangements, while your team manages its deployment and customisations.

Your agreement should specify the support period, covered components, bug-fix scope, and how issues involving custom code or third-party systems are handled.

An updated product version may need to be merged with changes your team has made. Your team is responsible for managing the customised codebase and validating changes before deployment.

Access to releases and any assistance with updates depend on your agreement. Receiving an update does not mean it can be applied automatically to a modified version without compatibility checks and testing.

Yes. You can explore the backoffice demo to review operational workflows. The pricing page also links to customer-facing applications and merchant tools.

Choose the interface that matches the part of the product you want to evaluate. For a walkthrough focused on your requirements, contact our team with your use case and the workflows you would like to discuss.

For a new project, use our contact page. Include your product idea, target markets, required integrations, and whether you are considering SaaS or source code licensing.

If you are an existing customer, use the support contact specified in your agreement. For an issue with a financial service built using SDK.finance software, contact that service’s operator.