Developer documentation

Build Paylor payment integrations.

Use these docs for Kenya payments, Global custodial wallet flows, provider callbacks, payment links, and merchant webhooks.

Quickstart

A typical integration creates a payment, waits for Paylor to reconcile the provider callback, then updates your system from a signed Paylor webhook.

1. Create API keys

Create API keys from the merchant dashboard.

2. Initiate payment

Call a local payment endpoint or a Global collection endpoint with your reference.

3. Listen for webhooks

Update your order only after Paylor sends a signed webhook.

Base requestbash

1curl https://api.paylorke.com/api/v1/global/collections \2  -H "Authorization: Bearer sk_live_xxxxx" \3  -H "Content-Type: application/json" \4  -d '{5    "rail": "SASAPAY_KE",6    "msisdn": "0712345678",7    "amount": 1500,8    "currency": "KES"9  }'

Products

The docs are split by the same product areas your dashboard exposes.

Kenya Local Payments

STK Push, B2C payouts, merchant wallets, and local settlement flows.

Crypto Payments

USDT TRC20 payment intents on the TRON network with automatic blockchain confirmation.

Global Payments

Supported provider rails, custodial wallet balances, withdrawals, payment links, and FX display.

Webhooks

Signed delivery events for collections, withdrawals, wallet credits, and failures.

Wallet model

Global Payments is custodial: supported provider collections are reconciled into a Paylor Global Wallet before withdrawals.

CollectCustomer pays through an enabled provider rail such as mobile money or a supported hosted payment flow.

ConfirmProvider callback is validated and mapped to a Paylor transaction.

CreditThe merchant wallet ledger is updated in the transaction currency.

WithdrawMerchant withdraws using the destination channels enabled for that provider.