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.
Frequently asked questions
Do I have to apply before I can receive revenue share?
Yes. You must submit the Developer Program application and be approved. Until you are in the program, we do not accrue or pay developer revenue share—even if you already use our API or plugin.
I integrated Paystack, Flutterwave, and others for years and never got a share—is this different?
Many gateways treat developers as implementation help while the brand captures all long-term value from processing. Our program is meant to fix that gap: when you are approved and attribution is valid (for example your Business ID on a qualifying integration), you can earn a defined share on eligible volume—not just a one-off project fee.
Why do I need my own CheckoutPay business account if I only build for clients?
Your share is credited to your business account—the same place your Business ID lives—so you have statements, tax identity, and withdrawals in one profile. You are not “becoming the merchant”; you are claiming the developer attribution channel we use to pay you.
Where do I find my Business ID?
After you create a business account, use the Business ID shown in your dashboard (alongside API keys and business settings). That is the value you paste into the WordPress plugin’s developer / partner field.
Does the merchant’s Business ID replace mine?
No. The merchant connects their store with their own API credentials. Your Business ID is a separate field used only to attribute the developer share to your account.
Is it safe to put my Business ID on a client’s WordPress site? What does the store owner see?
The field is for attribution, not for sharing secret keys. Merchants should know you are listed as the integrating developer and that the ID is how we route your revenue share. Treat it like any other admin setting: only people who should manage payments should have wp-admin access.
Does my client pay extra so I get paid?
Your share comes from the program’s agreed economics on eligible processing—not from sneaking a hidden surcharge onto the shopper. The headline rate on our Developer Program page is kept in sync with admin configuration; your partner agreement may include additional detail.
Can my agency use one Business ID for every client site?
Usually yes: one partner business account, one Business ID, many stores—each installs the plugin with the same developer field so volume rolls up to you. If you need separate entities for tax or accounting, create separate business accounts and use the matching IDs.
I only do custom code / Laravel / mobile apps—no WordPress. How do I get paid?
The WordPress field is the first simple pattern we ship; the same principle applies elsewhere: an explicit partner or developer identifier we agree at onboarding (metadata, referral codes, or documented API patterns). Contact us with your stack so we can align attribution before go-live.
Can I get paid on stores I built before the plugin had a developer field?
Retroactive credit is not guaranteed. Once the field is available, add your Business ID and apply to the program; we will confirm what history—if any—can be attributed fairly.
What if someone removes my Business ID from the plugin after launch?
Attribution follows what is configured in production. If the ID is removed or overwritten, new volume may no longer map to you until it is restored. Disputes between you and a merchant are a commercial relationship; we can only pay against valid, current attribution and program rules.
Do test or sandbox transactions count toward my share?
No. Revenue share applies to qualifying production volume under the program. Test keys and sandbox traffic are for integration quality, not payouts.
Does every integration automatically qualify?
No. You should apply to the program, meet technical and compliance rules, and use production traffic with a valid Business ID (or approved equivalent). We may decline or pause partners if attribution is unclear or terms are breached.
Can I stack this with another referral or affiliate program?
Stacking is governed by your partner agreement. Default assumption is one primary developer attribution per merchant integration unless we document an exception.
What if my client already has an account?
You can often still add your Developer Business ID in the plugin when the program allows it for that merchant. Migrations and legacy setups vary—contact us during application so we can confirm the cleanest path.
Where do I get API keys and documentation?
Start at the Developer hub and API documentation. Product downloads and plugin details are linked from Products.
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.