BRICS Cross Border Payments Initiative: A Finance Guide
The BRICS payments initiative is a direction for financial cooperation, not proof of a universally available payout network. Here is how finance teams can separate policy ambitions from usable payment capabilities.
The BRICS cross border payments initiative is a cooperation agenda aimed at improving payments between participating economies through stronger correspondent banking relationships, local-currency settlement, and greater interoperability. It should not be treated as a single, universally accessible payment rail, a shared BRICS currency, or a ready-made replacement for every SWIFT-connected bank relationship.
For companies paying vendors, contractors, or sellers internationally, the practical question is narrower: does a specific arrangement improve an eligible payment from your funding account to your recipient’s usable balance? A summit announcement cannot answer that. Participating banks, currency liquidity, regulatory permissions, and beneficiary access can.
What the initiative means—and what remains uncertain
The 2024 Kazan policy agenda encouraged stronger correspondent banking networks and local-currency settlements under the BRICS Cross-Border Payments Initiative, often abbreviated BCBPI. That matters because the agenda includes improving existing banking relationships, not simply replacing them with a new technology.
GIS Reports’ October 2025 analysis describes the initiative’s policy direction and implementation constraints, noting that BRICS Pay remained in planning and early pilot stages as of mid-2025. That is a dated assessment, not evidence that every component remains at the same stage today.
Reporting available through October 7, 2026 describes continued interest in connecting payment systems and central bank digital currencies. However, deployment claims vary, and the evidence does not establish universal corporate access across BRICS markets. Finance teams should distinguish a policy commitment, a technical demonstration, a restricted pilot, and a commercially available service.
BCBPI, BRICS Pay, and mBridge are not interchangeable
- BCBPI: the broader policy initiative covering cross-border payment cooperation and local-currency settlement.
- BRICS Pay: a named payment project discussed within the broader BRICS ecosystem. Its branding alone does not establish which banks, currencies, or business payment types are accessible.
- mBridge: a separate multi-central-bank digital currency project relevant to the discussion of alternative settlement architectures. It is not another name for BCBPI.
- A common currency or gold-backed token: a different proposition from connecting existing national payment systems. Neither is a prerequisite for local-currency payments.
The Lowy Institute’s analysis of BRICS Pay provides context on its ambitions and obstacles as a potential challenge to SWIFT. For operators, the important distinction is between an intended alternative and a service their bank can actually execute.
How the payment mechanisms could affect your business
Local-currency settlement changes FX exposure—not necessarily cost
A supplier invoice can be settled in a local currency without creating a common BRICS currency. Depending on the arrangement, participating banks may use local-currency accounts and correspondent relationships instead of routing the transaction through a dollar conversion.
Eliminating an intermediate currency conversion can reduce friction. But a less-liquid direct currency pair may have a wider spread, limited quote availability, or more restrictive hedging options. A route without a dollar settlement leg can still use the dollar as a pricing reference.
Compare the total funding debit against the recipient’s net credit for the same invoice, quote time, and payment deadline. Include conversion charges, bank deductions, prefunding costs, and any cost of converting unused balances back into your operating currency.
Payment-system links can shorten one part of the journey
Connecting domestic fast-payment systems could make cross-border initiation and recipient delivery more efficient. But a domestic instant-payment service does not become internationally accessible just because its country participates in BRICS.
The connection still needs rules for eligible users, FX execution, transaction limits, compliance checks, and liability. A link designed for consumer remittances or merchant purchases may not support corporate supplier invoices or bulk contractor payments.
FXC Intelligence’s analysis of the BRICS CBDC-link proposal highlights interoperability and differing national CBDC development stages as important constraints. Treat proposed links as conditional capabilities until the relevant institutions confirm production access.
Messaging and settlement solve different problems
SWIFT primarily provides financial messaging; it is not a currency. Replacing a message channel does not by itself replace the accounts, liquidity, and legal arrangements that move value.
A wholesale CBDC arrangement could change the settlement asset and the way participating institutions exchange it. Payment-versus-payment can reduce FX principal risk by making one currency’s transfer conditional on the other. It does not eliminate liquidity shortages, operational outages, sanctions obligations, or the work required to credit a supplier’s ordinary bank account.
A readiness test for BRICS payment announcements
Classify each announcement before adding it to a treasury roadmap. The following is an operational framework, not a rating of any particular BRICS project.
| Evidence available | What it establishes | Finance team response |
|---|---|---|
| Declaration or proposal | Policy intention | Monitor; do not change payment promises |
| Technical demonstration | A mechanism can be demonstrated | Ask about legal and commercial access |
| Restricted pilot | Defined participants can test it | Verify eligibility and pilot restrictions |
| Contracted production service | A provider offers a specified route | Validate costs, controls, and beneficiary credit |
| Repeatable production evidence | The route works for your payment profile | Consider controlled expansion |
BRICS membership is not a coverage specification. A useful specification identifies the originating legal entity, funding currency, destination country, receiving institution, beneficiary type, payment purpose, and settlement currency. Our guide to evaluating payout platforms by corridor explains why country-level coverage claims are insufficient.
The limitations that matter most to finance teams
Spendable liquidity matters more than currency availability
Receiving or holding a currency is useful only if the business can spend, transfer, convert, or hedge it on acceptable terms. Otherwise, avoiding one conversion may create trapped liquidity and a later conversion problem.
Before accumulating balances, map expected local receipts against local payables and confirm account eligibility, transfer restrictions, and repatriation requirements. Multi-currency accounts can support currency management where available, but an account product does not override local capital controls or establish access to a BRICS-linked arrangement.
Compliance follows the parties and jurisdictions
A non-dollar payment is not automatically outside sanctions restrictions. Applicable obligations depend on the entities, institutions, jurisdictions, and transaction involved—not simply the currency or messaging network.
Have compliance approve the actual route and counterparties. Confirm who screens the transaction, who handles requests for supporting documents, and what happens if an intermediary rejects or freezes the payment. Alternative infrastructure must not become a way to bypass existing controls.
Recipient data does not become uniform
Do not build a single “BRICS beneficiary” onboarding form. Requirements remain country-, bank-, and payment-purpose-specific. Depending on the destination, a provider may require local account identifiers, beneficiary legal names, tax identifiers, purpose codes, invoices, or other supporting documents.
Get the required data schema from the executing provider and validate it before payment release. Preserve invoice references through conversion, settlement, and recipient credit so that faster movement does not produce slower reconciliation.
A practical adoption checklist
- Choose a relevant payment flow. Start with recurring, lawful payments where FX friction or delivery uncertainty is material. Do not migrate an entire international payment run based on an announcement.
- Identify the actual service. Record the provider, participating institutions, scheme rules, production status, and whether your legal entity and payment purpose qualify.
- Document the complete money path. Identify where conversion happens, which accounts require prefunding, and who is responsible for final beneficiary delivery.
- Request an executable quote. Compare the funding debit and guaranteed or estimated net credit with your existing route. Record quote expiry and responsibility for deductions.
- Confirm completion evidence. Distinguish instruction acceptance, interbank settlement, beneficiary-bank receipt, and usable beneficiary funds.
- Test exception handling. Establish procedures for rejected payments, uncertain status, refunds, and returned currency. Avoid fallback resubmission while the original payment may still complete.
- Set an expansion gate. Require acceptable beneficiary outcomes, reconciliation, compliance review, and recovery procedures before increasing volume.
For ongoing oversight, keep an evidence record for each approved route: dated provider confirmation, eligibility restrictions, pricing basis, completion evidence, and fallback owner. This turns a geopolitical development into a controlled operational decision.
Prepare for more options, not a single replacement
The BRICS payments initiative deserves attention because it could expand local-currency settlement and connections between national systems. It does not justify assuming that a common currency, universal network, or frictionless corporate payout service is already available.
The next step is to ask existing banking and payment partners for documented access on your relevant routes. Evaluate Payouts.com’s payout automation against your current execution and reconciliation requirements, while assessing any future BRICS-linked service separately. The objective is not to choose a geopolitical label; it is to deliver compliant, predictable payments with a defensible cost and an auditable outcome.
Created with AI assistance. Sources are linked in the article; this content is general information, not legal, tax, or financial advice.
Discussion
38 commentsRelated resources
How to Evaluate a Mass Payout Platform: Test Corridors, Not Country Counts
Country coverage is not proof that a platform can deliver your payment run. Use a corridor-level acceptance test to evaluate costs, recipient requirements, delivery evidence, and failure handling.
Established Common Standards for Cross-Border Payments
Cross-border payments rely on several standards, not one global rulebook. Learn what each standard governs, where local requirements still apply, and how to turn standards into enforceable payment controls.
Xero Supplier Payment on Account: Record and Allocate Advances
A supplier advance should remain visible until it is allocated or refunded—not disappear into a reconciled bank transaction. Here is how to manage that workflow in Xero, including cross-border payment checks.
Run your entire money cycle on one ledger
Global payouts, AP/AR automation, and AI agents with their own wallets and spend limits.
Get started
The statement that BRICS membership is not a coverage specification is something we learned the hard way. We assumed that because both origin and destination were BRICS countries, certain payment routing options would automatically be available, but the actual bank capabilities varied significantly by corridor and beneficiary bank tier.
We made the same mistake. Turned out one of the banks didn't even have the correspondent relationship activated for commercial payments, only consumer remittances. Now we verify actual capability at the transaction type level before making any routing assumptions.
The readiness test framework would be useful to circulate internally, but the harder question is who at the bank or provider actually has the answers for each classification level. When we've asked about pilot eligibility or production access for new corridors, we usually get routed between three departments and end up with inconsistent information.
We had the same problem and ended up escalating through our relationship manager to get someone from their correspondent banking team on a call. Even then, the answer was basically 'we can explore it' rather than a yes or no. The person who knows is usually not the person answering routine inquiries.
We've found that creating a structured inquiry template helps. We send the same five questions to relationship managers, product teams, and compliance separately, then compare answers. When the answers don't match, that's usually a signal the route isn't ready for production.
The BCBPI vs BRICS Pay vs mBridge clarification should be standard onboarding material for anyone in treasury or AP touching emerging markets. The number of vendor queries we've fielded conflating these three just because they all have 'BRICS' in the name has been ridiculous.
We added a two-page glossary to our treasury ops manual after the fourth time someone asked if BRICS Pay meant we could stop using correspondent banks entirely. The conflation problem is worse when you're trying to explain it to stakeholders who only read headlines.
We built a one-pager with those three definitions and the readiness test table from the article. Cut our internal confusion in half and gave us a script for when banks start pitching vague 'BRICS payment solutions' without specifying which component they're actually talking about.
The point about local-currency settlement changing FX exposure but not necessarily cost is something we learned the hard way. We assumed a direct CNY/INR route would be cheaper than going through USD, but the spread was actually worse and our hedging options disappeared. Now we run the full funding debit vs. net credit comparison the article describes before committing to any new corridor.
Same lesson. We now model the round-trip cost including any balance repatriation before we commit to a new corridor, especially when liquidity is thin on the pair.
Same here. The spread difference caught us off guard on a BRL/RUB corridor. We now include the round-trip conversion cost in every comparison, especially if there's any chance of unused balances sitting in the destination currency.
The part about payment-versus-payment reducing FX principal risk but not eliminating operational outages or sanctions obligations is a distinction that seems obvious once you read it but almost never gets mentioned in the bank pitch decks we see. They always lead with settlement finality and skip the parts that still require manual intervention.
Same problem on our side. The pitch always ends at finality and I've started explicitly asking what happens if their system goes down mid-day or if sanctions get updated between trade and settlement. The answers are usually much less polished.
Same here. The pitch materials focus on settlement mechanics and ignore everything downstream. We had to specifically ask about sanctions screening timing and cutoff windows before we realized the new rail still had the same compliance holds as the existing one.
The distinction between BCBPI, BRICS Pay, and mBridge is genuinely helpful. Our AP team gets vendor questions mixing these up constantly, and having a simple breakdown to reference will save a lot of back-and-forth before we even get to whether a given payment is actually possible.
We built a short internal FAQ using those three definitions and it cut down on the noise significantly. The harder part is keeping it updated when someone reads a headline about a BRICS currency and assumes it changes what we can actually do this quarter.
We started adding that exact section to our payment capability documentation after the third time a procurement lead asked if we could 'just use the BRICS currency.' Having the three-way distinction written down made vendor conversations much shorter.
The conditional capabilities point is spot-on. We've been tracking the mBridge pilots since last year and the gap between what gets announced at summits versus what our banks can actually execute for corporate payables is massive. The readiness test table should be required reading before anyone puts a BRICS route into a quarterly treasury plan.
Same experience here. We've found it useful to actually send the readiness test table to relationship managers when they forward BRICS-related announcements. Saves a week of back and forth trying to figure out if anyone can actually route the payment.
We've started asking banks for the production contract language before we even consider routing volume. If they can't provide beneficiary confirmation timelines and liability for failed credits, it's still a pilot regardless of what they call it.
The messaging versus settlement distinction is something our treasury team struggles to explain to non-finance stakeholders. We had a situation last month where an exec thought switching to a non-SWIFT message format would somehow bypass our FX liquidity constraints, and it took three meetings to walk that back.
We had the exact same problem. One of our regional directors assumed that any alternative to SWIFT automatically meant lower costs and faster settlement. The article's point about settlement assets versus message channels helped me reframe the conversation—now I just ask them to walk through where the actual liquidity sits and who holds the accounts at each step.
The article's breakdown of messaging versus settlement would have saved you those meetings. That table comparing what each announcement type actually establishes is worth printing out for exactly this kind of conversation.
The framework for classifying announcements is the real value here. We wasted two months evaluating what turned out to be a technical demonstration that had no clear path to commercial availability for corporate payments, and this would have stopped that immediately.
We had a similar situation but didn't even realize it was just a demo until our bank couldn't provide a service agreement. The readiness test would have flagged that immediately at the contracted production service row—if there's no contract available, you're not in production territory.
Same lesson here. Now we ask upfront whether the thing being described has a production SLA and a contract template. If the answer is vague, we table it and revisit in six months.
The warning about direct currency pairs having worse spreads than going through USD is something we learned the hard way on an INR/ZAR payment last year. Everyone assumes removing the intermediate leg automatically saves money but liquidity matters more than route simplicity.
We've started modeling both routes now for anything outside the major pairs. Sometimes the synthetic rate through USD is still better even with two conversion legs, especially if you need a hedge instrument that only quotes against the dollar.
We now model both the direct pair and the USD-intermediated route for every payment over a certain threshold. The difference in effective rate can be 200+ basis points depending on the corridor and time of day. Liquidity always wins.
The readiness test framework is exactly what we needed. We've had vendors in Brazil and India ask if we can pay them via BRICS Pay and until now I had no structured way to evaluate whether that was even real. The distinction between a restricted pilot and contracted production service is going to save us from committing to timelines we can't meet.
Completely agree. The framework also helps when you need to explain to procurement why you can't just flip a switch because a vendor saw something in the news. We now require them to provide us with the bank name, service tier, and whether their account can actually receive the payment type before we even start the conversation with our bank.
Same situation here. Our Brazil vendors started mentioning it in Q4 last year and I couldn't get a straight answer from our correspondent bank about whether they support it or if it was even past pilot stage. The framework at least gives me a script for the next conversation with our banking partner.
One thing I wish the article addressed more directly: how do you actually find out if your bank has live access to any of these arrangements? We bank with a tier-1 global institution and their relationship managers still give vague answers when we ask about local-currency settlement options between our UAE entity and suppliers in China. Is there a standard question set that gets past the sales layer?
I don't think the bank knows until you ask about a specific corridor and beneficiary type. We've started requesting test quotes for actual upcoming invoices instead of hypothetical routes—if they can't price it in 48 hours, it's not production-ready regardless of what policy documents say.
The banks probably don't know themselves until they route a test transaction. We've found it's better to ask for a specific payment scenario with actual beneficiary details and invoice amounts rather than asking in the abstract. Even then, the answer changes depending on which ops desk handles it.
The point about less-liquid currency pairs having wider spreads is critical and often overlooked when people get excited about bypassing USD. We tested INR/ZAR settlement last year for a recurring payment and the all-in cost was actually higher than going through dollars, plus the beneficiary bank took three extra days to credit. Eliminating an intermediate currency sounds great until you price the actual execution.
We had the same experience with RUB/CNY earlier this year. The spread was brutal and settlement took longer than our normal correspondent route. Saved nothing on fees and lost on the conversion.
Exactly. We ran into the same issue with BRL/RUB for a supplier arrangement last quarter. The quoted spread was 4x what we pay on a normal USD leg, and that's before factoring in the delay while their treasury confirmed they could actually accept the currency. Ended up reverting to standard routing.