Referral Program
ADBNK's referral program lets advertisers and publishers acquire new users via invite codes and earn cash rebates when their invitees make real transactions. This page explains the invitation mechanism, rebate rates and limits, and how settlement and revocation work.
Invitation mechanism
- Every advertiser/publisher account has a unique invite code and can generate a sign-up link carrying it (e.g.
https://adbnk.co/register?invite=AA090481). - Both advertisers and publishers can invite any type of new user (an advertiser can invite advertisers or publishers, and vice versa).
- When a new user registers with an invite code, the system automatically establishes an invitation relationship, binding them as the inviter's "downline".
- Invitation relationships are single-level (inviter → invitee direct rebate); there is no multi-level distribution.
| Type | Invite code prefix | Example |
|---|---|---|
| Advertiser | AA | AA090481 |
| Publisher | PP | PP123456 |
Limits on regenerating an invite code
You can only regenerate an invite code when the current account has no downlines, to avoid disrupting existing invitation relationships.
Rebate triggers
Rebates are triggered by the invitee's transaction behavior, and the transaction must actually land:
| Invitee type | Trigger event | Description |
|---|---|---|
| Advertiser | Successful top-up | After the invited advertiser's top-up lands, the inviter earns a rebate |
| Publisher | Successful withdrawal | After the invited publisher's withdrawal lands, the inviter earns a rebate |
The whole chain is event-driven: a successful top-up/withdrawal fires an event, and the rebate service computes and credits accordingly — executing consistently whether the confirmation comes from an admin's manual review, an automatic payment callback, or a scheduled batch task.
Rebate rates and limits
Rebate rates and all caps are configurable in the admin console (the referral config group):
| Config | Meaning | Default |
|---|---|---|
enabled | Whether the referral program is on | On |
advertiser_rate | Rebate rate for advertiser invites (%) | 5% |
publisher_rate | Rebate rate for publisher invites (%) | 5% |
min_trigger_amount | Minimum trigger amount (below it, no rebate) | 100 |
max_times | Max rebates per invitation relationship (0 = unlimited) | 0 |
max_amount | Cap per single rebate | 1000 |
total_max_amount | Cumulative cap per invitation relationship (0 = unlimited) | 0 |
Values follow the live console config
The table shows design defaults; the platform may adjust them at any time. For the actual rate, cap, and threshold, refer to the current config in your console's "Referral Settings".
Calculation logic
The rebate amount is the trigger amount times the rate, with limits applied step by step:
rebate = trigger amount × rebate rate(%) / 100The computation checks, in order: whether the program is enabled → whether the invitation relationship is valid → whether the trigger amount reaches min_trigger_amount → whether max_times is exceeded → whether total_max_amount is exceeded; then it caps the single rebate with max_amount and applies a second cap using the remaining cumulative allowance. If any condition fails, no rebate is paid this time.
The inviter's rate applies
The rebate rate follows the inviter's role: an advertiser inviter uses advertiser_rate, a publisher inviter uses publisher_rate.
Settlement
- Direct credit to balance: the rebate is added directly to the inviter's account balance (advertiser to advertiser balance, publisher to publisher balance), and a rebate ledger entry is generated (with rebate number, trigger order number, trigger amount, rate, amount, and before/after balance).
- Idempotent: the same top-up/withdrawal is rebated only once; repeated triggers do not double-credit.
- Queryable: advertisers/publishers can view the invitation overview, downline list, and each downline's rebate records and cumulative rebate in their own console.
Revoke
When the triggering top-up/withdrawal is revoked, or an admin manually revokes a rebate, the system deducts the inviter's balance and sets that rebate record's status to REVOKED, keeping the books consistent with real transactions.
Rebates are clawed back with the transaction
Rebates are built on real transactions. If the corresponding top-up/withdrawal is revoked, the paid rebate is clawed back accordingly — don't treat an unconfirmed rebate as locked-in earnings.