TLDR
- On Sept. 22, 2026, J.P. Morgan Payments selected Thunes to expand cross-border reach through the Xpedite Remit solutions suite, combining J.P. Morgan connectivity to local real-time payment rails with Thunes’ Direct Global Network (J.P. Morgan Payments newsroom; PR Newswire).
- Stated reach: payouts to local bank accounts and mobile wallets across 100+ corridors, with access framed as 12 billion wallets and accounts via Thunes, on real-time, 24/7 networks, from a single account and connectivity.
- Operator surface: instant supplier settlements, bill payments, and remittances, with principal protection, end-to-end traceability, same-currency payouts or FX conversion, in remittance-heavy markets such as India, Mexico, Bangladesh, Brazil, China, Colombia, Indonesia, Kenya, Nigeria, Pakistan, and the Philippines.
- Chase consumer and small-business accounts (stated ~94 million) are also in scope for faster outbound experiences and real-time inbound payments into the U.S.
- This is a bank + network news explainer, not a rewrite of FintechSpecs’ best outbound payment APIs listicle. Ask which corridors are live vs planned, who holds settlement risk, and how FX/traceability show up in the API and ops console.
If you move money to suppliers, wallets, or remittance corridors, Sept. 22, 2026 is a coverage and rail-assembly signal, not another “instant payouts” slogan.
J.P. Morgan Payments said it is working with Thunes to expand Xpedite Remit so clients can send faster payouts to bank accounts and mobile wallets across 100+ corridors, using both J.P. Morgan’s local real-time payment rail connectivity and Thunes’ Direct Global Network (newsroom, Sept. 22, 2026).
FintechSpecs readers should care because this sits on the same operator surface as outbound payment APIs, marketplace payout / split payments, embedded payments for B2B SaaS, and ACH payment APIs. The question is no longer “does the bank talk about real-time?” It is “which corridors are actually live, which local rail is used per country, and who owns principal and FX when a payout fails mid-path?”
What happened
On Sept. 22, 2026, Thunes and J.P. Morgan Payments published matching announcements: a J.P. Morgan Payments newsroom post and a PR Newswire release stating that Thunes was selected to expand cross-border capabilities through the Xpedite Remit solutions suite.
Verified claims from those materials (bank / vendor-stated):
- Product suite: Xpedite Remit, expanded via Thunes for cross-border payouts.
- Assembly model: J.P. Morgan Payments’ connectivity to local real-time payments rails plus Thunes’ Direct Global Network.
- Client benefits named: principal protection, end-to-end traceability, and faster payouts in the same currency or with seamless FX conversion.
- Access claim: local bank accounts and mobile wallets via real-time, 24/7 payment networks from a single account and connectivity.
- Scale claim: access to 12 billion mobile wallets and bank accounts across 100+ corridors via Thunes’ network.
- Initial use cases: instant supplier settlements, bill payments, and remittances.
- Named remittance-heavy markets in the initial rollout framing: India, Mexico, Bangladesh, Brazil, China, Colombia, Indonesia, Kenya, Nigeria, Pakistan, and the Philippines.
- Consumer bank angle: JPMorganChase Consumer and Community Bank / Chase accounts serving approximately 94 million consumer and small business customers; expected faster payout experiences and support for real-time inbound payments into the U.S.
- Broader context in the newsroom post: builds on J.P. Morgan Payments cross-border work including Wire 365 and a recent milestone with Swift’s retail payments scheme; Sibos 2026 (Sept. 28–Oct. 1, Miami) called out as a speaking venue.
Gayathri Vasudev, Global Head of High Value Payments & FX at J.P. Morgan Payments, said: “Our clients want simpler, faster ways to move money across borders and to reach people through the payment methods they prefer. That’s why we are continuing to enhance our cross-border capabilities and further expanding our solution through the collaboration with Thunes. Building on milestones, like our recent progress with Swift’s retail payments scheme, we’re helping clients grow in new markets while delivering the faster, more seamless experiences they have come to expect.”
Peter De Caluwe, Co-Founder and CEO of Thunes, said: “We are thrilled to welcome J.P. Morgan Payments to our Direct Global Network. Thunes offers the bank-grade compliance, security and resilience required to move money safely and quickly at global scale. Together, we are demonstrating how traditional banking infrastructure can connect with popular local payment methods to make global commerce smoother for everyone involved.”
Ashish Ajmera, Head of Banking Payments at Chase, said: “As customers increasingly move money across borders as part of their everyday lives, they expect the experience to be fast, intuitive and reliable. These enhancements mark an important step in our efforts to modernize cross-border payments and expand the capabilities available through our broader suite of products and services, helping customers send money internationally with greater speed, transparency and confidence.”
Flag: The announcements do not publish a corridor-by-corridor go-live matrix, per-market local rail names (UPI, PIX, SPEI, and so on), SLA tables, FX spreads, or API documentation. “100+ corridors” and “12 billion” endpoints are network reach claims until clients see live destination coverage in production.
What Xpedite Remit, Thunes, and local rails actually mean for builders
Xpedite Remit as the bank product surface
Xpedite Remit is framed as a J.P. Morgan Payments solutions suite for faster cross-border payouts. For treasury and fintech operators already on J.P. Morgan, the commercial question is whether Remit becomes the default outbound path versus wires, correspondent chains, or third-party payout APIs you already integrate.
Treat Remit as the bank-packaged product. Treat Thunes as the destination network layer that extends where that product can land without J.P. Morgan building every local connection alone.
Thunes Direct Global Network as destination coverage
Thunes is a cross-border payments network provider. In this deal it supplies the Direct Global Network that J.P. Morgan Payments taps for wallet and account reach. That pattern matters for operators comparing outbound payment APIs: bank-led assembly (sponsor bank + network partner) versus pure API aggregators.
Local real-time rails + single connectivity
Two different ideas appear in the same announcement:
- Local rail connectivity: J.P. Morgan Payments’ existing links into domestic real-time systems.
- Thunes network reach: wallet and account destinations across 100+ corridors on 24/7 rails.
For product managers, “single account and connectivity” is the UX and ops claim. For risk and treasury, you still need to know which entity settles each leg, when principal is protected, and what “traceability” returns when a wallet provider rejects a payout after your cut-off.
Use cases called out for platforms and corporates
The materials list three builder-facing patterns:
- Instant supplier settlements: B2B payouts into local accounts/wallets instead of multi-day correspondent chains.
- Bill payments: payee-directed flows in markets where local methods dominate.
- Remittances: consumer and small-business outbound into high-volume corridors, with Chase as a consumer distribution surface.
Those map to FintechSpecs clusters on outbound APIs, marketplace payouts, and embedded payments. Keep this post as the what shipped layer; use the listicles for vendor shortlists.
How this sits next to FintechSpecs outbound and payout coverage
Do not treat this as a replacement for category comparisons. Use those posts for depth; use this section for placement.
Category listicles (evaluation depth)
- Best outbound payment APIs for B2B SaaS
- Marketplace payout API / split payments
- Embedded payments providers for B2B SaaS
- Best ACH payment APIs for vertical SaaS
- Payment orchestration for SaaS
Practical operator map
| Layer | What Sept. 22 mainly moves | What it does not replace |
|---|---|---|
| Bank product packaging | Xpedite Remit as the named suite for faster cross-border payouts | Your payout product UX, retry logic, and customer messaging |
| Destination coverage narrative | Thunes claim of 100+ corridors and 12B wallets/accounts | Per-corridor live status, wallet KYC rules, and reject codes |
| Rail assembly | J.P. Morgan local RTP links + Thunes Direct Global Network | Correspondent fallbacks when a local rail is down |
| Risk language in launch materials | Principal protection and end-to-end traceability (stated) | Contractual definitions of principal, liability caps, and evidence packets |
| Consumer distribution | Chase ~94M accounts as a potential remittance / inbound surface | Consumer pricing, corridor limits, and fraud controls for retail remits |
Note on the outbound APIs list: Thunes and J.P. Morgan Remit may or may not be shortlisted in your existing vendor matrix. That is a content gap to watch, not a reason to turn this news post into a forced ranking rewrite. If Remit becomes an RFP option, evaluate it with the same corridor coverage, FX transparency, and failure-mode tests you use for outbound API vendors.
Risk, controls, and diligence questions for platforms
Cross-border payouts inherit rail risk, FX risk, and destination compliance risk even when a global bank brands the product.
Controls and promises in launch materials
- Principal protection (stated)
- End-to-end traceability (stated)
- Same-currency or FX conversion paths
- Real-time / 24/7 network framing
- Bank-grade compliance language from Thunes
What operators should still design for
- Coverage vs marketing footprint: “100+ corridors” can mean network eligibility, partner ambitions, or live payout destinations. Require a live corridor matrix (country, destination type bank vs wallet, local rail, cut-off, SLA).
- Principal protection definitions: Ask what “principal protection” covers (send-side debit? mid-path failure? beneficiary credit reversal?) and where liability sits between J.P. Morgan, Thunes, and the local receiving institution.
- Traceability that ops can use: End-to-end sounds good in a press release. You need payment IDs, status codes, and support playbooks that match your console and customer tickets.
- FX and landed amount: “Seamless FX” is not a quote board. Require mid-rate source, spread disclosure, and when the FX rate locks relative to send confirmation.
- Chase consumer path ≠ corporate Remit: The ~94M Chase figure is a distribution signal for retail remittances and inbound U.S. receipts. Do not assume every corporate Remit feature ships to Chase apps on the same day.
- Sibos timing: The newsroom flags Sibos 2026 (Sept. 28–Oct. 1). Treat that as a conference follow-up window for corridor detail, not as confirmation that every named market is production-ready on Sept. 22.
Who should care, and what to ask
Prioritize a deep read if you:
- Run B2B SaaS or marketplaces that pay suppliers, sellers, or field workers across borders
- Own treasury or payments product at a company already banking with J.P. Morgan
- Compare outbound / remittance / wallet payout vendors and need a current bank-network coverage signal
- Build remittance or bill-pay experiences that might ride Chase distribution later
Concrete questions for J.P. Morgan Payments / Thunes / your counsel
- Which corridors are live for new client traffic this quarter vs roadmap only?
- Per corridor, is the destination a bank account, mobile wallet, or both, and which local rail is used?
- What does principal protection contractually cover, and who remediates a failed credit after your send is confirmed?
- What traceability artifacts (IDs, statuses, webhooks) are available in API and ops UI today?
- How is FX quoted, locked, and disclosed for same-day vs delayed payouts?
- How do AML/sanctions screening and beneficiary KYC map across Thunes destinations vs J.P. Morgan’s existing controls?
- For Chase: which remittance corridors and inbound U.S. real-time paths are consumer-live vs “expected to enable”?
- How does Remit sit next to Wire 365 and Swift retail scheme paths in the recommended architecture?
The take: corridor assembly moved; failure modes did not disappear
J.P. Morgan Payments selecting Thunes for Xpedite Remit is a coverage and packaging event. Local RTP connectivity plus a global destination network is how large banks extend “send once, land locally” without owning every last-mile relationship. Chase’s consumer footprint makes the remittance story politically and commercially louder than a pure wholesale wire upgrade.
The operator lesson is sharper: a 100+ corridor claim does not erase per-market rail outages, FX opacity, or beneficiary reject codes. Treat Sept. 22 as permission to expand the shortlist and pressure-test Remit against your outbound API matrix, not as a substitute for corridor-level diligence in FintechSpecs’ outbound payments coverage.
If you are shipping supplier payouts or remittance features, integrate for reach, then instrument for blame. Know which entity can credit in-market, which clock your 24/7 rail actually runs on, and which team owns the ticket when “traceable” still leaves a wallet unpaid.
For category depth after this news, start with best outbound payment APIs for B2B SaaS and marketplace payout / split payments.
FAQ
When did J.P. Morgan Payments and Thunes announce the Xpedite Remit expansion?
Sept. 22, 2026, via the J.P. Morgan Payments newsroom and a matching PR Newswire release.
What is Xpedite Remit?
Xpedite Remit is J.P. Morgan Payments’ solutions suite for faster cross-border payouts. This announcement expands that suite by adding Thunes’ Direct Global Network alongside J.P. Morgan’s local real-time payment rail connectivity.
What is Thunes?
Thunes is a cross-border payments company whose Direct Global Network is used here for destination reach to bank accounts and mobile wallets. More at thunes.com.
How many corridors and endpoints were claimed?
The materials claim 100+ corridors and access to 12 billion mobile wallets and bank accounts via Thunes’ network. Treat those as vendor/network reach figures until you see a live corridor matrix.
Which use cases and markets were named?
Initial rollout framing covers instant supplier settlements, bill payments, and remittances, including India, Mexico, Bangladesh, Brazil, China, Colombia, Indonesia, Kenya, Nigeria, Pakistan, and the Philippines.
Does Chase get this too?
JPMorganChase’s Consumer and Community Bank is in scope. Chase accounts serving about 94 million consumers and small businesses are described as expected to see faster payout experiences and support for real-time inbound payments into the U.S. Confirm consumer go-live separately from corporate Remit.
Does this replace FintechSpecs’ outbound payment API comparisons?
No. Those posts compare payout vendors and architectures. This piece explains what J.P. Morgan Payments and Thunes announced on Sept. 22, 2026, and which diligence questions operators should ask.
How does this relate to Wire 365 or Swift?
The newsroom post positions the Thunes expansion as building on broader cross-border investment, including Wire 365 and progress with Swift’s retail payments scheme. Those are related rails and milestones, not the same product as Remit + Thunes.
