The term, without the legal padding
Merchant of record surfaces late in most partnership conversations, usually when somebody in legal reads a checkout page and asks whose name is on it. It belongs at the front of the discussion instead, because it settles far more than the artwork.
The merchant of record is the legal seller of a transaction. It is the entity that charges the card, the name the traveler reads on a statement four weeks later, and the party that owes the money back when an order goes wrong. The card networks require that name to be visible, which is why the question has exactly one answer per transaction and no room for a diplomatic split.
Four things attach to whoever holds that role:
None of that is branding. It is the difference between selling the visa and pointing the traveler at somebody who does.
Three models, three sellers
Our three commercial models run on the same machinery underneath. The destination catalogue, the government portals and the status data coming back are identical across all of them. What changes between them is who the traveler buys from, and the rest of the differences fall out of that one decision.
On revenue share we are the merchant of record. Our name appears at checkout and on the statement, and we carry the refunds, the chargebacks and the traveler support that comes with it. The partner carries a route and an email address, and takes a share of the $39 service fee on volume terms. Starting costs nothing, which is the entire point of the model.
On Desk the agency is the merchant of record. It buys at wholesale, $29 per application, falling to $24 between 100 and 500 a month and $19 above that, then sets whatever retail price its market supports and charges the traveler itself. The margin is the spread. The customer stays at the counter, and so does the refund.
On the Platform licence the partner is the merchant of record on its own payment gateway. Full white label, with our name absent from the flow and the money settling into the partner's own account on its own cycle. It runs at a $5,000 monthly minimum drawn down against $12 per application, and the API behind it is documented on the developers page. Every rate above, and the add-ons that sit alongside them, is published on the pricing page.
Consular fees are passed through at cost in all three. Whoever is merchant of record collects the government charge and remits it unchanged. Our margin sits on the service fee, where a partner can see it and check it.
The logo question
The objection we hear most on the free model is why our name cannot come off the checkout. The answer is that card networks require the merchant of record to be named, and on that model the merchant of record is us. No plan removes a card-network rule; becoming the merchant does. We are not holding the white label back to sell it to you later.
The corollary is the part worth acting on. If you want your own name everywhere the traveler looks, be the merchant. That is what Desk and the Platform licence are, and the step up in price is buying the obligations listed at the top of this piece. The artwork simply travels with them.
Where the money questions land
Every visa order eventually produces one of four messages: where is my visa, why was it refused, can I change the date, where is my refund. The first three follow the application. The last one follows the statement, and travelers do not write to the party that did the work. They write to the name their banking app shows them.
On revenue share that is us, and our support team answers it. On Desk it is the agency counter. On Platform it is the partner's own service desk, and the partner's own team defending the dispute with the submission evidence we hand over.
Choosing a commercial model is choosing which inbox "where is my refund" arrives in.
Finance teams usually arrive at the same fork from the settlement side. On revenue share the traveler's money lands with us and we pay the partner's share out on a cycle. On the other two it lands in the partner's own gateway and we invoice for the wholesale or per-application rate. Which of those a controller would rather reconcile is a legitimate reason to pick a model, and in practice it decides a fair number of them.
How to choose
Decide who the traveler should think they bought from. If the answer is your brand, you are choosing between Desk and Platform before any other question gets asked. If you are indifferent, revenue share is free and live the same day.
Price the refund risk honestly. A refused application has already spent the consular fee at the government, and the traveler will still ask for their money back. Whoever is merchant of record absorbs that conversation, and sometimes absorbs the amount.
Ask finance where the money should land. Settlement into your own gateway on your own cycle points at Desk or Platform. A single monthly payout to reconcile points at revenue share.
Work out how much price control you actually want. Revenue share holds the traveler price at the $39 list fee and shares it. Desk lets you set retail above your wholesale rate. Platform gives you the whole price above $12, once the monthly minimum is covered.
Answered in that order, the four questions usually converge on their own. Most partners who cannot answer the first one confidently start on revenue share for a quarter, because it costs nothing to find out what the real attach rate is on their traffic. The volume then tells you whether the wholesale rates and the obligations are worth taking on, which is a cheaper way to learn it than modelling it in a spreadsheet.
Partners who already know the answer to the first question tend to skip that step and buy the seat outright, and they are usually right to. The only wrong version of this decision is the one made on the assumption that the logo is the thing being priced.