Mobile PoS and merchant-acquiring platform for a UAE fintech operator
- 10,000+
- transactions in the first three months
- PCI DSS
- audited in 2025
Payment Processing Software Development
Payment processing software that starts above the gateway.
A direct payment gateway integration handles the transaction itself well: authorisation, capture, refund. Custom payment software is the right choice when you need the layer above the gateway, the transaction routing logic, the multi-currency ledger, the reconciliation system, the merchant settlement workflow, and the fraud controls that turn a payment API into a payment product. We build payment platforms for marketplaces splitting payments between buyers and sellers, fintech products embedding payments, and businesses replacing manual reconciliation with an automated system.
Payment gateway integrations with Stripe, Adyen, Braintree, and direct acquirers with multi-provider routing
Custom checkout flows with 3D Secure 2.0, tokenised card-on-file, and PCI scope reduction
Multi-currency processing with real-time FX rates and local payment method routing
Automated reconciliation, marketplace split payments, and merchant settlement
Recent outcomes
Voice AI · Research
6× deeper insights
Text-based interviews converted to automated phone calls
AI Automation · Ops
20k+ txns day one
Manual invoice OCR across 40+ gas stations
Loyalty · Retail
1,062 users in 4 weeks
SuperValu & Centra loyalty platform with receipt validation
SaaS · Logistics
2,000+ shipments yr 1
Multi-carrier shipping hub for Indonesian eCommerce
4.9
on ClutchThe problem
Sound familiar?
Reconciliation team spending hours each day manually matching gateway transactions against bank statements because there's no automated matching system?
Running a marketplace where split payments, seller payouts, and reconciliation still require manual spreadsheet work?
Short answer
RaftLabs builds custom payment processing software for fintech companies, marketplaces, and financial institutions who need payment gateway integrations, multi-currency transaction processing, automated reconciliation, fraud controls, and merchant or seller settlement built around their specific payment model. A validated v1 launches in 10 to 16 weeks at a fixed cost, then grows as volume and complexity rise.
Key takeaways
- Custom payment software is justified when the payment flow exceeds a single processor's out-of-the-box capability - multi-provider routing, marketplace split payments, or multi-currency settlement.
- Processor-hosted card fields (Stripe Elements, Adyen Drop-in) keep raw card data off your servers, reducing PCI DSS scope to SAQ A or SAQ A-EP.
- Dynamic 3DS2 triggering exempts low-risk transactions from friction under PSD2's TRA exemption, preserving conversion on clean traffic.
- A single-currency platform with gateway integration and reconciliation runs $35,000-$75,000; a full multi-currency, multi-provider platform with marketplace payouts runs $80,000-$180,000.
Trusted by
The reconciliation that used to take until lunch.
Every morning the finance team opened three tabs: the bank statement, the gateway settlement report, and the internal ledger. Then they matched rows by hand, one transaction at a time, chasing the handful that didn't line up.
By the time the numbers agreed, half the day was gone. And the mismatch that actually mattered, the one worth investigating, was buried under a hundred that were just FX rounding.
A payment platform doesn't ask the team to find the exception. It clears the matches on its own and puts the exception at the top of a queue, with the bank entry and the nearest settlement record side by side.
The gateway moved the money. Everything above it is the product.
When payment complexity needs more than a gateway integration
A direct payment gateway integration handles the transaction itself: the card authorisation, the capture, the refund. The product starts above that layer. How transactions route between multiple providers for redundancy. How funds from different transaction types separate in the ledger. How platform fees deduct before merchant settlement, and how failed transactions retry and surface their failure reason. These are product decisions the gateway's SDK doesn't make for you.
Payments is now a multi-trillion-dollar layer of the economy. McKinsey's Global Payments Report puts annual global payments revenue above $2 trillion, and the businesses building on top of it increasingly route across several processors, currencies, and settlement models that no single gateway SDK was built to handle. The moment a platform splits a payment, settles to more than one party, or reconciles across providers, the logic moves out of the gateway and into software you own.
Three layers get confused in most briefs. Naming them keeps scope honest.
- Gateway
- The API that captures card data and sends the authorisation request. Stripe, Adyen, Braintree, and Checkout.com are gateways. This layer is a buy, not a build. You integrate it.
- Processor / acquirer
- The regulated entity that moves the money and settles funds to a bank account. You do not build one. You route to one (or several), and your software has to reconcile against each settlement file it returns.
- Orchestration
- The software layer above the gateway: routing between providers, the multi-currency ledger, retries, reconciliation, split payments, and settlement. This is the part you own, and the part this page is about.
We build the orchestration layer for marketplaces managing split payments, fintech platforms embedding payments into a non-financial product, subscription businesses managing recurring billing with dunning management, and businesses replacing manual reconciliation with an automated system.
RaftLabs has been shipping production software since 2015, with a track record building payment, marketplace, and fintech platforms. One team scopes the payment flows and builds the platform, production-grade, compliant, and reliable from day one. No offshore handoff after the contract is signed.
Custom payment software pays off when the flow outgrows the gateway.
Everything on the left should already be true for your operation. Even one thing on the right, and a direct Stripe or Adyen integration is the smarter first step.
A fit
01
A marketplace, platform, or fintech product that splits payments, deducts a platform fee, or settles to multiple sellers.
02
Multi-provider routing, multi-currency settlement, or a transaction volume where automated reconciliation saves more than it costs to build.
03
Real flow complexity above the gateway: a currency ledger, retry logic, or fraud controls your processor's SDK doesn't cover.
Not a fit
- A single currency, a single payment method, and no multi-party settlement, where a direct Stripe or Adyen integration already covers you.
- Low transaction volume where matching by hand still costs less than automating it.
- A standard checkout with no routing, ledger, or settlement logic beyond the gateway.
What we build
What we build
- 01Gateway integration and multi-provider routingIntegration with your acquiring layer, Stripe, Adyen, Checkout.com, or Braintree, via SDK or REST API for payment intent creation, capture, refund, and webhook delivery. Multi-provider routing is a configurable rule engine, by card BIN range, transaction amount, currency, or MCC, with automatic failover to a secondary processor. Every payment intent call carries an idempotency key so network retries never duplicate a charge; webhook events are HMAC-SHA256 verified before updating order state.
- 02Custom checkout flowsOne-click checkout for returning customers via tokenised card-on-file; guest checkout for new customers with no forced account creation. 3D Secure 2.0 integrates for PSD2 strong customer authentication, with dynamic triggering that exempts low-risk transactions from friction under the TRA exemption. Card fields are processor-hosted, Stripe Elements or Adyen Drop-in, so raw card data never touches your application, keeping PCI scope to SAQ A or SAQ A-EP.
- 03Multi-currency processing and FXLive FX rates from ECB reference feeds or a commercial provider, with configurable spread over mid-market. A multi-currency ledger tracks each currency balance separately; settlement conversion applies at transaction time or deferred to the daily batch depending on your FX exposure preference. Local payment method routing extends beyond card by market: iDEAL, SEPA, BACS, UPI, Pix, OXXO, each with its own settlement timeline and refund mechanics.
- 04Payment reconciliation automationA reconciliation engine matches incoming bank statement transactions against gateway settlement reports and the internal ledger, marking matched items reconciled without manual intervention. An exception queue shows the bank entry, the nearest matching settlement record, and the discrepancy, rather than requiring the team to find it themselves. Tolerance handling auto-clears low-value FX-rounding discrepancies; a daily reconciliation report shows the reconciled and unreconciled position across all methods and currencies.
- 05Marketplace and merchant settlementBuilt on Stripe Connect or Adyen Platforms depending on your payout model, PayFac (you as merchant of record) or aggregation (sellers onboard directly). Seller KYC and bank verification complete before first payout. Commission deduction, reserve holds against chargebacks, and automated payout scheduling are configurable per seller tier. Settlement statements show each merchant their transactions, fees, and net payout; chargeback management deducts disputes from the next settlement automatically.
- 06Fraud detection and PCI DSSVelocity controls limit transaction count and value per card, account, IP, and device within a rolling window. Rule-based screening and third-party fraud scoring (Stripe Radar, Sift, Kount, Sardine) combine IP reputation, device fingerprinting, and behavioural signals into a risk score that drives approve, decline, or manual-review routing. Dispute-rate monitoring alerts before your chargeback ratio approaches the card network's compliance threshold: Visa flags merchants at a 0.9% dispute ratio under VDMP, Mastercard at 1.5% under its Excessive Chargeback programme (card-network rules, 2024). Cross that line and you face per-dispute fines and, eventually, loss of acquiring, so the monitoring has to warn early, not report after the fact.
- 07Subscription billing and recurring paymentsPlan management defines billing cycle, price, currency, and trial period per product. A recurring billing engine processes renewals automatically, handling the payment attempt and triggering the next cycle or the dunning sequence on failure. Dunning runs a configurable retry sequence with subscriber communication; upgrade and downgrade handling computes proration automatically. Subscription lifecycle events publish to a webhook for downstream systems.
Pitfalls we plan around
Payment software fails in specific, repeatable ways. Naming them up front is how you know we have shipped this before, not just read the docs.
- Double charges from webhook retries
- Gateways deliver the same webhook more than once, and network timeouts make clients retry a charge that already succeeded. Every write is idempotent, keyed on the payment intent, so a replayed event or retried request updates state once and never bills twice.
- A ledger that drifts from the bank
- When the internal ledger and the acquirer's settlement file disagree, the gap compounds silently until close of quarter. We reconcile against each settlement file on a schedule and surface the exception the same day, not at audit.
- Refunds and chargebacks that lose money twice
- A refund issued while a chargeback is already in flight pays the customer twice. Dispute state is modelled explicitly so a refund, a representment, and a chargeback on the same transaction cannot double-debit you.
- FX rounding treated as a real mismatch
- Most reconciliation exceptions are sub-cent FX rounding, not fraud. Tolerance rules auto-clear those so the exception queue holds only the items a human should actually look at.
- One processor as a single point of failure
- When your only acquirer has an outage, every payment stops. Multi-provider routing with health-checked failover keeps authorisation flowing to a secondary processor while the primary recovers.
Proof it works
Proof
- 10,000+
- transactions in the first three months on a mobile PoS and merchant-acquiring platform we built
- RaftLabs, UAE fintech merchant-acquiring platform
- 2 processors
- PayBy and Stripe behind a single transaction ledger, with automatic routing
- RaftLabs, UAE fintech merchant-acquiring platform
- PCI DSS
- audited in 2025; card data tokenised, never stored in plaintext
- RaftLabs, UAE fintech merchant-acquiring platform
Clients include Vodafone, T-Mobile, Aldi, Nike, Cisco, and Lockheed Martin, across AI, SaaS, mobile, automation, and enterprise platforms.
A UAE fintech operator came to us to replace hardware card terminals with a mobile app. Merchants now take contactless cards, QR codes, tap-to-pay, and payment links from a phone. Two payment processors, PayBy and Stripe, run behind a single transaction ledger. Card data is tokenised, never stored in plaintext. The platform processed 10,000 transactions in its first three months and passed a 2025 PCI DSS audit. This is the assess-then-rebuild path for a payment MVP that has outgrown a single processor or cannot yet meet compliance and scale. Read the full case study.
Have a payment software project?
Tell us your payment model, the currencies, the gateways, and where the current process relies on manual reconciliation. We'll scope a payment platform built around your actual transaction flows.
How it works
From scope to live payment platform
- Week 101
Payment flow and processor scoping
We map your transaction flows, settlement model, and processor requirements. You leave week 1 with a written scope document and a fixed-price quote.
- Weeks 2-402
Architecture and PCI-scope design
Ledger structure, routing rules, and PCI scope-reduction approach designed and confirmed against your processor stack before development starts.
- Weeks 5-1403
Build and integrate
Gateway integration, checkout, reconciliation, and settlement built in parallel, tested against processor sandboxes every sprint.
- Final 2 weeks04
Launch and reconciliation validation
Production launch with the reconciliation engine validated against real settlement files before go-live.
What clients say
What our clients say
Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.
Charles E.
USAEntrepreneur at Aggie Technologies
All of the sprints were completed on schedule and on budget. We highly recommend RaftLabs!
Where you land in that range depends on scope, not negotiation:
- Single-currency platform, $35,000-$75,000
- A single acquiring integration, custom checkout, and automated reconciliation for one currency.
- Multi-currency, multi-provider platform, $80,000-$180,000
- Multi-provider routing with failover, a multi-currency ledger, marketplace split payments and payouts, and fraud controls.
What it costs
Custom payment software, starting at $35,000.
Gateway integrations, a multi-currency ledger, reconciliation automation, and the settlement and fraud controls your payment model needs.
Starts at $35,000
A validated v1 in 10-16 weeks. Start with the core gateway integration and ledger, then add reconciliation depth and fraud controls as volume grows.
The largest cost variables are the number of acquiring integrations, marketplace payout complexity, and reconciliation depth. Start with the core flow, add complexity once it's live and processing real transactions.
No hourly billing
Once we scope your first phase, that price is locked in writing. No hourly billing, no surprise invoices for work outside the agreed scope.
Validated before go-live
The reconciliation engine is validated against your real settlement files before launch, so the numbers agree on day one, not week three.
Payment software rarely stands alone. Related build work includes fintech automation for KYC, reconciliation, and fraud workflows, AI for fintech for transaction scoring and anomaly detection, and business process automation for the settlement and back-office steps around a payment platform. For the wider track record, see our fintech software work.
Stay on topic
More on fintech
Article
How to Build a Trading App Like Robinhood: Cost, Phases, and the Brokerage API Decision
Building a trading app like Robinhood costs $50K-$130K over 14-28 weeks. This guide covers brokerage API options (DriveWealth, Alpaca, Apex Clearing, Interactive Brokers), phased feature sets, and the regulatory decisions that determine your actual timeline.
Read more
Article
Cost to build a payment app like Stripe: a guide for niche fintech founders
Stripe works fine for most businesses. But healthcare platforms, real estate escrow operators, B2B invoice financers, and gig economy payout engines all hit walls with off-the-shelf processors. This is what building a custom payment layer actually costs, how long it takes, and when it pays off.
Read more
Article
B2B Wholesale Marketplace Development: Costs, Features, and When to Build vs. Buy
Faire charges 25% on every new retailer order. At $10M/year in wholesale volume, that is $1.5M-$2.5M leaving your business annually. Here is what it costs to build your own platform, what features matter, and when custom software actually makes sense.
Read moreFrequently asked questions
A direct Stripe or Adyen integration is the right choice for a straightforward payment model: a single currency, a single payment method, no multi-party settlement. Custom becomes right when the flows are more complex: a marketplace splitting payments between buyers and sellers, a platform deducting a fee before settling to merchants, multi-provider routing with automatic failover, a multi-currency product requiring a currency ledger, or a business whose volume has reached the point where automated reconciliation saves more than the cost of building it.
PCI DSS applies to any business that stores, processes, or transmits cardholder data. Most payment platforms avoid the full audit burden through scope reduction: processor-hosted card fields (Stripe Elements, Adyen Drop-in, Braintree Hosted Fields) mean raw card data never touches your servers, reducing PCI scope to SAQ A or SAQ A-EP, both self-assessed rather than a full QSA audit. Tokenisation for card-on-file stores a processor-generated token, which has no PCI scope. We build with scope reduction as a design principle from the start: no card data in your database, logs, or error reporting.
Yes. Live FX rate feeds (ECB reference rates or a provider like Open Exchange Rates) power local-currency pricing at checkout. Local payment methods extend beyond card: iDEAL for the Netherlands, SEPA for Europe, BACS for the UK, UPI for India, Pix for Brazil, OXXO for Mexico. FX conversion can happen at transaction time (rate locked at checkout) or settlement time (deferred cost, simpler reconciliation). We scope the currency list, market list, and payment rails during discovery and confirm processor coverage before development starts.
Yes. Common integrations cover Xero, QuickBooks, Sage, and NetSuite. The integration posts each settled transaction or settlement batch to the correct nominal code, reconciles the payment platform's ledger against the accounting system's bank account, and flags discrepancies for investigation. For a custom general ledger or ERP, we build the integration using the available API or file-based exchange.
A payment platform with a single acquiring integration, custom checkout, and automated reconciliation for a single currency typically runs $35,000 to $75,000. A full platform with multi-provider routing, multi-currency support, marketplace split payments, and fraud controls typically runs $80,000 to $180,000. The largest cost variables are the number of acquiring integrations, marketplace payout complexity, and reconciliation depth. We scope every project before pricing and deliver at a fixed cost.
Work with us
Tell us what you need. We'll tell you what it would take.
We scope Payment Processing Software Development in 30 minutes. You walk away with a clear cost, timeline, and approach. No commitment required.
- Scope and cost agreed before work starts. No surprises. No obligation.
- Working prototype within 3 weeks of kickoff.
- Pay by milestone. You see progress before each invoice.
- 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
- All conversations are NDA-protected.