Partner Fee Configuration

Overview

You set your own fees from the Wirex admin panel, under Configuration → Fees.

Everything you configure is an addend: your margin, added on top of the platform price. You do not edit the platform's numbers, and nothing you enter reduces them.

charged fee  =  platform base × (1 − customer discount)  +  your addend

The two halves stay apart on purpose. The left half is Wirex revenue and Wirex discounts. The right half is yours, recorded separately on every calculation, so paying you out never requires reverse-engineering a total.

Two screens apply your margin, and a third assigns it per user:

---

Which Fees Apply to a Transaction

Exactly one fee set prices a transaction. Wirex walks this order and stops at the first match. Two sets never merge.

Attribution: A fee scope carries your company id inside its name, so any fee priced through it is attributed to you. Company Fees carries no owner in its key — those addends are attributed to you only when your account is registered as a BaaS-class client. Confirm your client class with your Account Manager before relying on Company Fees for revenue.

---

Access

Your admin account is scoped to your own company. Platform-wide screens are hidden, and Wirex re-checks the scope on every request — the menu is convenience, not the boundary.

Two roles govern what you can do:

A page that loads but returns a permission error on Save means the account holds Editor and needs Admin.

---

Choosing Your Approach

Most partners use both: standard margin on Company Fees so every new customer is priced from day one, then a scope per exception, bound only to the customers who need it.

Important: A bound user takes the scope's numbers instead of the company numbers, not in addition to them. Transaction types the scope leaves blank fall through to the platform default. Build exception scopes as complete price lists.

---

Create a Fee Scope

A scope is an empty price list until you fill it in. Creating one changes no pricing.

Step 1: Open Fee Scopes

Go to Configuration → Fees → Fee Scopes. Your company is pre-selected. If you administer more than one, pick it from the Company field.

Step 2: Create the scope

Press New. Owner is fixed to your company and read-only — a scope is only ever created under the company you administer.

Name rules: lowercase letters, digits, dot, dash or underscore. Start with a letter or digit. 31 characters maximum. The dialog shows the Full id as you type.

The description is what appears in the scope picker afterwards. Tier 2 corporates, 25bps beats new.

Step 3: Record the full id

The full id is your company id (32 characters, no dashes), a dot, then your name:

7f3c1ab94e5d42f8b0d61c9e2a5b8d04.vip-corporates

That prefix is how a fee is paid to you rather than absorbed by the platform, which is why the dialog builds it instead of accepting it typed. Step 3 of Bind an Individual User consumes this value — copy it from the line under the scope picker.

Deleting a scope

Delete is refused while a company is assigned to the scope, or a user is still bound to it. Unbind first.

This is deliberate. A scope that disappears while something still names it does not fall back to the default — it fails every transaction for that customer.

---

Enter Your Fees

The same editor serves Fee Scopes and Company Fees. Fees are grouped into tabs by what they are for, and each table inside a tab saves independently.

Bold tab labels mark the areas that already contain rows. Save stays greyed until you change something.

Four editing rules

What you can save

The editor shows five tabs. Three accept a partner's changes.

Retail Plans and the currency and asset grouping tables are hidden on partner screens. They are platform structure and carry no per-company variant.

---

Company-Wide Fees

Same editor, no scope to name. What you set here applies to every user of the company, unless a binding overrides them.

The Currently customized chips and the bold tab labels show which areas you have changed. Everything else is on the platform default.

Important: Reset to default removes every custom fee for the company in one action — all tabs, all tables. There is no undo and no partial reset. To clear one table only, empty its rows and save that block.

---

Bind an Individual User

A binding attaches one end-user wallet address to one fee scope. From then on that user is priced entirely by that scope.

Step 1: Copy the full scope id

On Fee Scopes, select the scope. The id is the line under the picker. This is the value Step 3 requires.

Step 2: Enter the user's wallet address

Paste the full address into Subject address. A truncated display value is rejected.

Step 3: Enter the scope id and save

Paste the full scope id into Fee scope and press Save. The field checks the format before sending, then Wirex checks the scope exists. A malformed id and a non-existent one are both rejected.

Step 4: Confirm the binding

The binding appears in the table below with the operator who set it and the time. Saving the same subject again updates the existing binding rather than adding a second one.

Removing a binding returns the user to the normal order: the company's scope, then Company Fees, then the platform default. It never strands them.

---

Fee Fields

Fees by transaction type

Exchange margin by currency pair

Trading margin by asset group

Operation types

---

Currency and Asset Classes

You price by class, not by currency. One row covers every pair that falls into it. The mappings below are platform structure — not editable by you, and not shown on your screens.

Currency classes

USDC, EURC and TGBP are classified as currencies, not as tradeable assets. A USDC to EUR conversion is priced as an exchange on MAJOR_MAJOR. A trading markup never applies to it.

How a pair becomes a Pair Class

Only pairs involving a MAJOR get their own class. Everything else lands on DEFAULT — including MID to EM, EM to EM, PEGGED to MID, and any currency absent from the table above. A single exchange row covering the most traffic is DEFAULT.

Asset classes

Important: A markup row on STABLECOIN earns nothing while no asset is classified into it. List a new asset and a MICRO row prices it, not ALT.

Exchange or trading — one applies, never both

Same-asset transactions skip both. No conversion means no margin to add to.

---

Common Pitfalls

---

Your Responsibilities

• Verify every change after saving. Reopen the screen: the Defines and Currently customized chips and the bold tab labels are read back from Wirex. An area absent from them did not save, whatever the confirmation message said.
• Build exception scopes as complete price lists. A bound user does not inherit your company fees.
• Unbind every user before deleting a scope they are bound to.
• Confirm your client class with your Account Manager before relying on Company Fees for attributed revenue.

---

Limitations

• Corporate Plans and Card Issuance & Delivery are visible in the editor but reject a partner's save. They set what Wirex discounts and what Wirex charges for cards.
• Currency classes, asset classes and retail plan tiers are platform structure. Changing them is a request to Wirex, not a self-service action.
• A transport addend cannot create a transport charge where Wirex absorbs the cost.
• A weekend surcharge addend bills only inside the weekend window.
• Fee scope self-service depends on the scope-ownership release being live in your environment. Until it is, Fee Scopes reports a permission warning, and Company Fees and Subject Bindings are the available screens.

---

Contact