Unified payments API
Create orders, query status, and issue refunds with a predictable HTTP + JSON contract.
Payment infrastructure for global commerce
Manage payments, refunds, events, and payouts with one straightforward server-side API. Keep your team focused on your business, not payment plumbing.
Order amount
$29.90 USD
ORD_2026_001
Payment lifecycle
POST /v1/orderscheckout_urlpayment.succeededHTTP 200+ $29.90Platform capabilities
The essentials in one API. Every state can be queried, and every movement of funds can be traced.
Create orders, query status, and issue refunds with a predictable HTTP + JSON contract.
Send customers to a signed checkout link without handling payment credentials yourself.
Independent test and live keys lower the risk of accidental real transactions.
Verify signatures, retry failed deliveries, inspect logs, and resend events.
Pending payments and refunds are checked again when a notification is missed.
Track payments, refunds, and payouts in an auditable record of balance changes.
Built for developers
Create an order on your server, then redirect the customer to the checkout URL. Your order reference also acts as an idempotency key, so retries are safe.
View quickstartRequest
curl -X POST https://api.kukopay.com/v1/orders \
-H "X-Api-Key: kuko_test_•••" \
-H "Content-Type: application/json" \
-d '{
"out_trade_no": "ORD_2026_001",
"amount": 2990,
"currency": "USD",
"subject": "Premium plan"
}'Response 201
{
"code": 201,
"data": {
"trade_no": "TRD_SB_9F3A2C7E…",
"status": "pending",
"checkout_url": "https://checkout.kukopay.com/…"
}
}Integration flow
The browser return improves the experience; a verified server-side event is the basis for fulfillment.
Create a merchant account and request a test key to start integration.
Send the amount, order reference, and notification URL to get a checkout link.
Redirect the customer to KukoPay's hosted checkout.
Verify the payment.succeeded event and deduplicate by event ID.
Security by design
Separate environments, signed events, and ledger rules reduce operational mistakes.
Keys are stored encrypted and can be reset by merchants.
Merchant-level API rate limits and optional IP allowlists.
Test and live use independent keys and ledgers.
Idempotent state changes and balance movements have matching records.
FAQ
Public integration docs are at kukopay.com/docs. Keys, orders, and webhook delivery logs are in the merchant portal.
Use a unique out_trade_no when creating an order, then deduplicate webhook events by event ID. You can retry the same order reference after a timeout.
No. Fulfill only after verifying a payment.succeeded webhook; query the order for an additional check.
Open a merchant account, request a test key, and follow the quickstart from end to end.