T+2 in FX means a spot currency trade settles two business days after the trade date. The rate is agreed on day T, and the two currencies change hands on the spot date, also called the value date. CLS, the FX settlement utility, says T+2 remains the convention in the spot market. Exceptions exist, such as USD/CAD at T+1 (Kantox).
That gap is why a payment can carry a rate agreed on Thursday and still not reach the recipient's bank until the following Tuesday. This post defines the terms, shows which pairs break the rule, works through weekends and holidays, and ends with how a payout rail changes the clock. The route a payment takes across borders is covered in what a stablecoin corridor is.
What do trade date, spot date, and value date mean?
The trade date (T) is the day two parties agree the rate. The value date is the day the money actually moves. Kantox, a treasury software vendor, defines a spot trade as "an agreement to deliver some amount of one currency for another currency in two business days" (Kantox glossary). Its glossary entry for the value date calls it the date "at which the trade is settled and one currency is exchanged against another".
Terms in a spot trade, with a trade agreed on a Monday
Term | Meaning | Date in the example |
Trade date (T) | Rate agreed, deal confirmed | Monday |
T+1 | One business day after the trade | Tuesday |
Spot date (T+2) | Both currencies are exchanged | Wednesday |
Value date | The settlement date of any FX deal, which equals the spot date for a spot trade | Wednesday |
Forward date | Any agreed value date beyond spot | Later, by contract |
Kantox adds that when the value date is more than 48 hours from the trade, the deal is a forward. So "spot" does not mean "now". It means "on the standard settlement date".
Why spot FX is still T+2
An FX trade has two legs, and each one is paid through a different country's payment system, in that country's banking hours. The convention gives both sides time to confirm the deal and fund the payments.
CLS describes the direction of travel: settlement periods "shortened over time to T+2 (and now T+1)", but "T+2 remains the convention in the spot market" (CLS on T+1 settlement). The "now T+1" part is about securities. The US and Canadian securities markets moved to T+1 in May 2024, and the FX leg for a foreign investor buying a US security had to follow. CLS found that only about 1% of its average daily settlement value of USD 6.6 trillion (as of May 2024) was tied to that kind of trade.
The BIS Triennial Survey put spot turnover at USD 3 trillion a day in April 2025, 31% of the USD 9.6 trillion traded across all FX instruments (BIS). Reference rates carry the convention too: Banco de México says its FIX rate is an average of wholesale quotes "to be settled on the second banking day" after it is determined (Banxico). A treasury team that books the peso at the FIX is booking a T+2 price.
Which currency pairs settle on T+1 instead?
Most pairs settle on T+2, and a short list does not. Kantox names one: it says the Canadian dollar, traded against the US dollar, settles in one business day. Other pair conventions are set by the market and by each dealer, not by one rulebook, so this post does not list them from a secondary source.
Value-date conventions confirmed by the sources read for this post
Pair or currency | Convention | Source |
Most pairs | T+2 | CLS, Kantox |
USD/CAD | T+1 | Kantox glossary |
Mexican peso, FIX reference rate | Settles on the second banking day | Banxico |
For BRL, COP and any pair not in the table, the value date comes from the dealer. Ask for the value date of the exact pair and amount, in writing, before the trade. A Lumx quote works differently: it carries an expiry, not a value date, as the product section below shows. Our guide to how long a payment quote lasts covers the quote side.
How weekends and holidays move the value date
A value date has to be a business day in both currencies, and weekends and holidays are not counted. That is why "two days" often means four calendar days or more.
Standard spot dates with no holidays in either country
Trade day | T+1 | Spot date (T+2) | Calendar days |
Monday | Tuesday | Wednesday | 2 |
Wednesday | Thursday | Friday | 2 |
Thursday | Friday | Monday | 4 |
Friday | Monday | Tuesday | 4 |
A pair on T+1 behaves differently: a USD/CAD trade on Friday settles on Monday. Now add a holiday. A treasury team buys reais against dollars on a Thursday, and the next Monday is a banking holiday in one of the two countries.
One holiday in the middle of the count (illustrative)
Day | Status | Count |
Thursday | Trade date | T |
Friday | Business day | T+1 |
Saturday and Sunday | Weekend | Not counted |
Monday | Holiday | Not counted |
Tuesday | Business day | T+2, the value date |
The rate was agreed on Thursday and the money moves on Tuesday: five calendar days for a "two-day" settlement. If the dollars left the paying account on Thursday, they spend that time in transit.
Each rail follows its own calendar, which is where a payout differs from a trade. Per the Lumx cut-off times page, Pix (Brazil's instant payment system, run by the Central Bank) and Faster Payments (the UK's real-time bank transfer network) have no holiday calendar and run 24/7/365. SPEI (Mexico's interbank transfer system, run by Banxico) is instant and listed as 24/7/365, and the same page lists the Banxico non-business-day calendar for its holidays. ACH, FEDWIRE (the Federal Reserve's same-day wire system) and the USD international wire follow US federal holidays. A request sent after the cut-off or on a holiday waits for the next business day. Our post on payout cut-offs by rail has the full table.
What can go wrong between the trade date and the value date
The main risk is settlement risk: you pay your leg and the counterparty does not pay theirs. CLS exists for this. It says it settles over USD 8.0 trillion of payments a day in 18 of the most actively traded currencies, settling both legs of a trade at the same time. Where a trade does not go through a mechanism like that, each side waits for the other's payment, and the exposure lasts as long as the gap. A long weekend lengthens it.
There is also a funding cost: money committed on T and delivered on T+2 or later cannot be used elsewhere. The cost of holding that float is worked through in pre-funding cross-border payouts.
The rate carries a third risk. Between the quote on screen and the value date, the market keeps moving, which is why a bank asks for the deal to be confirmed on the spot. A locked quote on Lumx limits that exposure to the quote window: 30 seconds, 1 minute or 5 minutes, chosen when the quote is requested.
How BRL, MXN and COP fit the T+2 calendar
A spot trade in a Latin American currency ends in a bank account in that country, so the local calendar matters on the delivery side. The Mexican FIX is the one peso convention confirmed above. The real and the peso for Colombia are different, because offshore markets trade both through contracts settled in dollars, with no delivery of the currency itself. We explain why in BRL and COP payouts onshore.
For a payout the question is which domestic rail delivers, and when. On Lumx, BRL goes out by Pix, MXN by SPEI, and COP by Bre-B (Colombia's instant payment system) or by ACH Colombia, chosen when the recipient's destination is registered. The Brazil step by step walks through the Pix leg. The cut-offs of each are in the rail table linked above. Rates by pair are on the USDC to BRL, USDC to MXN and USDC to COP pages.
The three dates to record on every cross-border payment
I would record three dates on every cross-border payment: the day the rate was agreed, the day the money left the paying account, and the day the recipient's bank showed it. The gap between the first and the last is the number to compare across providers, because a headline rate hides it. A payment that looks cheaper on the rate screen can cost more once the days in transit are priced as float, and a finance team only sees that if all three dates sit in the same row.
When a T+2 comparison is the wrong frame
The comparison between spot FX and a stablecoin payout fits one case: a business converting between two currencies and sending the result abroad. It is the wrong frame in a few others:
A domestic payment in one currency has no FX leg, so there is no spot date to compare.
A payment due in three months wants a rate fixed for that date. That is a forward, which comes from a bank or an FX broker. A quote that lasts five minutes cannot stand in for it. The trade-offs are in live quote vs forward contract.
When the recipient's bank closes for the day, the rail decides the arrival time whatever the FX leg did.
What the calendar looks like on a Lumx payout
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
A payout starts with a rate. The API returns either a floating rate, priced at execution, or a locked rate with an exchangeRateId and an expiry. Locked durations are 30 seconds, 1 minute and 5 minutes: the 30-second lock carries no fee, and longer ones include a fee for the volatility risk. The id goes on the off-ramp request, which converts USDC from the customer's custodial wallet into local currency at the quoted rate. If the lock expires first, the transaction fails with EXCHANGE_RATE_EXPIRED and the application requests a new rate, which comes with a new exchangeRateId. The clock starts when the rate is created, and the response gives the expiry in UTC. The locked rate is honored if the transaction is submitted before the lock expires, and a transaction held in an RFI (request for information, a hold that asks for a document before a transaction clears) still settles at the quoted rate after the lock lapses, because the fiat leg was already converted at the agreed rate. What remains is the clock of the rail that delivers.
Rail clocks on Lumx payouts (Lumx cut-off times page, read on November 1, 2026)
Currency | Rail | Cut-off | Settlement target |
BRL | Pix | None | Instant, 24/7/365 |
MXN | SPEI | None | Instant, 24/7/365 |
COP | Bre-B | None | Instant, like Pix |
COP | ACH Colombia | None published | None published |
GBP | Faster Payments | None | Instant, up to GBP 1 million per payment |
USD | FEDWIRE | 3:00 PM ET | Same business day, typically within hours |
USD | ACH | 2:00 PM ET | 1 to 2 business days |
USD | SWIFT | 3:00 PM ET | 1 to 5 business days, subject to intermediary bank hours |
The docs call these processing targets, not commitments: delivery depends on banking partners and the receiving institution, and an RFI can pause a transaction. The weekend effect is also not the same everywhere. The USD SWIFT row follows the 3:00 PM ET cut-off and the US federal holiday calendar, while Pix has no holiday calendar and SPEI follows the Banxico non-business-day calendar. Funding the wallet is its own step with its own rail clock, so a payout funded by a USD wire starts later than one funded by Pix. The conversion step is in the off-ramp explainer, and stablecoins against SWIFT compares the clocks. The corridors are on global payments, and the Coverage page lists which rails are live per currency.
Methodology and sources
Checked on November 1, 2026: CLS on T+1 settlement for the T+2 convention and the May 2024 impact figure, and the CLS Settlement page for the 18 currencies and USD 8.0 trillion a day. The Kantox spot trade and Kantox value date glossary entries gave the definitions and the USD/CAD exception. The BIS Triennial Survey page gave the April 2025 turnover, and Banco de México gave the FIX footnote. Product behavior comes from Exchange Rates, payment rail cut-off times and Coverage.
Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.
Cover photo: Patrick Robert Doyle on Unsplash.
What is T+2 in FX?
T+2 means a spot FX trade settles two business days after the trade date. The rate is agreed on day T, and the two currencies change hands on the spot date, also called the value date. CLS says T+2 remains the convention in the spot market. A Lumx payout has no spot date: the rate is fixed by the quote, and what follows is the clock of the delivering rail.
Which currency pairs settle on T+1?
USD/CAD is the standard exception, per Kantox. Other pair conventions are set by the market and each dealer, so confirm the pair with your bank in writing. Lumx quotes carry an expiry of 30 seconds, 1 minute or 5 minutes instead of a value date.
What happens to T+2 when there is a holiday?
The value date moves forward until it falls on a business day in both currencies. A trade on Thursday before a Monday holiday in one of the two countries settles on Tuesday, five calendar days later. On Lumx, Pix has no holiday calendar, SPEI is instant and follows the Banxico non-business-day calendar, and ACH, FEDWIRE and the USD international wire follow US business days and cut-offs of 2:00 PM or 3:00 PM ET.
Does T+2 apply to BRL, MXN and COP payouts?
Banxico says its MXN FIX rate settles on the second banking day. For BRL and COP, and for any other pair, the value date comes from the dealer, so ask in writing. A payout is different, because the last leg is a domestic transfer on its own clock. On Lumx that is Pix for BRL, SPEI for MXN, and Bre-B or ACH Colombia for COP, chosen when the recipient is registered.
How does a stablecoin payout compare with a T+2 trade?
A locked rate is honored if the transaction is submitted before the lock expires, and the delivery then follows the rail: instant per the docs on Pix and SPEI, same day on FEDWIRE, and one to five business days on the USD international wire. On Lumx the off-ramp converts USDC from the customer's custodial wallet at the quoted rate, and the delivery times are processing targets, not commitments.
