PaalTech
PaalTech
Payment infrastructure PaalPay

One payment layer in front of every gateway.

A self-hosted payment service that sits in front of Paystack and Hubtel, so PaalTech applications create a payment intent once and receive a signed, verifiable result - whichever gateway processed it.

Our role
Payment service behind PaalTech systems
Status
Internal infrastructure
Core technology
Laravel · PHP · REST API · Paystack · Hubtel

Every product that takes money needs the same plumbing: initialise a payment, send the customer to checkout, handle the gateway's callback, verify the transaction and reconcile it. Building that separately into each application multiplies the places where money can go wrong.

We pulled payments out of the individual applications into one service with a single contract. An application asks for a payment intent; PaalPay decides which gateway handles it, and returns the result in the same shape every time.

Applications create payment intents with an API key and an idempotency key, so a retried request never charges twice. PaalPay routes the payment to Paystack or Hubtel, processes the gateway's webhook, and notifies the application with an HMAC-SHA256 signed callback that the application verifies before marking anything paid. Transactions can be re-verified by reference at any time.

04 · How it works

Architecture, simplified

  • Application Creates a payment intent and redirects the customer to checkout.
  • PaalPay Selects the gateway, tracks the intent and processes gateway webhooks.
  • Gateways Paystack and Hubtel handle card and Mobile Money collection.
  • Callback A signed server-to-server callback that the application verifies before acting.
05 · Key capabilities

What the system does

Payment initialisation

Intents created through one API, with amounts in minor units.

Idempotency

Retried requests resolve to the same intent rather than a second charge.

Signed callbacks

HMAC-SHA256 signatures verified before any record is marked paid.

Verification

Transactions re-verified by reference for reconciliation.

06 · Technology

What it is built with

Application

  • Laravel
  • PHP
  • REST API

Integrations

  • Paystack
  • Hubtel
  • Mobile Money
  • Webhooks

Security

  • HMAC-SHA256 signatures
  • Idempotency keys
  • API keys
07 · Outcome
PaalTech systems - including PaalFi and the invoicing on this website - share one payment path, so the rules for verifying and recording money are written once and applied everywhere.

Need something similar?

We take on custom work in payments & integrations and the systems around it.

See our services
More from the portfolio

More from PaalTech

Full portfolio
The PaalFi website at paalfi.com: hotspot and PPPoE billing for MikroTik networks
Connectivity platform In production

PaalFi

A multi-tenant connectivity platform that provisions MikroTik routers over WireGuard, authenticates sessions through FreeRADIUS, and sells access through vouchers, plans and Mobile Money.

  • Laravel
  • PHP
  • MySQL
  • Laravel Reverb
Read the case study
The EventIX organiser dashboard showing ticket sales, check-ins and payments
Ticketing & gate control In production

EventIX

An event ticketing platform that sells online, through agents and over USSD, issues QR e-tickets, and lets gate staff admit attendees from an ordinary phone.

  • Laravel
  • PHP
  • MySQL
  • QR codes
Read the case study
Messaging infrastructure In development

WhatsApp Business Platform

A multi-tenant platform being built on Meta's WhatsApp Business Platform, so that several businesses can connect their own numbers and run their messaging through one system.

  • Laravel
  • PHP
  • MySQL
  • Multi-tenant architecture
Read the case study

Working on something like PaalPay?

Tell us what you are trying to solve. We will tell you plainly whether we can build it, and what it would take.