For banks and payment businesses
Discuss Payments Code
Tell us about your channels, providers and volumes — we’ll suggest where to start.
Discuss a solutionPayments Code · Payment acceptance
One hub for every payment your bank accepts
Payments Code centralizes payment acceptance across internet and mobile banking, teller desks, ATMs, kiosks, agent networks and APIs — with one service directory, flexible fees and 24/7 operation.
- payments a day in a single deployment
- up to 2M
- service providers per deployment
- 2,000–20,000
- average time to set up a simple service
- ~1 hour
Types of services you can accept payments for
01The problem
Payments shouldn’t be integrated in every system separately
In most of our projects, Payments Code replaced payment functions built separately into core banking, remote banking and other systems — each with its own provider integrations. Banks usually connect one channel first and then the rest.
Without a hub
- Payment functions duplicated in core banking, remote banking and branch software
- Each system integrated with service providers on its own
- Remote channels usually cover fewer than 500 providers
With Payments Code
- One service directory for every channel
- Gateways to large aggregators and state services, plus direct contracts
- A simple service set up in about an hour — once, for all channels
- Technical reconciliation with aggregators and providers in one place
02Who it’s for
For anyone who accepts payments at scale
Banks with retail business
A single payment center for every customer channel — from branch cash desks to mobile banking.
Companies accepting payments for their services
Mobile operators, lotteries, utilities and others that collect payments from many customers.
Banks building agent networks
Agents and sub-agents work in a web application with software for teller desks, kiosks and smartphones, and cooperation with the bank is fully automated.
03How it works
Every channel in. Every provider out. One set of rules.
Channels connect to Payments Code through standard interfaces or its own API. The hub routes each payment, calculates the fee online, checks it against anti-fraud rules and posts it to core banking.
Acceptance channels
- Internet banking
- Mobile banking
- Teller desks
- ATMs and kiosks
- Agent networks
- API
Payments Code
One service directory · one set of rules for every channel
Payment processing
- Service directory
- Multi-step scenarios
- Routing
- Online handlers
Money and control
- Fee engine
- Recurring payments
- Anti-fraud
- Reconciliation
Extension
- Gateway SDK
- BCIT
- Reporting engine
- UI plugins
Destinations
- Billing aggregators
- State services
- Providers under direct contract
- Core bankingPostings via BCIT
- Processing and anti-fraud
04Capabilities
What Payments Code does for the bank
Unlimited providers and services
Built-in gateways to the largest billing aggregators and state services, direct contracts and bulk loading of services.
Fees that earn
Simple or formula-based fees by any parameter, calculated online and shown before payment.
Security and anti-fraud
Transaction integrity, secure key storage, password policy, staff audit, built-in anti-fraud and a standard API for an external anti-fraud system.
Uninterrupted 24/7
Active–active across multiple locations, rerouting via an alternative channel if the primary one fails, updates without downtime.
Recurring payments
Scheduled payments, payments on an event — such as a low phone balance — and payments when debt occurs.
Reconciliation and reporting
Technical reconciliation with gateways and agents, a reporting engine and tag-based full-text search.
05Fee engine
Price every payment the way your business needs
Fees can be a percentage, a fixed amount or any formula. They are calculated online and shown to the customer before the payment — and can integrate with the bank’s own fee service if needed.
Set fees by
- Channel
- Point or group of points
- Service or group of services
- Payment instrument
- Payment amount
- Payment time
- Data plans
- Fee charged to the recipient
Payment instruments
- Own card
- Other bank’s card
- Cash
- Credit
- E-money
- Bonus points
06Integration and extension
Built to be extended by your team
Almost all of our banking clients build payment gateways themselves with the Gateway SDK. Integration with anti-fraud, core banking and the processing center is standard practice.
Standard extension points
- Gateway SDK — build payment gateways in-house
- Payment gateway implementations
- Online handlers — transaction processors, kernel method handlers, API request plugins
- BCIT — chart of accounts and postings to core banking
- 1010Code input protocol, extensible
Additional extension points
- Reconciliation service
- Customised reporting engine
- Incoming protocol converters
- UI plugins for the Payments Code interface
- Plug-ins for task automation
07Performance
Scales horizontally, stays predictable
In the latest load test, one server processed 6.6 million operations over 48 hours — 38.6 operations per second. Capacity grows by adding operation server instances.
- operations on one server in a 48-hour load test
- 6.6M
- payments a day in a single deployment
- up to 2M
Operation server cluster
Recommended for stability and higher throughput.
Database cluster
Recommended for fault tolerance; the main load is on the database server.
Light on application servers
Performance depends least on application-server RAM and disk.
08Use cases
Where Payments Code runs today
- 01
Bank-wide payment hub
All customer channels connected to one hub, replacing payment logic scattered across systems.
- 02
Branch cash desks
Payments in cash, by card and from bank accounts at the counter.
- 03
Auto-payments
Recurring payments across channels, from the off-the-shelf solution.
- 04
Telecom and billing
Customer payment acceptance for a large mobile operator through kiosks and offices.
09Implementations
Thousands of providers. Millions of payments.
Most of our clients are under NDA. Figures come from live deployments.
- 01
Bank · Europe
One of Europe’s largest banks, 7M+ clients
- Payments Code
- ATM Code
- Challenge
- Centralize payment acceptance across branches, self-service devices and remote banking.
- Solution
- Payments Code as the central hub for cash desks, kiosks, ATMs, internet and mobile banking, plus recurring payments. ATM Code with a personal account on self-service devices.
Result
- providers in the payment hub
- 8,000
- branch cash desks
- 3,200
- ATMs and kiosks
- 4,000 + 1,800
- 02
Telecom · Central Asia
One of the largest mobile operators in Central Asia
- Payments Code
- Challenge
- Accept customer payments reliably across kiosks and service offices at national scale.
- Solution
- A payment acceptance system built on Payments Code.
Result
- transactions a day
- 500,000+
- payment services
- 300+
- service points
- 100+
- 03
Bank · Eastern Europe
Bank with 497 offices in 224 cities and a 38,000-device partner network
- Payments Code
- ATM Code
- Challenge
- Unify payment acceptance across cash desks, terminals, ATMs and auto-payments, and connect instant payments.
- Solution
- Payments Code for all acceptance channels, ATM Code to extend ATM functionality, payment acceptance at teller desks, integration with the instant payments system.
Result
- service providers
- 10,000+
- ATMs
- 4,400
- cash desks
- 800
Bring every payment into one place
For partners
Offer Payments Code to your clients
Offer Payments Code to banks in your market and earn on delivery.
Become a partner