Payment software delivery, by the numbers
02
- PCI-scope-reduced design
- SAQ A
04
- week delivery cycles
- 10-16
A direct payment gateway integration handles the transaction itself: the card authorisation, the capture, the refund. The payment product starts above the gateway, 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, how failed transactions retry and surface their failure reason. These are product decisions the gateway's SDK doesn't make for you.
We build payment software 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.
Capabilities
What we build
01Gateway integration and multi-provider routing
Integration with your acquiring layer 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.
- Built with
- Stripe · Adyen · Checkout.com · Braintree
One-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 so raw card data never touches your application, keeping PCI scope to SAQ A or SAQ A-EP.
- Built with
- Stripe Elements · Adyen Drop-in · 3DS2
03Multi-currency processing and FX
Live 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.
- Built with
- ECB rates · iDEAL · SEPA · UPI · Pix
04Payment reconciliation automation
A 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 settlement
Built 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.
- Built with
- Stripe Connect · Adyen Platforms
06Fraud detection and PCI DSS
Velocity controls limit transaction count and value per card, account, IP, and device within a rolling window. Rule-based screening and third-party fraud scoring (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.
- Built with
- Stripe Radar · Kount · Sardine
07Subscription billing and recurring payments
Plan 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.
How we work
From scope to live payment platform
- Week 1
01Payment 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-4
02Architecture 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-14
03Build and integrate
Gateway integration, checkout, reconciliation, and settlement built in parallel, tested against processor sandboxes every sprint.
- Final 2 weeks
04Launch and reconciliation validation
Production launch with the reconciliation engine validated against real settlement files before go-live.
Why us
Why fintech teams choose RaftLabs
01Senior engineers build what they scope
The engineers who assess your payment flows also build the solution. No bait-and-switch, no offshore handoff after the contract is signed.
02Fixed price before development starts
We scope the work, calculate the cost, and lock it in writing before any development starts.
039 years and 100+ products shipped
Clients include Vodafone, T-Mobile, Aldi, Nike, Cisco, and Lockheed Martin. Track record building payment, marketplace, and fintech platforms.
04PCI scope reduction is a design principle
No card data in your database, logs, or error reporting. Processor-hosted fields and tokenisation keep you at SAQ A or SAQ A-EP wherever the flow allows it.
05We'll tell you when you don't need us
If a direct Stripe or Adyen integration covers your requirement, we say so. Custom payment infrastructure is justified by real flow complexity, not built by default.
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.
