Super Agent sells credits to Agent using cash
Super Agent receives cash (or another offline payment method) from an Agent, then issues credits to that Agent's CDN wallet.
Basic flow:
Super Agent collects payment → record full details → issue credits to Agent → save reconciliation ledger
Who does what
| Role | Action |
|---|---|
| Super Agent | Create credit sale transaction, enter payment details, confirm status |
| Agent | Pays per agreement; receives credits in wallet |
| System | Debits Super Agent credits, credits Agent, calculates amount due, writes ledger, stores audit |
Required information when selling
When Super Agent sells credits to an Agent, the form must include all items below before submit.
1. Counterparty & quantity
| Field | Required | Description |
|---|---|---|
| Agent | ✅ | Agent receiving credits (select from Super Agent's agent list) |
| Credits sold | ✅ | Credits issued to Agent CDN wallet (positive number, > 0) |
| Cost rate | ✅ (display) | Agent (buyer) cost rate at time of sale — used to calculate amount due |
| Amount due | ✅ (auto-calculated) | Credits sold × Cost rate — Super Agent confirms before saving |
2. Payment & receipt method
| Field | Required | Description |
|---|---|---|
| Actual amount received | ✅ | Amount Super Agent actually received (USD). Default = amount due |
| Receipt method | ✅ | How Agent paid — e.g. Cash, Bank transfer, Check, Other |
| Payment received at | ✅ | When Super Agent confirmed payment received (default = now; editable if entered late) |
| Currency | ✅ | Default USD |
3. Status
| Status | Meaning | When to use |
|---|---|---|
| Paid in full — credits issued | Full payment received, credits in Agent wallet | Standard flow: collect payment before issuing credits |
| Pending payment — credits issued | Credits issued but payment not yet received / not fully received | Only with temporary credit policy — requires separate approval |
| Partially paid | Partial payment received | Record Amount received + Remaining |
| Cancelled | Transaction cancelled, no credits issued (or credits reversed) | Wrong entry, refund, etc. |
Default recommendation: Safest flow is to allow submit only when status = Paid in full — credits issued. Other statuses are optional if receivables management is needed later.
4. Reference (optional)
| Field | Required | Description |
|---|---|---|
| External reference | Recommended | Internal receipt number, transfer reference, payment voucher number |
| Note | Recommended | Short additional description (if needed) |
Recommended additions
| Field | Reason |
|---|---|
| Performed by (Super Agent) | Audit — who created the transaction (from session) |
| Linked credit transaction | Reference to Super Agent debit / Agent credit ledger entry after issuance |
Business rules
- Cost rate is snapshotted for Agent (buyer) at time of sale — not updated if Agent changes rate later.
- Amount due =
Credits sold × Cost rateof the Agent buyer. - Super Agent must have sufficient credits in CDN wallet before issuing to Agent.
- Issuing credits does not change Agent's online USD wallet — this records cash / offline payment collected by Super Agent.
- Any status or amount change after creation must have an audit log (who, when, from value → to value).
Example
Agent Agent-Beta under Super Agent SA-Alpha, Agent cost rate 15% (0.15).
| Item | Value |
|---|---|
| Credits sold | 5,000 credits |
| Amount due | 5,000 × 0.15 = $750 |
| Receipt method | Cash |
| Actual amount received | $750 |
| Status | Paid in full — credits issued |
| External reference | PT-SA-2026-0088 |
| Note | June 2026 transaction |
After submit: Agent CDN wallet +5,000 credits; Super Agent CDN wallet −5,000 credits; cash settlement ledger records Super Agent received $750 from Agent-Beta.
Related
- Previous flow: Admin → Super Agent
- Next flow: Agent → Shop