Payment Flow Setup (2026): Banking, Invoicing, Who Holds What

⚠️ Last verified: 2026-04-20 · Volatility: MEDIUM. Processor and banking policies shift.

Money from OF → model → agency → you. How that flows determines legal, tax, and dispute risk. This guide is the architecture.

1. OF payout TOS requirement

OF requires

• Payouts to model's own account.
• Model owns OF account.
• Agency can't directly receive.

Implication

• Model gets money first.
• Agency paid by model.

---

2. Four common payment flow structures

Structure A: Model fully owns

• OF → Skrill (model's) → Model's bank.
• Model pays agency via invoice/transfer.
• Most legally clean.

Structure B: Joint account (risky)

• OF → Skrill (joint) → shared bank.
• Both access.
• Legal complexity.

Structure C: Agency-controlled (out of scope)

• OF → Skrill (agency's Skrill).
• Uses model's identity.
• TOS violation + legal risk.

Structure D: Split payout

• OF allows multiple payout splits in some configs.
• Each party receives directly.
• Cleanest where supported.

---

3. Structure A: Model fully owns

Flow

1. OF pays model via Skrill/Cosmo/bank.
2. Model receives funds in her account.
3. Agency invoices model for services.
4. Model pays agency.

Pros

• Legally clean (both sides own their accounts).
• Transparent.
• Tax-reportable on both sides.

Cons

• Requires trust (model could stop paying).
• Model must actively pay agency monthly.
• Cash flow timing (agency waits for model).

Protection

• Written contract.
• Missed payment = termination clause.
• Track payments via invoice system.

---

4. Structure B: Joint account

Flow

• Shared account, both access.
• OF deposits there.

Complications

• Who legally owns funds?
• Divorce / partnership dispute complexity.
• Some banks don't allow.

Generally avoid

• Too many edge cases.
• Structure A cleaner.

---

5. Structure C: Agency-controlled (out of scope)

What community sometimes does

• Skrill account in model's name.
• Agency operates credentials.

Legal issues

• Not model's actual control of funds.
• Identity misuse.
• Bank fraud exposure.
• OF TOS violation.

Out of scope for this library

• Won't cover operational how-to.

---

6. Structure D: Split payout (where supported)

OF / Cosmo / some processors

• Allow splitting payout at source.
• Agency gets % directly.
• Model gets % directly.

Pros

• Both receive directly.
• No middleman trust issue.
• Transparent accounting.

Cons

• Not all processors support.
• Requires setup.

Preferred where available

• Cleanest structure.

---

7. Invoice flow (Structure A)

Weekly invoice

• Agency sends invoice to model.
• Specifies services delivered.
• Amount owed.

Payment

• Model pays via Wise, Zelle, crypto, whatever.
• Weekly or bi-weekly.

Tracking

• Agency invoicing system.
• Pro tools: QuickBooks, Wave.
• DIY: Google Sheet.

---

8. Agency invoicing best practices

Frequency

• Weekly standard.
• Bi-weekly max.

Amount

• Clear calculation.
• Revenue × agreed %.

Documentation

• What services.
• What period.
• Payment due date.

Chase missed

• 3 days late: reminder.
• 7 days late: urgent follow-up.
• 14 days late: termination warning.

---

9. Crypto payments between model and agency

USDT-TRC20 popular

• Fast.
• Low fees.
• Cross-border.

Tax implications

• Both parties report.
• Document each transaction.

When it fits

• International model / agency.
• No mainstream banking options.

See Crypto Plan.

---

10. Trust issues both directions

Agency fears

• Model keeps all funds.
• Stops paying.
• Disappears.

Model fears

• Agency over-charges.
• Hides revenue.
• Controls her money.

Mitigation

• Transparent accounting (shared dashboard access).
• Clear contract.
• Fast payment cycles (weekly).
• OF dashboard shared with model (she sees all revenue).

---

11. The legal ownership question

OF account = model owns

• No question.

Revenue = who collects first, owes second

• Model collects.
• Owes agency per contract.

Model's bank = model owns

• Agency has no legal claim to her bank.

Implications

• Agency contracts are commercial, not legal ownership.
• Enforcement limited if model leaves.

---

12. OF dashboard sharing with model

Transparency essential

• Model sees all revenue.
• Sees all chats (or her message volume).
• Access to her own earnings.

Agency access

• Operates under her credentials.
• She can revoke anytime.

Communication

• Weekly revenue summary.
• Monthly review call.

Builds trust

• Prevents "you're stealing" accusations.
• Enables real conversations.

---

13. Payment processor choice

For model's receiving

• Skrill, most-used.
• Cosmo, newer, cleaner.
• Paxum, established.
• Direct bank, depends on country.

See Crypto Plan, OF income.

For model paying agency

• Wise Business, international.
• Zelle, US-domestic.
• Crypto (USDT-TRC20), cross-border cheap.

---

14. Regional considerations

US model + US agency

• ACH or Zelle.
• Simple.

US model + non-US agency

• Wise.
• Or crypto.

Non-US model + US agency

• Crypto via Skrill/Cosmo.
• Or international wire.

Emerging markets

• Crypto often only option.

---

15. Common payment flow mistakes

No invoice system

Lost track.

Agency-controlled Skrill (Structure C)

Legal risk.

Monthly vs weekly

Cash flow friction.

Crypto without tax tracking

Audit risk.

No contract for payment terms

Disputes.

---

16. Frequently asked questions

Who controls OF account?

Model per TOS.

Should agency have bank access to model?

No. Structure A cleanest.

Can I use joint Skrill?

Legal complexity. Avoid.

Weekly or monthly?

Weekly.

What if model stops paying?

Termination clause + legal options + replace.

---

Related guides

• Guide 1, Compensation Models
• Guide 4, Preventing Disputes
• Tax/LLC, Model Payments
• Crypto Plan

---

This is general information. Consult qualified professional.

Built from a corpus of real operator discussions across 11 OFM Telegram communities (2024-2026). Usernames anonymized.