Datacenter

We partner with EvoSwitch, a leader in secure data hosting.

EvoSwitch is certified with ISO27001 and 9001 security standards, PCI DSS (Payment Card Industry Data Security Standard), and SAS-70. These certifications ensure the highest reliability, making it a trusted choice for banks. Physical access to the data center is tightly controlled, requiring passes, including biometric verification.

Key Technologies

We employ best practices to build modern, complex systems.

Our platform is built on open-source technologies such as .NET, RabbitMQ, Vue.js, MSSQL, and PostgreSQL. The stack is predominantly Microsoft or open source, ensuring flexibility and scalability. Our architecture and infrastructure are designed to grow with your business, minimizing unnecessary expenses.

Architecture

TIP

Our architecture is informed by extensive experience in developing and operating factoring systems for the top 10 banks in Russia from 2016 to 2021.
Let's talk

The system's core is a modular monolith complemented by a set of microservices using the RabbitMQ broker. This setup allows for independently scalable services and a fault-tolerant system, supporting both Windows and Linux environments.

Three-Step Confirmation System

Our factoring automation software ensures a secure and reliable transaction management process with a robust three-step confirmation system. Tasks are clearly delineated between clients, enabling you to manage multiple clients simultaneously without confusion. You can easily confirm or cancel any transaction within each client's framework, maintaining full control over the process.

Rest assured, our system allows you to roll back any transaction before its final confirmation, providing an additional layer of security and confidence in your operations. Work efficiently and with peace of mind, knowing you always have the option to correct any situation.

Buyer API

Our system allows debtors to operate 100% automatically, transmitting data about new deliveries, confirming payment amounts, and providing an XML document for payment distribution across monetary claims.

Sample XML document:

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="NewSupplyNotification">
    <xs:complexType>
      <xs:sequence maxOccurs="unbounded">
        <xs:element ref="CommercialInvoice"/>
      </xs:sequence>
      <xs:attribute name="NotificationNumber" type="xs:string" use="optional"/>
      <xs:attribute name="NotificationDate" type="xs:date" use="optional"/>
      <xs:attribute name="FactoringAgreement" type="xs:string" use="optional"/>
    </xs:complexType>
  </xs:element>
  <xs:element name="CommercialInvoice">
    <xs:complexType>
      <xs:sequence>
        <xs:element ref="DocumentType"/>
        <xs:element name="InvoiceNumber" type="xs:string"/>
        <xs:element name="InvoiceDate" type="xs:date"/>
        <xs:element name="DispatchDate" type="xs:date"/>
        <xs:element name="DeliveryDate" type="xs:date"/>
        <xs:element name="PaymentTerms" type="xs:int"/>
        <xs:element ref="PaymentTermsType"/>
        <xs:element name="InvoiceAmountExVAT" type="xs:decimal"/>
        <xs:element name="InvoiceAmountIncVAT" type="xs:decimal"/>
        <xs:element name="SupplyContractNumber" type="xs:string"/>
        <xs:element name="SupplyContractDate" type="xs:date"/>
        <xs:element name="InvoiceReferenceNumber" type="xs:string" minOccurs="0"/>
        <xs:element name="InvoiceReferenceDate" type="xs:date" minOccurs="0"/>
        <xs:element ref="Seller"/>
        <xs:element ref="Buyer"/> 
        <xs:element ref="LineItems"/>
      </xs:sequence>
      <xs:attribute name="ContractPaymentDueDate" type="xs:date" use="optional"/>
    </xs:complexType>
  </xs:element>
</xs:schema>

Microservices

Our microservices include scoring, EDI, digital signature verification, data collection and analysis for verification, task scheduling, various integrations, and more.

Inside the microservices: separate databases, reliable distributed transactions, load balancing, three-level message retry, strict contracts, outbox, circuit breaker, poison message control, separate service deployment, and comprehensive monitoring with alerts.