Why this program exists
I have been a developer for more than ten years. Over that time I integrated payment gateways my clients asked for—names you know, like Paystack and Flutterwave—and many others. The businesses kept running, transactions kept flowing, and the brands got stronger.
What I did not get was a commission. Not a recurring share, not a referral fee tied to the volume I helped unlock. I had effectively become free advertising for those gateways: real implementations, real trust, real revenue—for them—while my upside stopped at the invoice for “integration hours.”
That experience is why CheckoutPay exists, and why we run this developer program. I know the pain from the inside. If you put our API or plugin on a site you build or maintain, we want a fair, documented way for you to earn an ongoing percentage—not goodwill, but a rule-based share credited to your business account when you claim the integration.
How we identify you—and pay you
WordPress / WooCommerce plugin: Developer Business ID
We are adding a dedicated field in our WordPress / WooCommerce plugin so you can claim your work without awkward spreadsheets or disputed “who introduced this merchant?” debates.
- Apply for the Developer Program using our online form: your name, Business ID (if you already have a business account), phone, email, WhatsApp number, and whether you want to join the developer community on Slack, WhatsApp, or both. We review applications and only approved partners are eligible for revenue share.
- Register a CheckoutPay business account if you do not have one yet—that is the account that will receive your revenue share once you are in the program.
- In your business dashboard, use your Business ID (the identifier for that account—we show it where you manage API keys and business settings).
- When you configure the plugin on your client’s WordPress site, you—or the merchant, if you hand off the site—enter your Business ID into the plugin’s Developer / partner Business ID field. The store still uses the merchant’s API credentials for checkout; your ID is only there to attribute the integration to you.
- After approval, eligible volume from that store is tied to your ID. Your shared percentage accrues to your business account—the same account as that Business ID—so payouts and reporting stay in one place you already control.
API-only or custom stacks: we use the same idea—an explicit partner or developer identifier on the integration—so attribution stays auditable. WordPress is the first place we surface it as a simple, copy-paste field.
How the program fits together
You remain the builder helping the merchant go live. You must apply and be approved into the Developer Program first; until then, no revenue share accrues. After approval, we handle processing and you receive a defined share of qualifying revenue when your Business ID (or approved equivalent) is on file and the integration meets program rules. This is separate from normal merchant pricing: it exists so developers are not unpaid distribution for another brand’s growth.
Who qualifies
- Developers, agencies, and freelancers who implement CheckoutPay for third-party merchants and can supply a valid Business ID for payouts.
- Product teams embedding our checkout in WordPress, WooCommerce, or custom applications.
- Partners who keep attribution honest: the merchant knows who built the integration, and your ID reflects the work you actually performed.
What counts as a qualifying integration
WordPress / WooCommerce (plugin + Business ID)
Production use of our official plugin with the merchant’s API keys, plus your Developer Business ID entered in the plugin field so shareable volume can be credited to your business account. Sandbox-only or missing IDs may not qualify.
REST API & server-to-server
Production API keys on behalf of a registered merchant, with webhooks and patterns documented in our API reference. Partner attribution follows the same principle as the plugin: an explicit, approved identifier—not guesswork from IP or domain alone.
Hosted checkout & payment links
Flows that complete on our infrastructure with clear merchant identification and any partner metadata we agree during onboarding.
Attribution & tracking
The Business ID field in the WordPress plugin is the default way we know which developer account to credit, after you are approved into the Developer Program. For other channels, we align on the same idea: a partner or developer identifier you place at integration time, documented in your partner agreement.
If attribution cannot be determined unambiguously—for example, conflicting IDs or missing plugin configuration—that activity may be excluded from payouts until resolved. You agree not to obscure or misrepresent the merchant relationship.
Payouts, minimums, and reporting
Your share accrues to the business account linked to the Business ID you used to claim the integration, only while you remain an approved program partner. Placeholder: add your payout schedule (e.g. monthly net-30), minimum balance, withdrawal methods, and where partners see statements in the dashboard or exports.
Partners are responsible for valid tax and banking information on that business account. We may withhold payouts if fraud checks are open or program terms are breached.
Compliance & merchant consent
- Merchants must understand they are contracting with CheckoutPay for payment processing; your Business ID is for attribution and revenue share, not to hide who processes payments.
- No false claims about rates, approval odds, or regulatory status. Direct merchants to official docs for PCI and data handling.
- Do not store secret API keys in client-side code or public repositories.
- Honor opt-out and data-deletion requests consistent with the merchant’s policies and applicable law.
Application & ongoing eligibility
Participation starts with the online application (name, Business ID if available, phone, email, WhatsApp, and Slack/WhatsApp community preference). We review each submission and may request more detail about your integrations. We may accept, defer, or decline applications at our discretion. Approved partners should keep integrations maintained (security updates, API changes) to remain in good standing.
We may update program terms with notice. Continued participation after changes constitutes acceptance unless you exit the program according to the notice period we specify.
Developer program FAQs
See all FAQs including search for WordPress, API, and developer program topics.
What is the CheckoutPay Developer Program in Nigeria?
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.
Do I need to apply before earning revenue share?
Yes. Submit the application at https://www.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.
How is this different from integrating Paystack or Flutterwave for years?
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.
Where do I put my Business ID on a client WordPress site?
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.
I build Laravel or mobile apps—how do I get paid without WordPress?
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://www.check-outnow.com/contact with your stack before go-live.
Does my client pay extra so I get paid?
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://www.check-outnow.com/developers/program and in your partner agreement.
Do test or sandbox transactions count toward my share?
No. Revenue share applies to qualifying production volume under program rules with valid attribution. Test keys are for integration only.
Can one agency Business ID cover many client stores?
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.
Ready to stop working for free?
Submit the Developer Program application with your contact details and how you want to join our Slack or WhatsApp community. After approval, your Business ID can start earning on qualifying integrations.