A public API is on the way, and is not open yet. We are finishing the dashboard first, because everything the API will do is something the dashboard has to do properly first. This page is where it will be announced, so it is worth checking back.
Paynecta already has an HTTP API. It runs the dashboard, it collects real payments, and it is the same code a public API will be built on. What it is not yet is something you can safely build against: it authenticates people rather than programs, and it changes whenever the dashboard needs it to.

​
Why the dashboard comes first

An API is a promise that something will keep working. That promise is much harder to keep if the thing underneath is still moving, and it is the wrong order to ask developers to build on something we are still changing weekly. So the sequence is deliberate: get every payment flow right where people can see it, let it settle, then expose it.

​
What is being built towards

1

Credentials that belong to a program

Today’s tokens belong to a person and end when that person signs in elsewhere. A server integration needs a key of its own, scoped to what it actually does and revocable without touching anybody’s sign-in.
2

Webhooks, signed and retried

A payment arriving is something we tell you about, not something you poll us for. Signed delivery with retries is not a detail that can be bolted on afterwards, which is why it is being designed in rather than added later.
3

A version, and a promise not to break it

A version number, a deprecation policy, and the discipline to keep both. Publishing endpoints without that is worse than publishing nothing, because it invites people to build on something we have not committed to.

​
In the meantime

The dashboard at app.paynecta.co.ke does everything Paynecta can do today, and every payment method described in these docs is available there. Nothing is hidden behind an API that is not also on screen, so nothing is waiting on this to be usable.

​
Tell us what you would build

This genuinely changes what ships first. If you are waiting on the API, tell us what for: collecting from your own checkout, reconciling settlements into your accounting system, issuing payment links from your own system, something we have not thought of. Email support@paynecta.co.ke with what you need, and we will let you know when there is something to build against.

​
Next

How a payment works

The flow an API would expose, as it works today.

TapFlows

Where money lands, and the model the API will use.