Payment Gateway Integration & Custom Gateway Development

Integration across mobile money, card and bank rails behind a single internal interface, with the failure modes handled explicitly. Payment integration is defined by its unhappy paths — timeouts, duplicate callbacks, partial reversals — and that is where our engineering effort concentrates.

Request a proposal for this capability Speak with the practice lead

Business outcomes

What you get from the engagement

Multiple payment rails behind one internal payment interface
Idempotent handling of duplicated and out-of-order callbacks
Failed and pending transactions resolved by automated reconciliation
Rail-level success rates reported and alertable

Technical capabilities

What we do inside it

Mobile money integration including M-Pesa Daraja
Card acquiring and 3-D Secure integration
Bank transfer and PesaLink integration
Payment orchestration and rail failover
Webhook, callback and idempotency engineering

Architecture and stack

How we build it

Architectural position

Every inbound callback is verified, deduplicated by provider reference and processed exactly once. Payment state transitions are append-only.

Representative technologies

Technology selection follows the requirement. This list is representative of engagements in this service line, not a constraint we impose on yours.

Service assurance

SLA, compliance and governance

Engagements in this service line are delivered under the Platinum service tier by default, against the compliance obligations below. Both are set in the engagement contract, not by this page.

Default tier

Platinum — 99.95% availability target, P1 response within 15 minutes, coverage 24 × 7 × 365.

Compliance scope

Governance

Written architecture decision records, weekly delivery reporting, and a documented handover comprising runbooks, source and credential transfer at engagement close.

Intellectual property

Client-commissioned work product vests in the client on payment. Source escrow available on request.

Service level tiers, availability targets and response commitments
Tier	Availability target	P1 response	P1 resolution target	Coverage	Service credits
Platinum	99.95%	15 minutes	4 hours	24 × 7 × 365	Yes
Gold	99.9%	1 hour	8 hours	24 × 5 plus on-call	Yes
Silver	99.5%	4 hours	2 business days	09:00–18:00 EAT	No

Publication gate G-05 — outstanding

These values illustrate the structure of the table. Each figure must be confirmed by whoever will be contractually bound by it, and the availability targets must be achievable on the underlying cloud provider SLAs before publication. Publishing a 99.95% target on infrastructure whose own composite SLA is lower creates an obligation that cannot be met.

Also in FinTech & Payments

Related service lines

Institutional Billing, Invoicing & Subscription Engines

Billing systems that compute the correct amount under proration, mid-cycle change, tax and multi-currency, and that produce an inv...

Core Transaction Processing & PCI-DSS Compliant Architecture

High-integrity transaction processing with cardholder data scope deliberately minimised. The most valuable architectural decision...

Request for Proposal

Begin with a scoped conversation, not a sales call.

Our intake is structured so that the first response you receive is technical. Tell us which of the following describes your position and we will route your enquiry to the engineering lead who owns that practice.

Enterprise modernisation An existing system — core, legacy or on-premises — that must be migrated, re-architected or integrated. New product build A platform to be taken from concept or specification to production under a fixed scope. Team augmentation Senior engineering capacity embedded into an existing team and roadmap.

Submit a Request for Proposal Speak with our engagement desk

Enquiries are acknowledged within one business day and answered substantively within two business days. All submissions are treated as confidential; a mutual non-disclosure agreement is available before disclosure of scope.