CASE STUDY

B2B Credit Card Payment Platform

An early-stage FinTech startup wanted businesses to pay rent, GST and vendors by credit card. We built the full platform, and proposed the architecture that made it production-safe.

FinTech Fixed ProjectFull Product BuildPaymentsKYC
3
Surfaces shipped
Gateway + OTP
Fallback layers
FinTech
Industry

Overview

A fixed-scope engagement for an early-stage FinTech startup with a clear vision: a mobile-first platform that lets businesses make credit card payments to recipients who traditionally can't accept them, such as rent, GST and vendor payments. XLORIT turned that vision into a fully working product as the first and only development team.

ClientB2B credit card payment platform (anonymized)
IndustryFinTech
Tech Stacks
FlutterDjangoReactPayment gateway adapterOTP providersKYC verification
Challenge

Credit cards work everywhere, except where businesses actually need them most

Businesses routinely need to pay rent, taxes and vendor invoices, but most recipients can't accept credit cards. The client wanted to bridge that gap through a mobile app with full KYC verification, a multi-gateway payment infrastructure and an admin panel for real-time control. All of it was money-sensitive, and all of it required zero tolerance for silent failures.

Key Challenges
  • KYC identity and beneficiary verification before any transaction
  • Multiple payment gateways that needed fallback logic
  • OTP-based authentication that couldn't become a single point of failure
  • A fully configurable admin layer for a money-sensitive product

Our Approach

We built the full platform, and proposed the architecture that made it production-safe.

01
Three surfaces from zero
Built the Flutter mobile app, Django backend and React admin panel with no inherited codebase, including a full KYC flow (OTP sign-in, identity and beneficiary verification) gating every transaction.
02
Multi-gateway payment adapter
Created a single adapter layer across all gateways with automatic fallback when one fails. When the client later wanted to enable or disable gateways by commission rate, it was a configuration change, not a code change.
03
OTP that can't lock users out
Proposed and built multi-provider OTP fallback: if the primary SMS provider fails, the system switches to the backup automatically. Without it, a provider outage would have blocked every login and transaction.
04
Traceable and controllable
Added structured logging on every user action, transaction attempt and gateway call, plus RBAC in the admin panel for gateway configuration, live transaction monitoring and user access.
Outcome

Built for what can go wrong, not just what should go right

In FinTech, a payment routed to a failed gateway, an OTP that never arrives or a transaction with no audit trail breaks user trust permanently. We identified those risks, proposed the solutions and built them into the architecture from the start. The client came to us after smaller features and trusted us with the full build; the gateway fallback, OTP redundancy and admin layer were all our proposals, approved as additions to the original brief.

Key Outcomes
  • 0 → fully shipped mobile app, backend and admin panel
  • Multiple payment gateways with adapter-based fallback
  • Multi-provider OTP with automatic fallback
  • Full identity and beneficiary KYC verification flow
  • Structured logging on every user action and payment event
  • Validated in early production with real transactions
“

As an early-stage startup, we needed a team that thinks like a co-founder on the tech side, not just people who write code. That's exactly what we got.

FT
FinTech client
Early-stage FinTech startup

Found This Useful?

Explore more projects or share this with someone who might find it useful.

Building a payment-sensitive product?

Most dev teams build for the happy path. We build for everything else.

Book a Call
B2B Credit Card Payment Platform
Surfaces shipped
3
Fallback layers
Gateway + OTP