SWIFT Fees, FX, and the True Cost of a Cross-Border Payment

The fee a customer sees on a cross-border payment confirmation is rarely the cost of the payment. It is the visible slice of a stack that includes correspondent deductions, FX margin, and charge-bearer rules, most of which never appear on the confirmation.

Table of contents

• The cost stack
• Charge bearer: OUR, SHA, BEN
• FX margin is usually the biggest line
• gpi fee transparency
• Product moves that compress cost
• Operator notes
• FAQ

The cost stack

A real cross-border payment carries:

1. Originating bank fee. Charged by the sender's bank.
2. Correspondent deductions. Each correspondent in the chain may deduct a fee.
3. Beneficiary bank fee. Charged by the receiving bank, depending on charge-bearer rules.
4. FX margin. The spread between the interbank rate and the rate applied to the customer.
5. Lifting charges and local levies. Country-specific deductions, taxes, or central-bank fees.

The sticker fee from the originating bank is usually the smallest line. The FX margin is usually the largest.

Charge bearer: OUR, SHA, BEN

SWIFT charge-bearer codes determine who pays which fees:

• OUR: Originator pays all fees. Beneficiary receives the full sent amount.
• SHA (shared): Originator pays the sender's fees; beneficiary pays correspondent and beneficiary fees.
• BEN: Beneficiary pays all fees, deducted from the amount.

These are commercial and operational choices, not technical defaults. Picking the wrong one for a use case is a frequent source of customer complaints (e.g., a payroll wire sent SHA with surprise deductions on the employee's end).

FX margin is usually the biggest line

Banks and fintechs typically apply a spread on top of the interbank rate. For consumer cross-border, this spread can be one to three percentage points or more in some corridors. On a $1,000 transfer, that is $10–30, often dwarfing the explicit fee.

The product question is whether the FX margin is bundled (a single "good rate" with the spread hidden) or transparent (interbank rate + explicit FX fee). Regulators in the EU, UK, Australia, and elsewhere are pushing toward transparency. Many emerging-market regulators are following.

gpi fee transparency

SWIFT gpi requires correspondents to report deductions along the chain. The originator's bank can, and should, show the customer the full deduction trail. Most still do not. The platforms that do create a trust advantage that price alone cannot.

Product moves that compress cost

For a fintech routing cross-border:

• Direct correspondent relationships in major corridors remove a hop.
• Local-rail last-mile delivery beats correspondent settlement on cost in many corridors.
• Netting flows between corridors reduces FX volume.
• Transparent FX with a published margin builds trust and supports premium pricing.
• Charge-bearer defaults matched to use case reduce support volume.

Each of these is a product decision that affects cost more than any single contract negotiation.

Operator notes

• The visible fee is the smallest part of the cost.
• FX margin is usually the largest line and the most opaque.
• Charge-bearer rules are product decisions with downstream customer impact.
• gpi gives the originator visibility into deductions, use it.
• The structural cost moves come from routing, netting, and last-mile rail choice.

FAQ

Is "zero fee" cross-border real? Often the fee is moved into the FX margin. The total cost is rarely zero.

Which charge bearer is best? OUR for payroll and supplier payments where the recipient must receive a known amount. SHA for many consumer remittances. BEN is rare and operationally risky.

Does gpi reduce cost? Indirectly, by exposing deductions and creating commercial pressure, not by lowering them directly.