Help to stop the war! Stand with Ukraine!
Contact Us

SDK.finance SaaS Core Ledger Technology

Explore SDK.finance ledger layer backend on how to create scalable payment solutions on top of its open APIs and accelerate product launch, address regulatory compliance issues, reduce development costs and fuel innovation thanks to its SaaS nature combined with the hybrid cloud delivery model.

Contact us

Hybrid cloud model

SaaS version of SDK.finance software is available through the hybrid cloud delivery model designed primarily for startups or SMBs.

The backend app is hosted on our servers or via major public cloud platforms and maintained by our team.
The databases are stored on your servers and managed by your own team. This is in order to meet the cloud data management regulators’ requirements for any country and enable usage of our platform around the globe.

Database setup guide

SDK.finance SaaS Core Ledger Technology

Front-end

Users of the cloud SaaS version of SDK.finance platform need to take care of the product front-end on their side. This includes admin area and end-user design.

The downloadable web front-office and back-office UI packs are available on Github and can be modified according to the customer’s vision. Alternatively, customers can develop their own front-and back office design from scratch.

Free UI packs download

Frontend configuration guide

SDK.finance SaaS Core Ledger Technology

AWS Server infrastructure

SDK.finance solution is available on the AWS cloud infrastructure, which features top-notch resilience, security and meets the strictest regulatory requirements.

In addition, AWS services can be delivered regionally across the AWS 87 availability zones, per customer request, in order to meet the data management requirements of the regulator.

If necessary, a customer’s SDK.finance platform instance can also be made available from the other cloud providers like Oracle or Microsoft Azure.

SDK.finance SaaS Core Ledger Technology

Integrations

SDK.finance implements REST and gRPC API architecture style to facilitate integration with third party providers and services and assist in driving our customers’ products innovation.

SDK.finance out-of-the-box functionality lies in using its 400+ interactive API endpoints exposed as Open APIs (available via Swagger).

Customers can build integrations with third party services and providers leveraging SDK.finance API flows designed for specific use cases, which streamlines the process and makes it more time- and cost-efficient.

API flows for typical use cases

SDK.finance SaaS Core Ledger Technology

Hardware requirements

Here are the minimum requirements of the instance for both Production and Test environments to run the system and ensure its stable performance.

 

Front end

CPU – 1
RAM – 2 GB
SSD – 40 GB
OS: Ubuntu 20.04 LTS
Software: NGINX 1.14.0

Application server

CPU – 4
RAM – 8 GB
SSD – 160 GB
OS: Ubuntu 20.04 LTS
Software: openJDK 16

Postgres DB

CPU – 4
RAM – 16 GB
SSD – 160 GB
OS: Ubuntu 20.04 LTS
DB: PostgreSQL – 13.3

Transaction Viewer DB

CPU – 2
RAM – 4 GB
SSD – 80 GB
OS: Ubuntu 20.04 LTS
DB: MongoDB – 4.2.2

Security

System architecture security

We follow the latest ISO standards in code development, meeting the requirements of the ISO 27001, ISO 12812, ISO 12812-5.

The interaction between clients and server components in the system is protected by a variety of traffic encryption methods:

  • -TLS with a 256 or 512 bit encryption
  • -data hashing algorithms SHA-256 or SHA-512
  • -data packets signature
  • -checksums verification
  • -IP filtering
  • -brute force attacks protection.

We also implement firewalls, IDS (Intrusion Detection System), WAF (Web Application Firewalls) and load-balancing.

AWS infrastructure security

SDK.finance customers benefit from a secure environment offered by AWS cloud infrastructure. Apart from a range of physical security measures protecting the data centers, AWS infrastructure is compliant with numerous third-party assurance frameworks, like PCI-DSS, EU Data Protection Directive, FedRAMP, GDPR etc. 

Clients interface and staff back office security

  • -OTP and ​​HMAC authorisation are used to secure the back office access for employees
  • -Two-factor authorisation and OAuth are used for end-users logins into their accounts.
  • Role-based access limits staff access to specific sections of the back office
  • Trusted domains list can be implemented.

Need more details? Get in touch!

    By pressing “Send” button you confirm that you have read and accept our Privacy Policy and Terms & Conditions