What is SWIFT?
Also: SWIFT gpi
Global bank messaging network used to instruct cross-border wire transfers; slower and more expensive than schemes, but the default for large B2B settlements.
The Society for Worldwide Interbank Financial Telecommunication (SWIFT) operates a secure messaging network facilitating cross-border payments between financial institutions.
When a payment is initiated, the originating bank sends a SWIFT message, typically an MT103 for customer transfers, to the beneficiary’s bank, either directly or via correspondent banks, specifying the payment amount, currency, beneficiary details,
and the unique Bank Identifier Code (BIC) of all involved parties.
This messaging infrastructure, while not directly moving funds itself, authorises the debit and credit entries in the respective banks’ nostro and vostro accounts, often resulting in settlement times ranging from one to five business days depending on the currencies and intermediary banks involved.
For merchants, SWIFT is primarily encountered when receiving large value international business-to-business payments or when making payments to international suppliers that do not accept card scheme payments.
The merchant typically provides their bank account details, including their BIC and International Bank Account Number (IBAN), to the remitting party, who then instructs their bank to send a SWIFT transfer.
A common operational challenge arises from incorrect or incomplete SWIFT message fields, such as an erroneous BIC or beneficiary account number, which can lead to payment delays, rejections, or even misrouted funds, incurring additional investigation and repair fees.
Worked example
A merchant reviews a £10,000 transaction where SWIFT is the deciding factor. Approved transactions are cleared, interchange and scheme fees are calculated, refunds and chargebacks are netted, and the balance is paid to the merchant account.
The operational cost is modelled at 35 basis points, or £35, deducted before payout, and the relevant action must complete T+1 to T+3. Step 1 is to capture the original request data, including amount, currency, issuer country, MID, and response or status code.
Step 2 is to apply the merchant's rule set, for example whether to retry, challenge, refund, release goods, or hold for review. Step 3 is to reconcile the result against acquirer reporting so finance can see the cash impact.
If the rule improves the outcome by even 50 basis points on 2,000 similar monthly transactions, the merchant protects roughly 10 extra orders from avoidable failure or loss.
Scheme notes
Visa and Mastercard both separate authorisation, Clearing, and settlement, but cut-off times, fee billing, currency handling, and reporting formats vary by acquirer and region.
American Express often operates as both scheme and acquirer in its closed-loop model, so statement presentation and funding timing can differ materially.
Domestic bank-transfer rails such as SEPA, Bacs, Faster Payments, Pix, and PayNow use their own settlement cycles and return rules rather than card-scheme Clearing files.
Why it matters for merchants
Commercially, this affects cash flow, Reconciliation effort, FX exposure, reserves, and the predictability of merchant funding. For a merchant processing £500,000 per month, a 25 basis point movement is worth £1,250 before secondary effects such as disputes, reserves, support tickets, or failed delivery costs.
The impact is larger in high-risk, subscription, travel, digital-goods, and cross-border models because issuer decisions and scheme monitoring can compound quickly.
Cardflo can help by combining acquiring access, MID routing, orchestration rules, KYB review, and chargeback tooling where relevant, so the merchant is not dependent on one processor interpretation or one fixed transaction path.
Frequently asked
Which data should a merchant store for SWIFT?
Store the transaction ID, MID, acquirer, amount, currency, issuer country, card scheme, response or status code, timestamp, and any 3DS, exemption, refund, or dispute reference. For card transactions, keep authorisation and Clearing identifiers because settlement or chargeback questions may arrive 30 to 120 days later.
For regulated flows, keep customer consent and evidence records for at least the period required by local law or scheme rules. Good records reduce investigation time from hours to minutes when acquirer reporting does not match the order system.
How often should SWIFT be reviewed?
High-volume merchants should review exception rates weekly and trend the main metric monthly by scheme, acquirer, issuer country, MCC, and payment method. A movement of 20 to 50 basis points can be material if the merchant processes thousands of orders.
Finance should reconcile the cash impact at settlement level, while risk or payment operations should analyse the root cause. Reviewing only blended totals hides problems that appear on a single BIN range, region, or MID.
What threshold usually triggers action on SWIFT?
The threshold depends on the category, but merchants should investigate any sudden change above 10% relative movement or 25 basis points absolute movement. For disputes and fraud, scheme thresholds such as 0.9% under Visa monitoring or 1.5% under Mastercard ECM can create immediate escalation risk.
For settlement or pricing items, even 5 to 15 basis points can justify routing or contract review. The key is to set thresholds before month-end, not after a processor invoice or scheme notice arrives.
Can SWIFT differ between acquirers?
Yes. Acquirers can map response codes differently, apply different risk rules, support different data fields, and settle on different cycles.
One acquirer may return a generic decline while another exposes issuer advice that allows a safe retry. Fee treatment can also vary by contract, especially for cross-border, FX, premium cards, and alternative payment methods.
This is why merchants using orchestration should compare performance by acquirer and scheme rather than relying on a single blended approval or cost figure.
What is the first remediation step when SWIFT creates losses?
Start with a 30-day sample and split it by scheme, issuer country, card product, payment method, MID, and response or dispute code. Quantify the value at risk in cash terms, not just percentage points.
Then decide whether the fix is operational, such as better evidence or customer communication, technical, such as richer data or 3DS indicators, or commercial, such as a different acquirer route.
Recheck the same metric after one full settlement or dispute cycle to confirm the change worked.
See how SWIFT plays out in practice
Industries and regions where this term drives real acquiring, routing, or dispute decisions.
Related terms
A card transaction where the issuer country differs from the acquirer country, attracting higher interchange and scheme fees.
The transfer of funds from the acquirer to the merchant's bank account, net of fees and reserves.
The transfer of settled funds from acquirer to merchant bank account, cadence governed by the funding cycle and any reserve holdbacks.
Related guides.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.