The affiliate program pays partners for customers they bring to Loopa. This is the operator guide: how applications arrive, how terms are set, and how money gets out.
Console: /admin/affiliates.php. Payouts: /admin/affiliate-payouts.php.
How an application arrives
Someone applies at mobieus.io/partners/apply. The form is protected by a human check and a honeypot, and the application does not reach your queue until the applicant clicks the verification link in their email. That is deliberate. It keeps unverified addresses out of the review queue.
Applicants can upload a logo. It is re-encoded on our side before it is stored, so what lands on disk is a clean image regardless of what was uploaded.
Reviewing and approving
The Queue tab lists verified applications. Approving requires terms. There is no default deal.
Start from a tier pre-fills the terms form. Three tiers exist: Standard (10% for 12 months), Creator (15% for 12 months) and Bounty ($2 per paying signup). A tier is a starting point, not a menu: every field stays editable afterwards, and the tier that seeded a term set is recorded so you can answer "why does this partner have these numbers" later.
Approving also creates or links a CRM contact, so a partner is a first-class record rather than an island. If the email already belongs to a different partner, approval stops rather than reassigning the contact.
Approval, rejection and suspension each send the partner a message. Termination does not, because by then that conversation has usually already happened.
Terms you can set
| Field | What it does |
|---|---|
| Rate % | Share of what we collect, after app-store fees |
| Duration | How many months a referred customer keeps earning; blank means for as long as they stay |
| Bounty | A flat amount per paying signup, instead of or alongside a rate |
| Signup cap | Ceiling per period; over-cap signups are still attributed but earn nothing |
| Lifetime cap | An independent total ceiling |
| Cookie days | How long after a click a signup still counts. Program default is 60 |
| Min payout | Balance required before a payout is cut. Default $50 |
Conditional rates override the base rate: per product (matching the billing source) or per volume tier (once a partner passes a number of paying customers). A product rule wins over a volume tier; both win over the base rate. New rules only affect future conversions. Nothing recalculates.
Attribution, and the thing worth understanding
Credit is locked when a customer creates their account, not when they pay. That is what makes app-store purchases attributable weeks later, and it is why the branded signup page exists.
Self-referral is blocked automatically where a partner's own account is linked.
Partners can tag their own links with a channel label, which shows up as a per-channel breakdown on their record.
Getting money out
Commission is held for 30 days before it becomes payable, because refunds happen and clawing money back afterwards is worse for everyone. A refund reverses the commission it earned; if that commission was already paid, the reversal carries forward against the next payout.
Two payout methods:
- Check. The original path. Requires a verified mailing address.
- Direct deposit. The partner sets it up themselves through our payment provider, who verifies their identity and collects their tax form. We never see or store bank details or a tax number.
Payouts run prepare, then approve, then issue, and the approver must be a different person from the preparer. That holds for both methods; automating the mechanism is not a reason to relax who may release money.
A payout cannot be issued until a tax form is on file.
Year-end
The payouts screen has a tax-year view: who was paid what, who crossed the $600 reporting threshold, and whose paperwork is missing. Partners outside the US on a W-8BEN are listed but flagged, because they do not get a 1099-NEC.
Partners can download their own statement for any year from their portal.
The partner portal
Partners sign in at mobieus.io/partners/portal with a one-time emailed link and no password. It is read-only for a reason: a payout destination must never be changeable from a session established by an email link.
They see clicks, signups, conversions, what is on hold and what is due, a 30-day trend, their referral link, a link builder for channel tags, shared creative assets, and their own API keys.
Sub-affiliates
A partner can be recorded as having recruited another, earning an override on what that partner generates. One level only, and no chains. The override is paid by us on top of the recruited partner's commission, never deducted from it. Refunds claw the override back along with the commission it came from.
Creative assets
The Assets tab holds shared images every partner sees in their portal. Retiring an asset hides it from the portal but keeps the file reachable, so a partner who already embedded it does not end up with a broken image in a published post.
Common questions
A partner says their link is not working. Check the code is active and the program is active. An unknown code still renders a signup page rather than an error, so "it loads but I get no credit" usually means a retired code.
A partner sees no commission after a sale. Check the 30-day hold, then check whether the signup was over their cap. Over-cap signups attribute but earn nothing, and that is shown on their record.
A partner wants their earnings in a spreadsheet. They can export a statement themselves from the portal, or use their API key.
The affiliate program pays partners for customers they bring to Loopa. This is the operator guide: how applications arrive, how terms are set, and how money gets out. Console: **/admin/affiliates.php**. Payouts: **/admin/affiliate-payouts.php**. ## How an application arrives Someone applies at mobieus.io/partners/apply. The form is protected by a human check and a honeypot, and the application does **not** reach your queue until the applicant clicks the verification link in their email. That is deliberate. It keeps unverified addresses out of the review queue. Applicants can upload a logo. It is re-encoded on our side before it is stored, so what lands on disk is a clean image regardless of what was uploaded. ## Reviewing and approving The **Queue** tab lists verified applications. Approving requires terms. There is no default deal. **Start from a tier** pre-fills the terms form. Three tiers exist: Standard (10% for 12 months), Creator (15% for 12 months) and Bounty ($2 per paying signup). A tier is a starting point, not a menu: every field stays editable afterwards, and the tier that seeded a term set is recorded so you can answer "why does this partner have these numbers" later. Approving also creates or links a CRM contact, so a partner is a first-class record rather than an island. If the email already belongs to a different partner, approval stops rather than reassigning the contact. Approval, rejection and suspension each send the partner a message. Termination does not, because by then that conversation has usually already happened. ## Terms you can set | Field | What it does | |---|---| | Rate % | Share of what we collect, after app-store fees | | Duration | How many months a referred customer keeps earning; blank means for as long as they stay | | Bounty | A flat amount per paying signup, instead of or alongside a rate | | Signup cap | Ceiling per period; over-cap signups are still attributed but earn nothing | | Lifetime cap | An independent total ceiling | | Cookie days | How long after a click a signup still counts. Program default is 60 | | Min payout | Balance required before a payout is cut. Default $50 | **Conditional rates** override the base rate: per product (matching the billing source) or per volume tier (once a partner passes a number of paying customers). A product rule wins over a volume tier; both win over the base rate. New rules only affect future conversions. Nothing recalculates. ## Attribution, and the thing worth understanding Credit is locked when a customer **creates their account**, not when they pay. That is what makes app-store purchases attributable weeks later, and it is why the branded signup page exists. Self-referral is blocked automatically where a partner's own account is linked. Partners can tag their own links with a channel label, which shows up as a per-channel breakdown on their record. ## Getting money out Commission is held for 30 days before it becomes payable, because refunds happen and clawing money back afterwards is worse for everyone. A refund reverses the commission it earned; if that commission was already paid, the reversal carries forward against the next payout. Two payout methods: * **Check.** The original path. Requires a verified mailing address. * **Direct deposit.** The partner sets it up themselves through our payment provider, who verifies their identity and collects their tax form. We never see or store bank details or a tax number. Payouts run prepare, then approve, then issue, and the approver must be a different person from the preparer. That holds for both methods; automating the mechanism is not a reason to relax who may release money. A payout cannot be issued until a tax form is on file. ## Year-end The payouts screen has a tax-year view: who was paid what, who crossed the $600 reporting threshold, and whose paperwork is missing. Partners outside the US on a W-8BEN are listed but flagged, because they do not get a 1099-NEC. Partners can download their own statement for any year from their portal. ## The partner portal Partners sign in at mobieus.io/partners/portal with a one-time emailed link and no password. It is read-only for a reason: a payout destination must never be changeable from a session established by an email link. They see clicks, signups, conversions, what is on hold and what is due, a 30-day trend, their referral link, a link builder for channel tags, shared creative assets, and their own API keys. ## Sub-affiliates A partner can be recorded as having recruited another, earning an override on what that partner generates. One level only, and no chains. The override is paid by us **on top** of the recruited partner's commission, never deducted from it. Refunds claw the override back along with the commission it came from. ## Creative assets The **Assets** tab holds shared images every partner sees in their portal. Retiring an asset hides it from the portal but keeps the file reachable, so a partner who already embedded it does not end up with a broken image in a published post. ## Common questions **A partner says their link is not working.** Check the code is active and the program is active. An unknown code still renders a signup page rather than an error, so "it loads but I get no credit" usually means a retired code. **A partner sees no commission after a sale.** Check the 30-day hold, then check whether the signup was over their cap. Over-cap signups attribute but earn nothing, and that is shown on their record. **A partner wants their earnings in a spreadsheet.** They can export a statement themselves from the portal, or use their API key.
