Payment infrastructure for affiliate teams is less about the cards themselves and more about the people around them. Who may ask for a new card, who issues it, who sees the balance, who closes the card when an account dies — when these questions have no fixed answers, a team of five buyers ends up with dozens of forgotten cards, mixed budgets and no clear picture of what each offer really costs.
What the infrastructure consists of — cards, BIN, funding, control and security — is covered in Financial Infrastructure for Media Buying: What a Team Needs to Scale. This article is about the processes on top of it: roles, access, the lifecycle of a card and how spend is split by offer and GEO.
Contents
- Roles in an Affiliate Team’s Payment Process
- The Card Lifecycle: Who Issues and Who Closes
- Payment Infrastructure for Affiliate Teams: Splitting by IBAN
- Accounting by Offer and GEO
- When a Buyer Joins or Leaves
- What the Setup Costs: An Example
- When Processes Outgrow Manual Work
- Summary
Roles in an Affiliate Team’s Payment Process
Even a small team benefits from naming who does what with money. Titles vary, but the functions are the same:
| Role | Responsibility in payments | Access |
|---|---|---|
| Owner or finance | Tops up the balance, approves monthly budgets, reconciles spend | Full access to the dashboard with 2FA |
| Team lead | Approves requests for new cards, assigns budgets by offer and GEO | Sees the register and the reports; card issue goes through finance |
| Media buyer | Requests a card for each new ad account, reports spend | Receives card details for their accounts only |
| Technical specialist | Prepares ad accounts and profiles, links cards | Card details for the accounts being set up |
The principle is simple: the fewer people with access to the dashboard, the safer the balance. Buyers do not need to see the balance or other people’s cards; they need a working card for their account within minutes. The dashboard is protected with 2FA, so access cannot be passed around with just a password.
The Card Lifecycle: Who Issues and Who Closes
- Request. The buyer asks for a card for a specific ad account and names the offer, GEO and platform.
- Issue. The person with dashboard access issues the card; it takes about 60 seconds.
- Register. The card’s last four digits go into the team register with the account, buyer, offer and GEO.
- Link. The buyer or technical specialist enters the number, expiry date and CVV in the ad account’s billing section.
- Review. Once a week, finance compares the transaction history with spend in the accounts.
- Close. When an account is abandoned or banned, the final charge is paid and the card is closed in one click; closing is instant.
The step most teams skip is the last one. A card that stays open after its account dies keeps costing maintenance and remains a possible point of leakage. The rule “the account is gone — the card is closed the same day” saves more money than any negotiation over rates.
Payment Infrastructure for Affiliate Teams: Splitting by IBAN
One client can have up to 5 IBANs at the start, with up to 100 cards per IBAN; the IBAN limit may be reviewed as turnover grows. That gives a natural way to separate money flows inside a team:
- one IBAN per sub-team or team lead, if buyers work in groups;
- one IBAN per traffic source, if Meta, Google and TikTok are run by different people;
- a separate IBAN for tests, so experimental offers do not mix with proven ones.
Pick one principle and keep it. A structure that changes every month is harder to reconcile than no structure at all. How many cards a team typically needs is discussed in How Many Virtual Cards Does Your Agency Really Need?.
Accounting by Offer and GEO
Affiliate teams are paid by offer, so spend has to be counted by offer as well. With one card per ad account and a register that ties each card to an offer and GEO, the transaction history becomes a ready source for the report: match each line to the register by the card’s last four digits, sum by offer and compare with the network’s payouts. The detailed method for doing this across dozens of campaigns is in How Affiliate Teams Track Ad Spend Across 10, 50, or 100+ Campaigns; here it is enough to fix three register fields that every card must have — offer, GEO and buyer.
When a Buyer Joins or Leaves
A new buyer gets cards only through the request process, never someone else’s card “for now”. When a buyer leaves, finance closes all cards registered to them on the same day, after the final charges on their accounts have gone through. Accounts that the team keeps are moved to new cards issued for the person who takes them over. This takes minutes and removes the risk of a former team member’s card details being used later.
What the Setup Costs: An Example
Take a team of 4 buyers with 120 active cards in total and €60,000 in monthly top-ups. 120 cards exceed the 100-card limit of one IBAN, so the team uses two IBANs.
- Mid plan: issuance 120 × €1.5 = €180 once; maintenance 120 × €1.5 = €180 a month; commission 2.5% of €60,000 = €1,500 a month; total €1,860 in the first month and €1,680 after that.
- VIP plan: issuance 120 × €1.0 = €120; maintenance €120 a month; commission 1.7% of €60,000 = €1,020; total €1,260 in the first month and €1,140 after that.
The difference of €540 a month comes almost entirely from the commission. Transactions and withdrawals are 0% on all plans, and maintenance is charged only for active cards, which is another reason to close dead cards on time.
When Processes Outgrow Manual Work
At a few hundred cards, issuing and closing by hand becomes a job in itself. VIP clients get an API for bulk issuance, balance and status checks and card management, plus a personal manager. The API lets a team connect card issuance to its own request system, so a buyer’s request turns into a card without someone copying details by hand. Terms are discussed individually on the VIP cards page.
Summary
Payment infrastructure for affiliate teams works when every card has an owner and a short life story: requested, issued, registered, linked, reviewed and closed. Keep dashboard access narrow and protected with 2FA, split money flows by IBAN on one clear principle, tie every card to an offer and GEO, and close cards the day an account or a buyer is gone. The structure of one card per account that all of this relies on is described in One Card per Campaign: How to Structure Payments for Ad Accounts; cards for each platform are on our Facebook Ads and Google Ads pages.