Collection
STK Push request accepted
CheckoutRequestID ws_CO_240820261525...
Unified Payment Infrastructure
Payments infrastructure built for how Africa moves money.
Zadhron Payments helps applications and businesses collect, send, verify, and monitor payments through a unified API and a shared operational control plane.
Collect
STK and callback-aware collection flows
Send
Controlled payout and disbursement operations
Observe
Request IDs, logs, callbacks, and health signals
Live Operation
POST /api/mpesa/b2c
Completed
Amount
KES 24,500.00
Destination
M-Pesa
Latency
327 ms
Request ID
zadhron_
48fd91aa-2f1c
48fd91aa-2f1c
Webhook
/api/mpesa/callbacks/b2c/result
Delivery Status
Accepted and correlated
200 OK
Gateway Event
Provider response
OriginatorConversationID mapped
Structured result
Normalized gateway response returned
Operating Model
One integration. Multiple ways to move money.
Zadhron Payments centralizes payout execution, collection flows, callback handling, transaction verification, and gateway observability around a single authenticated surface.
Payout
B2C
Controlled disbursement initiation with idempotency-ready request handling.
Status Query
Verify transaction state, retrieve provider result codes, and reconcile operational outcomes.
Webhook
callback received
payload sanitized
transaction updated
Service Health
OAuth
Provider reachability and token readiness are surfaced directly.
Platform Capabilities
Payments infrastructure shaped around real gateway work.
01
Collect
Accept money into applications through supported collection flows and callback handling.
02
Send
Initiate controlled payouts and disbursements across the gateway's authenticated M-Pesa operation surface.
03
Verify
Query transaction state, inspect provider codes, and reconcile outcomes with a normalized response model.
04
Monitor
Observe request logs, callbacks, transaction lifecycles, and provider health through a shared operational layer.
Developer Experience
Build around an authenticated payment surface, not a scattered provider maze.
The current gateway exposes authenticated `/api/mpesa/*` operations and normalized responses. The SDK shape below is presented as a future developer experience goal, while the REST shape shown remains truthful to the existing application.
Current REST integration
const response = await fetch(
"https://payments.zadhron.com/api/mpesa/b2c",
{
method: "POST",
headers: {
"Content-Type": "application/json",
"x-zadhron-app-id": "app_live",
"x-zadhron-app-secret": "••••••••"
},
body: JSON.stringify({
phoneNumber: "2547••••••••",
amount: 2500,
remarks: "Payout"
})
}
);Normalized response
201 Accepted
requestId zadhron_48fd91aa...
operation
b2c
status
accepted
provider
M-Pesa
Infrastructure Principles
The API surface is designed around control, traceability, and clean failure modes.
Authentication
Separate application authentication from administrator sessions.
Idempotency
Prepare payout and money-moving operations for retry-safe execution.
Structured Errors
Return normalized gateway errors instead of leaking raw upstream responses.
Webhooks
Accept, sanitize, and track callback deliveries as part of transaction lifecycle handling.
Correlation
Attach internal request IDs and preserve provider conversation identifiers.
Auditability
Retain sanitized operational logs and traceable request metadata.
Security & Trust
Security is handled as infrastructure, not page decoration.
Server-side credential handling
Consumer secrets, initiator credentials, and session signing stay on the server.
Scoped application access
Consuming applications authenticate separately from console users.
Request validation
Payloads are validated server-side before payment logic is reached.
Traceable operations
Request IDs, provider IDs, and callback events remain linked through the lifecycle.
Next Step
Build payments into your product.
Start with the current gateway surface today and prepare for a broader Zadhron Payments platform as public onboarding expands.