Program analysis
Reconciling developer-tag earnings with paid usage
Use eligible paid spend, attribution, reversals, and daily settlements to explain earnings instead of multiplying raw job counts by an assumed price.
By the easycaptcha team · Published
The developer program attributes individual paid task requests and credits 5% of eligible paid task credit spent. It is not a reward for every SDK invocation or every created task in a local log. Free tasks, refunded credit, and the developer’s own requests do not generate revenue.
Eligible revenue events
A submission counter cannot establish earnings by itself. The actual charge can depend on task family, recognition groups, account rates, and selected modes. Reversals can change the net amount later.
Keep the attribution boundary explicit
A developer tag belongs on each creation request, as a header or body field. If both are provided, they must match. A default tag in SDK construction is a request-building convenience; it does not attach permanently to the customer’s API key.
The customer’s credential still authorizes work. A tag identifies revenue attribution and cannot substitute for authentication. Review a redacted constructed request to establish whether the tag reached the intended creation boundary.
Reconcile three different totals
| Total | Meaning to review |
|---|---|
| Earned | Net eligible attributed revenue |
| Credited to balance | Revenue already settled into service credit |
| Pending | Earned amount not yet settled |
Daily settlement happens after midnight UTC. A delayed observation, refund, or reversal can make a local estimate differ from the authoritative account totals.
Use a small evidence-driven trial
For an illustrative $20 of eligible paid spend, 5% is $1. The example assumes eligibility and net spend are already established; it is not a forecast that twenty dollars of submitted work always generates that amount.
Record task identifiers and redacted attribution evidence where needed. Keep pending earnings separate from a cash payout: withdrawals require approval through a Billing support ticket, and opening that ticket does not transfer funds.
The affiliate guide is the product rule source. Program comparison separates deposits from spend, while developer-tag integration documents the exact request boundary rather than an estimate derived from an unqualified job count.
Frequently asked questions
How much does the easycaptcha developer program pay?
It attributes 5% of eligible credit spent by tagged requests. Free, refunded, and the developer's own requests do not earn revenue.
How do I add my developer tag to a request?
Send x-developer-tag as a request header or developer_tag in the request body using the documented developer identifier.
How do I activate an easycaptcha affiliate program?
Activate the referral or developer program in your dashboard. Eligible earnings are credited daily as balance; payout requests require approval through a support ticket.