Checklist · IB Commission Operations
CPA Qualification: An Affiliate Evidence Ledger
Build a CPA qualification ledger linking referrals, account checks, funding, eligible activity and approval to the exact partner agreement.
Published Updated
Published by FxTrusts, a supplier of brokerage and prop firm technology. Prepared with AI-assisted research and drafting; reviewed against the cited public sources. Examples are illustrative. Product links describe our services.
Quick answer
A cost-per-acquisition (CPA) qualification ledger records whether a referred account meets the acquisition conditions in its partner agreement. Referral, account verification, funding, activity, approval and payment are separate states. A registration or deposit alone should not be treated as proof that every condition has been satisfied.

Translate the agreement into observable conditions
List each required condition, its evidence source and the person responsible for interpreting it. Define what counts as a new customer, the eligible country or account type, the funding basis, the activity threshold and the deadline. A phrase such as active customer is too vague for an automated decision. OANDA describes region-dependent deposit and trading requirements in its own affiliate program; that is an example of why another program must use its own current signed terms.
Sources for this section
- OANDA Partners: types of partner programmeswww.oanda.com
Keep evidence status separate from eligibility
Missing evidence is different from evidence of failure. A verification service still processing an account may leave a condition unknown. A confirmed ineligible account fails a specific rule. Store the status, observed value, timestamp and evidence reference for each condition. If an import later supplies a missing trade, recompute the affected qualification without inventing an earlier approval time. A reviewer should be able to explain which fact changed and why it changed the outcome.
Make qualification repeatable without repeated payment
Version the evaluation evidence, but keep one durable acquisition-entitlement identifier for the acquired customer and the program's one-time award. A new rule version, changed attribution or repeated event must not create another entitlement. Check previous approvals and payments before approving a reevaluation; corrections should link to the existing award. Record the partner assignment separately from entitlement identity. For hybrid programs, subsequent revenue-share accruals have their own earning events, while the already approved or paid acquisition award remains identifiable across every reevaluation.
Limit the information shown to partners
A partner statement may need a condition summary and a reason code, while identity documents or detailed investigation notes belong in restricted systems. Keep evidence references and audit records proportionate to the task. OWASP logging guidance supports meaningful event records while excluding secrets and unnecessary sensitive data. Document the referral and consent records that the applicable workflow requires; this ledger does not create permission to collect or disclose customer information.
Sources for this section
- OWASP Logging Cheat Sheetcheatsheetseries.owasp.org
Four fictional qualification records
This test agreement awards USD 200 after approval, requires a verified new account, at least USD 500 net funding, two eligible closed lots and completion within 30 days of referral. All four records are inside the window. Net funding here means qualifying deposits less withdrawals; these are invented test terms, not an OANDA or FxTrusts offer. Only A is ready for an approval decision, and none is marked paid merely by this calculation.
If A is later paid under version 1 and reevaluated under version 2, retain the same acquisition entitlement and its USD 200 payment reference. The new evaluation creates no second acquisition award; any permitted correction follows the existing entitlement.
| Record | Observed evidence | Qualification result |
|---|---|---|
| A | Verified; USD 600 net funding; 3 lots | Ready for approval |
| B | Verified; USD 700; 1.5 lots | Activity threshold unmet |
| C | Identity review pending; USD 700; 3 lots | Verification evidence pending |
| D | Verified; USD 400 net funding; 3 lots | Funding threshold unmet |
Implementation checklist
- Write each condition with a source, deadline and rule version.
- Distinguish unknown, unmet, eligible, approved and paid states.
- Test that replay, rule-version changes and reassignment cannot duplicate a previously paid acquisition award.
- Expose only the evidence summary the partner is entitled to see.
Sources
These documents support the reference. Check the original publication for current requirements and the limits of its scope.
- OANDA Partners: types of partner programmeswww.oanda.com
- OWASP Logging Cheat Sheetcheatsheetseries.owasp.org
Continue with the broader guides
Connect this reference to platform selection and the wider operating workflow.
