Everything you need to integrate CheckoutPay into your application. API reference, webhooks, testing tools, and more.
https://check-outpay.com/api/v1
All API requests require an API key in the header:
X-API-Key: pk_your_api_key_here
Receive real-time notifications when payment status changes. Configure your webhook URL in your dashboard.
payment.approved - Payment verified and approvedpayment.rejected - Payment rejected or expiredSign up and get your API keys from the dashboard
Create payment request using our REST API
Get notified when payment is verified
Use test API keys to test your integration without processing real payments.
Note: Test mode uses the same API endpoints but with test credentials. No real payments will be processed.
See all FAQs including search for WordPress, API, and developer program topics.
Yes. Merchants use REST APIs to create payments, virtual accounts, and subscriptions, with webhook callbacks for success and failure. Start at https://check-outnow.com/api-docs and complete signup for full keys and reference docs in the business dashboard.
Generate API keys from your CheckoutPay business dashboard. Send the secret key in the Authorization header as documented in your account API reference. Never expose secrets in client-side mobile or browser code.
At minimum, handle payment success and failure events so you can fulfill orders or grant access. Verify webhook signatures when provided, respond quickly with HTTP 200, and make handlers idempotent using your payment reference IDs.
Create a payment with amount and customer metadata; CheckoutPay returns account details or payment instructions. When the customer transfers from a Nigerian bank, matching completes the payment and triggers your webhook.
Use test credentials from your dashboard for integration testing. Sandbox transactions are for quality assurance only and do not qualify for developer revenue share.
Store processed event IDs or payment references and ignore repeats. Design fulfillment logic to be idempotent so the same successful payment never ships twice.
Yes. Any stack that can call HTTPS APIs and receive webhooks can integrate. Agencies in the Developer Program should align partner attribution during onboarding at https://check-outnow.com/developers/program.
Public overview lives at https://check-outnow.com/api-docs. After registration, open API documentation inside your business dashboard for endpoints, payloads, and examples tied to your environment.
It is a partner program for developers and agencies who integrate CheckoutPay for clients. Approved partners can earn ongoing revenue share on qualifying production volume—not just a one-off project fee.
Yes. Submit the application at https://check-outnow.com/developers/program/apply and be approved. Until you are in the program, we do not accrue developer share even if you already use our API or plugin.
Many gateways treat developers as implementation help while the brand keeps long-term processing value. CheckoutPay is built so approved partners with valid attribution can earn a defined share on eligible volume.
In the WooCommerce CheckoutPay gateway settings, use the developer or partner Business ID field. The merchant still uses their own API credentials; your ID only routes revenue share to your account.
The WordPress field is the first simple pattern we ship. The same principle applies elsewhere: an explicit partner identifier agreed at onboarding (metadata, referral codes, or documented API patterns). Contact us via https://check-outnow.com/contact with your stack before go-live.
Your share comes from the program economics on eligible processing—not from a hidden surcharge on the shopper. Rates and terms are described on https://check-outnow.com/developers/program and in your partner agreement.
No. Revenue share applies to qualifying production volume under program rules with valid attribution. Test keys are for integration only.
Usually yes: one partner business account and one Business ID across many stores, each using the plugin or API with your attribution field. Separate legal entities may need separate business accounts.