IN DEVELOPMENT Product concepts shown here describe our intended direction. Availability, provider roles, and commercial terms will be confirmed before onboarding.
START WITH A TRANSACTION
A familiar shape. A connected workflow.
This example connects a buyer, seller, amount, currency, and marketplace reference. It illustrates the direction of the API, not a live contract.
View API Documentation — Coming SoonThere is no public API, SDK, or sandbox to connect to yet.
{
"buyer_id": "buyer_123",
"seller_id": "seller_456",
"amount": 250000,
"currency": "NGN",
"reference": "order_789"
}{
"transaction_id": "txn_example",
"status": "pending"
}API not released. Schema, amount units, and currency availability are not final.
The planned building blocks.
Authentication
The planned API will require authenticated requests and appropriately scoped access. Credentials, authorization mechanisms, and rotation guidance are not yet published.
Transactions
Create and inspect a transaction using a stable reference. Intended states and allowed transitions will be defined in a versioned contract.
Customers
Link buyer context to transactions while limiting the personal information collected. No customer API contract is currently released.
Sellers
Connect seller records with onboarding and verification workflow states. Requirements will depend on the service and use case.
Webhooks
Receive intended notifications about transaction changes. Consumers should be designed to verify messages and handle duplicate or delayed delivery.
Payments
Associate provider payment events with a transaction. These examples do not initiate a real payment or establish provider support.
Payouts
Track payout workflow states and related provider outcomes. Payout timing, eligibility, and supported methods are not yet offered.
Disputes
Connect a dispute with its transaction and supporting context. Workflows, evidence rules, and resolution responsibilities will be defined before release.
Illustrative endpoints.
These paths describe possible operations. They are not callable endpoints; do not send credentials, payment data, or personal information to them.
/v1/transactions/v1/transactions/{id}/v1/transactions/{id}/confirm/v1/transactions/{id}/cancel/v1/sellers/{id}