Software Development

Bity

Software Development

Bity SA is a Swiss based brokerage for buying, selling, trading cryptocurrency

Client:

Bity SA

Year:

2024

Service Offered:

Software Development, Software Architecture, Consulting

Initial Situation

We provided them with a tailored solution based upon the Velox architecture and standard modules. Their setup is customised to fit their unique requirements. Although this financial institution is experienced in the crypto market, this service marked a new area in their offerings.

PAIN POINTS

Our client

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

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

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.

Summary

The project involved the design and implementation of a backend commerce service enabling users to purchase tokenized gold assets (NFTs) for a client operating in the cryptocurrency and fintech domain.

The client already had an existing platform for cryptocurrency exchange but required a new capability to support the sale of gold-backed NFTs as an additional business offering. This represented a new functional domain for the client rather than a replacement of an existing system.

To address this requirement, a custom backend service was developed, focusing on enabling the end-to-end purchase flow of these assets. While the implementation was tailored to the client’s specific use case, it was conceptually aligned with the architecture and principles of the VELOX platform. Standard architectural patterns, modular design, and API-driven structures were reused and adapted rather than building an entirely unrelated system.

The system was designed with a modular architecture, allowing future decomposition into microservices and enabling extensibility for additional features or services. This reflects a deliberate design decision to support long-term scalability and flexibility.

A key technical challenge was the integration of multiple external APIs, many of which were not accessible during development. To mitigate this, mock services (e.g., based on OpenAPI specifications) were used to simulate dependencies and allow for end-to-end testing and validation of system behavior.

The project followed a collaborative delivery model in which development and architectural support were provided, while the client retained responsibility for DevOps, deployment, and ongoing operation. The solution was delivered as an initial implementation, with ownership of further development and maintenance transferred to the client after completion.

Overall, the project combined custom development with established architectural patterns to deliver a specialized commerce capability in a new domain, while ensuring compatibility with existing systems and future extensibility.

Assignment

We provided them with a tailored solution based upon the Velox architecture and standard modules. Their setup is customised to fit their unique requirements. Although this financial institution is experienced in the crypto market, this service marked a new area in their offerings.

RESULT

Our client

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

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

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.

Summary

The project involved the design and implementation of a backend commerce service enabling users to purchase tokenized gold assets (NFTs) for a client operating in the cryptocurrency and fintech domain.

The client already had an existing platform for cryptocurrency exchange but required a new capability to support the sale of gold-backed NFTs as an additional business offering. This represented a new functional domain for the client rather than a replacement of an existing system.

To address this requirement, a custom backend service was developed, focusing on enabling the end-to-end purchase flow of these assets. While the implementation was tailored to the client’s specific use case, it was conceptually aligned with the architecture and principles of the VELOX platform. Standard architectural patterns, modular design, and API-driven structures were reused and adapted rather than building an entirely unrelated system.

The system was designed with a modular architecture, allowing future decomposition into microservices and enabling extensibility for additional features or services. This reflects a deliberate design decision to support long-term scalability and flexibility.

A key technical challenge was the integration of multiple external APIs, many of which were not accessible during development. To mitigate this, mock services (e.g., based on OpenAPI specifications) were used to simulate dependencies and allow for end-to-end testing and validation of system behavior.

The project followed a collaborative delivery model in which development and architectural support were provided, while the client retained responsibility for DevOps, deployment, and ongoing operation. The solution was delivered as an initial implementation, with ownership of further development and maintenance transferred to the client after completion.

Overall, the project combined custom development with established architectural patterns to deliver a specialized commerce capability in a new domain, while ensuring compatibility with existing systems and future extensibility.

SOlUTION

Our client

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

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

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.

Summary

The project involved the design and implementation of a backend commerce service enabling users to purchase tokenized gold assets (NFTs) for a client operating in the cryptocurrency and fintech domain.

The client already had an existing platform for cryptocurrency exchange but required a new capability to support the sale of gold-backed NFTs as an additional business offering. This represented a new functional domain for the client rather than a replacement of an existing system.

To address this requirement, a custom backend service was developed, focusing on enabling the end-to-end purchase flow of these assets. While the implementation was tailored to the client’s specific use case, it was conceptually aligned with the architecture and principles of the VELOX platform. Standard architectural patterns, modular design, and API-driven structures were reused and adapted rather than building an entirely unrelated system.

The system was designed with a modular architecture, allowing future decomposition into microservices and enabling extensibility for additional features or services. This reflects a deliberate design decision to support long-term scalability and flexibility.

A key technical challenge was the integration of multiple external APIs, many of which were not accessible during development. To mitigate this, mock services (e.g., based on OpenAPI specifications) were used to simulate dependencies and allow for end-to-end testing and validation of system behavior.

The project followed a collaborative delivery model in which development and architectural support were provided, while the client retained responsibility for DevOps, deployment, and ongoing operation. The solution was delivered as an initial implementation, with ownership of further development and maintenance transferred to the client after completion.

Overall, the project combined custom development with established architectural patterns to deliver a specialized commerce capability in a new domain, while ensuring compatibility with existing systems and future extensibility.

Implementation

Our client

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

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

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.

Summary

The project involved the design and implementation of a backend commerce service enabling users to purchase tokenized gold assets (NFTs) for a client operating in the cryptocurrency and fintech domain.

The client already had an existing platform for cryptocurrency exchange but required a new capability to support the sale of gold-backed NFTs as an additional business offering. This represented a new functional domain for the client rather than a replacement of an existing system.

To address this requirement, a custom backend service was developed, focusing on enabling the end-to-end purchase flow of these assets. While the implementation was tailored to the client’s specific use case, it was conceptually aligned with the architecture and principles of the VELOX platform. Standard architectural patterns, modular design, and API-driven structures were reused and adapted rather than building an entirely unrelated system.

The system was designed with a modular architecture, allowing future decomposition into microservices and enabling extensibility for additional features or services. This reflects a deliberate design decision to support long-term scalability and flexibility.

A key technical challenge was the integration of multiple external APIs, many of which were not accessible during development. To mitigate this, mock services (e.g., based on OpenAPI specifications) were used to simulate dependencies and allow for end-to-end testing and validation of system behavior.

The project followed a collaborative delivery model in which development and architectural support were provided, while the client retained responsibility for DevOps, deployment, and ongoing operation. The solution was delivered as an initial implementation, with ownership of further development and maintenance transferred to the client after completion.

Overall, the project combined custom development with established architectural patterns to deliver a specialized commerce capability in a new domain, while ensuring compatibility with existing systems and future extensibility.

Summary

Our client

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

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

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.

Summary

The project involved the design and implementation of a backend commerce service enabling users to purchase tokenized gold assets (NFTs) for a client operating in the cryptocurrency and fintech domain.

The client already had an existing platform for cryptocurrency exchange but required a new capability to support the sale of gold-backed NFTs as an additional business offering. This represented a new functional domain for the client rather than a replacement of an existing system.

To address this requirement, a custom backend service was developed, focusing on enabling the end-to-end purchase flow of these assets. While the implementation was tailored to the client’s specific use case, it was conceptually aligned with the architecture and principles of the VELOX platform. Standard architectural patterns, modular design, and API-driven structures were reused and adapted rather than building an entirely unrelated system.

The system was designed with a modular architecture, allowing future decomposition into microservices and enabling extensibility for additional features or services. This reflects a deliberate design decision to support long-term scalability and flexibility.

A key technical challenge was the integration of multiple external APIs, many of which were not accessible during development. To mitigate this, mock services (e.g., based on OpenAPI specifications) were used to simulate dependencies and allow for end-to-end testing and validation of system behavior.

The project followed a collaborative delivery model in which development and architectural support were provided, while the client retained responsibility for DevOps, deployment, and ongoing operation. The solution was delivered as an initial implementation, with ownership of further development and maintenance transferred to the client after completion.

Overall, the project combined custom development with established architectural patterns to deliver a specialized commerce capability in a new domain, while ensuring compatibility with existing systems and future extensibility.