BKN301: building the 301pay payment platform

A new payment platform

BKN301 wanted to build a proprietary payment platform connecting international payment networks, local banking systems and digital channels in one infrastructure.

The business goals were to manage payments across channels, improve conversion rates and offer merchants a competitive service. There was no existing system to extend: the team had to define the architecture and build the platform within a roadmap, regulatory requirements and a delivery deadline.

BKN301 Diagram

Requirements

The project combined payment technology, regulatory requirements and the needs of merchants in an established market.

The requirements included:

  • PCI DSS, SCA and 3DS requirements from the first release
  • Support for multiple currencies and languages for international expansion
  • A modular design for adding payment networks and methods
  • A consistent payment experience across web, mobile, pay-by-link and social channels
  • A merchant service that could compete with established payment providers

Several stakeholders were involved, each with different priorities. We needed to agree the technical foundation and sequence the work within the delivery timeline.

Working with the BKN301 team

We began by reviewing the business requirements and how they would shape the architecture.

Discovery and architecture. We reviewed competitor payment orchestration models, identified gaps and designed the reference architecture. We then organised the roadmap into epics and prepared the technical backlog before development began.

Development. We worked in Agile sprints with the BKN301 team, combining analysis, design and development. We adjusted priorities as our understanding of the payment domain developed.

Coaching. BKN301’s internal team worked with us from the start. Training sessions and ongoing technical support helped them build the skills to manage the platform independently.

Quality. Automated tests and ongoing quality assurance accompanied development throughout the project.

bkn301 klilrway 301pay diagram

Architecture and features

The platform uses:

  • Front-end: Angular
  • Back-end: .NET Core, independent microservices
  • Database: MongoDB, chosen for speed and flexible document structure
  • Integration: API Gateway with REST services connecting international networks and external providers
  • Deployment: automated CI/CD pipelines

Its main features include:

  • Real-time administration and monitoring dashboard
  • Reconciliation and reporting modules
  • Omnichannel payment management: web, mobile, pay-by-link, social
  • API interfaces for e-commerce and merchant integration
BKN301 Payment Plaftorm Screenshot

Results

The platform reached production with the following results:

  • 100,000 transactions a week on average, with peaks of 400,000 during holiday periods
  • 40% reduction in deployment times through automated pipelines
  • Support for PCI DSS, SCA and 3DS requirements

The modular architecture supports adding payment networks and modules. BKN301’s team adopted Agile practices and developed the technical skills to take ownership of the platform.

301pay handles omnichannel payments for businesses and merchants across San Marino and the EU.

Outmatic worked with us from the first idea through to delivery of 301pay. They helped us turn that idea into a fintech platform that could scale.
Davide Salviani, Head of Product