
Ripple Payments Reaches Korea's Jeonbuk Bank
Jeonbuk Bank becomes the first Korean regional bank to deploy Ripple Payments, cutting cross-border settlement from days to seconds for local exporters.
Ripple's Korean expansion took a step down-market on August 18, 2026 — and that is meant as a compliment. Jeonbuk Bank has deployed Ripple Payments for cross-border remittances, making it the first regional bank in South Korea to do so. Regional banks are where the small and mid-sized businesses actually bank, which makes this a more interesting deployment than a headline partnership with a national institution.
- Jeonbuk Bank is the first Korean regional bank to deploy Ripple Payments
- The service targets settlement in seconds to minutes, available 24/7, against multi-day traditional transfers
- Aimed at import-export firms, IT startups, and online content creators
- Ripple's third Korean partnership of 2026, after Kyobo Life Insurance and Kbank in April
Why Regional Banks Are the Harder Sell
Correspondent banking is slow for structural reasons, not technical ones. A payment hops through intermediary banks, each adding a settlement window, and the whole chain stops for weekends and holidays. The cost of that is distributed unevenly: a large multinational negotiates around it, while a small exporter waits and eats the working-capital hit.
That asymmetry is why regional bank deployments matter more than their transaction volume suggests. Fiona Murray, Ripple's Asia Pacific managing director, framed it directly, calling regional banks "vital" to the real economy and describing the deployment as extending near real-time settlement to the businesses those banks serve. The customer profile named — import-export companies, IT startups, content creators — is exactly the cohort that traditional rails serve worst.
How Does This Compare to Ripple's Other Korean Deals?
This is the third Korean partnership Ripple has announced in 2026. In April it worked with Kyobo Life Insurance on tokenized government bond transactions through Ripple Custody, and with Kbank on a proof-of-concept for onchain cross-border transactions.
The progression is worth noting: custody and proofs-of-concept first, a live payments deployment now. That is the normal shape of institutional adoption — the pilot phase is where most integrations quietly stop, so a production deployment at a bank with real corporate clients is the more meaningful data point.
Korea has been an active market for payment rails generally. We covered Circle bringing USDC rails to Korea in July and Solana Pay targeting 330,000 Korean merchants in August. Different technologies, same underlying observation: Korea's payments market is unusually willing to test new infrastructure.
What to Watch
Two things will tell you whether this is durable. First, corridor volume — a deployment that handles a meaningful share of Jeonbuk Bank's cross-border flow is a different signal from one running a small pilot corridor. Neither the corridors nor the timeline have been detailed publicly. Second, whether other Korean regional banks follow, which is the usual pattern once one institution absorbs the integration cost and compliance work.
Worth keeping in perspective: Korea's crypto trading market has cooled, with exchanges Upbit and Bithumb reporting roughly 50% revenue declines in the first half of 2026. Payments infrastructure and trading volume are genuinely different businesses, and this deployment is squarely in the former. More in our crypto coverage, including Ripple's full EU MiCA license.
More Crypto Stories

Kazakhstan Tokenized Notes: What the $22M KASE Sale Shows
Kazakhstan's National Bank sold $22.3M of tokenized notes on KASE at 1.4x demand, side by side with traditional notes. Here's why the dual test matters.

Project Faro: What the Banks' $270M Stablecoin Plan Means
Goldman, Citi and other banks reportedly committed $270M to Project Faro, a U.S. dollar stablecoin targeting 2027. Here's how the bank coalition plan works

Solana 1.0 Explained: What Dropping Mainnet Beta Means
Solana 1.0 retires the mainnet beta label after 6 years and gives Agave and Firedancer one shared protocol version. Here's what changes and what doesn't.
