There is no public API yet. Paynecta’s HTTP API exists and runs the
dashboard, but it is internal: it authenticates people, not programs, and it
has no API keys, no webhooks and no stability guarantee.Building against it today means building against something that will change
without notice.
Why it is not open yet
Three things a public API needs that the internal one does not have:
Credentials for programs, not people
Today’s tokens belong to a person and end when that person signs in
elsewhere. A server integration needs a key of its own, one that can be
scoped and revoked without touching anybody’s sign-in.
Webhooks
A payment arriving is something we tell you about. Polling is not an
integration, and signed delivery with retries is not a detail that can be
added afterwards.
A promise not to break it
A version, a deprecation policy, and the discipline to keep both. Publishing
endpoints without that is worse than publishing nothing.
What you can rely on now
The dashboard at app.paynecta.co.ke does
everything Paynecta can do today. Nothing is hidden behind an API that is not
also on screen.
Tell us what you would build
If you are waiting on this, it helps to know what for: collecting from your own
checkout, reconciling settlements into your accounting system, something else
entirely. Email
support@paynecta.co.ke and say what you need.
It shapes what ships first.
