Redemption & Invite Codes
Issuing redemption codes in bulk, invite sign-up links and waitlist management.
This tab is only available to prepaid resellers. If you do not see it, check your account mode with your account manager.
Redemption codes and invite codes solve two different problems:
| Redemption codes | Invite codes | |
|---|---|---|
| Purpose | Distribute credit | Distribute sign-up access |
| How used | Customer enters the code on the wallet page and receives credit | Customer signs up through a link and is attributed to you |
| Single use | Yes | No — you set a number of seats |
Redemption codes
Creating them
Fill in:
| Field | Description |
|---|---|
| Campaign name | An internal label for distinguishing batches, e.g. "Singles' Day", "Partner A first batch" |
| Amount per code | How much credit each code grants on redemption |
| Count | How many codes to generate |
| Credit validity (days, optional) | Empty means the credit never expires; a value makes it a limited-time grant reclaimed at expiry |
After creation you can copy all codes at once for distribution.
Issuing deducts immediately
The full face value is deducted from your wallet the moment you create the codes (amount per code × count). It is not deferred until customers redeem.
Creation fails if the balance is insufficient. Confirm your balance before large campaigns.
Redemption re-checks your balance
This is the easiest trap to fall into: when a customer redeems, the system checks your current wallet balance. If it is insufficient at that moment, redemption fails.
In other words, issuing codes does not guarantee they can be redeemed. If you spend your balance elsewhere after issuing, outstanding codes may stop working and customers will come straight to you.
Practice: keep a healthy buffer in your wallet after issuing codes — never run it down to near zero.
Other rules
- Each code is single use, voided on redemption with the user recorded.
- Codes can be disabled, which invalidates any that are still unredeemed.
- You cannot redeem your own codes from your reseller administrator account. To credit your own account, use quota adjustment.
- Redeemed credit lands in the customer's account balance; if you set a validity period, it becomes a limited-time grant.
Codes versus direct quota adjustment
| Redemption codes | Direct adjustment | |
|---|---|---|
| Best for | Offline sales, promotions, channel distribution | One-to-one crediting after payment |
| Customer experience | Self-service, no action from you | You operate manually |
| Discounted selling | Yes, sell codes at your own rate card | Not applicable |
| Traceability | By campaign batch | By adjustment remark |
Prefer redemption codes when selling at a discount in local currency. How much you collect is your business; what the customer redeems is always the code's face value. The two are decoupled, so you never get "the amount I paid does not match the credit I received" complaints.
Invite codes
An invite code group generates a shared sign-up link; anyone registering through it is attributed to you.
Fields:
| Field | Description |
|---|---|
| Campaign name | Batch label |
| Seats | How many people may register through this link |
| Valid for (days) | Link lifetime, or never expires |
| Public code | Whether to generate a publicly shareable code |
After creation, copy the site link to distribute. You can enable or disable a group at any time.
Typical uses
- Community growth: one link posted to a group, capped at 100 seats;
- Channel partnerships: a separate invite group per partner, so seat consumption shows who drives sign-ups;
- Closed beta: small seat count, short validity.
Waitlist
If you restrict sign-ups, users who want to register without an available seat land on the waitlist. Review it and admit users as you choose.
Useful for controlling growth pace when service capacity is the constraint.