Implementation

On this page
  1. From requirements to launch
  2. How the delivery model affects your project
  3. Support after launch

Implementation takes your FinTech product from agreed requirements to a configured, tested SDK.finance deployment. This page outlines the main stages and the decisions needed before launch.

From requirements to launch

The project plan depends on your selected products, delivery model, integrations, and customisation needs. Some stages can run in parallel.

StageWhat happens
1. Scope and requirementsDefine your business model, users, markets, currencies, interfaces, and providers. Agree which SDK.finance products you need, the launch scope, and who is responsible for each part.
2. Environment preparation and setupPrepare databases, domains, and access. Set up separate environments for development, testing, and production according to the selected delivery model.
3. Product configurationIn Transaction Platform, configure currencies, fees, limits, and staff roles. For General Ledger, set up the chart of accounts and rules for recording business events.
4. IntegrationsArrange provider agreements and access, then configure existing connections or develop custom ones. Confirm the supported operations using the integration options.
5. Interfaces and brandingPrepare the names, logos, and colours for your selected interfaces. Agree any changes to screens or business workflows within the scope of your delivery model.
6. Testing and launchValidate customer journeys, transactions, balances, permissions, and provider connections. Resolve issues, confirm production readiness, and agree the launch date.
7. Support and updatesHand over day-to-day operations, assign responsibility for monitoring and issue handling, and agree how future updates will be tested and applied.

How the delivery model affects your project

For Transaction Platform, responsibilities differ by delivery model:

  • SaaS: SDK.finance manages application hosting and scheduled updates. Your team manages the databases and project-specific integrations. Changes are made through configuration and external integrations.
  • Source Code: your team or implementation partner deploys and maintains the software and infrastructure. You can modify the core code and manage the rollout of updates.

Agree the division of work before implementation begins. Provider onboarding, custom development, and testing all affect the launch schedule.

Support after launch

Use your agreed SDK.finance support channel for questions and issue reporting. Confirm support coverage and access to new releases in your agreement, including who will test and install updates.