Bity (BT) is a fintech company operating in the cryptocurrency space. Their platform includes services for buying, selling, and exchanging digital assets.

‍

Initial Situation

Bity did not have an existing system to support the purchase of gold-backed NFTs. While they already operated crypto-related services, this use case required a new backend component to handle transaction logic and integration with external services.

The new functionality needed to fit into their existing architecture and be compatible with their internal processes.

‍

Pain Points

The project was not driven by a malfunctioning system but by missing functionality. The main challenges were:

• No existing implementation for gold NFT purchasing
• Integration of multiple external APIs, some of which were not accessible during development
• Limited prior experience on the Sly side with crypto/NFT-specific processes
• Requirement for Bity to retain full control over deployment and operations

‍

Assignment

Sly was tasked with implementing a backend service that enables users to purchase gold-backed NFTs.

‍

The scope included:

• Structuring the system in a way that supports future modularization
• Ensuring compatibility with Bity’s existing infrastructure
• Delivering a solution that Bity can operate and extend independently

‍

Solution

The implementation was based on the architectural concepts of VELOX.

The checkout functionality was implemented in a tailor-made way, adapted to Bity’s requirements. At the same time, it remained close to the architectural structure and design principles of VELOX, including:

• API-first design
• Modular structure
• Separation of responsibilities

The system is therefore not a standard VELOX deployment, but also not independent of it. It is a custom implementation aligned with VELOX architecture.

‍

Implementation

The system was implemented as a backend service with a focus on API integration and modular structure.

Relevant aspects:

• Integration of external services via APIs, including NFT-related data sources
• Use of mock servers (Prism) to simulate APIs that were not accessible during development
• Implementation of integration tests to validate system behavior against expected API responses
• Structuring the codebase to allow future extraction into microservices

Collaboration model:

• Sly: architecture design, implementation, and technical support
• Bity: code reviews, deployment, infrastructure, and operations

After delivery, Bity took over maintenance and further development of the implemented components.

‍

Result

The result was a backend service that enables the purchase of gold-backed NFTs and integrates into Bity’s system landscape.

Key outcomes:

• System structured in a modular way, allowing future separation into microservices
• Bity assumed responsibility for deployment, operation, and further development after delivery
• Collaboration functioned as a shared development setup, with Sly and Bity working on the same codebase

‍

Summary

The project resulted in a backend implementation for a new transaction type (gold-backed NFTs), built as a custom solution that remains structurally aligned with VELOX.