Merchant approval
An administrator reviews and creates each service provider, then issues its private server API key.
One wallet. Many digital services.
A partner payment and service-token platform that lets customers fund a wallet once, then use those credits across approved digital services.
Kendra keeps merchant credentials on trusted servers, creates a time-limited checkout for each customer, and credits tokens only after a payment is verified.
An administrator reviews and creates each service provider, then issues its private server API key.
Token packages and service prices are configured for the merchant from the protected console.
The partner backend requests a short-lived registered or approved guest checkout without exposing its API key.
Paystack verification mints tokens once; merchant services spend them through idempotent server calls.
Merchant onboarding is administrator-managed. Partners receive an integration guide, a private API key, and a hosted checkout that can be added without handling payment credentials in the browser.