Skip to content Go to main menu

Discover the latest updates from Inspien.

Notice

[INSIGHT] BOK-Wire Int Integration: What Should RFIs and Foreign Financial Institutions Prepare?

관리자 2026-08-19 Number of views 20

Connecting existing payment systems to the Bank of Korea Won International Wire Network through ISO 20022 integration


The Bank of Korea has officially named its new international KRW settlement infrastructure the Bank of Korea Won International Wire Network (BOK-Wire Int) and is targeting September 2026 for pilot operations.

The network is designed to operate 24 hours on Korean business days, from 9:00 a.m. to 9:00 a.m. the following day, excluding weekends and public holidays. This is expected to reduce time-zone constraints and make KRW settlement more accessible to overseas market participants.

For foreign financial institutions, however, the introduction of a new settlement network creates an important technical question:

How can an existing payment infrastructure be connected to the new KRW settlement environment without unnecessarily replacing the existing system?

The answer lies largely in system integration, data mapping, financial message transformation and end-to-end transaction management.



What Is the Bank of Korea Won International Wire Network?

The Bank of Korea Won International Wire Network, commonly referred to as BOK-Wire Int, is a new KRW settlement infrastructure being developed by the Bank of Korea to improve access to won settlement for foreign investors and financial institutions.

BOK-Wire Int should not be confused with BOK-Wire+, the Bank of Korea's existing large-value payment system.

The Bank of Korea's regulatory proposals published in July 2026 describe BOK-Wire Int as a separate settlement infrastructure and provide for real-time gross settlement between participating institutions.

The proposed operational procedures also specify server-to-server connectivity as the primary connection method for participating institutions.

As a result, BOK-Wire Int readiness should be considered not simply as a new payment channel, but as a financial-system integration project involving payment data, messages, interfaces, transaction status and operational processes.



Do RFIs Connect Directly to BOK-Wire Int?

Not necessarily.

A Registered Foreign Institution (RFI) is a foreign financial institution registered with the Korean foreign exchange authorities to participate directly in Korea's domestic FX market.

However, participation in BOK-Wire Int is a separate issue.

Under the regulatory framework proposed by the Bank of Korea, eligibility for direct participation in BOK-Wire Int is linked to institutions that meet the relevant Bank of Korea and BOK-Wire participation requirements.

Therefore, an overseas financial institution should not assume that every RFI will connect directly to the Bank of Korea.

Depending on the institution's participation model, the operational flow may look broadly like this:


Foreign Financial Institution / RFI Payment System→ Participating or Agent Bank→ BOK-Wire Int→ Receiving Participant→ Final Payment Processing


The exact architecture will depend on the institution, its participating bank or agent, account structure, settlement model and applicable Bank of Korea requirements.

This makes integration design one of the most important parts of BOK-Wire Int preparation.



Why ISO 20022 Matters for KRW Payment Integration

ISO 20022 is an international standard for financial messaging used across payments, securities, foreign exchange, trade finance and other financial services.

The Bank of Korea completed the adoption of ISO 20022 for the core fund-transfer services of BOK-Wire+ in May 2026, including major payment and settlement functions.

ISO 20022 enables richer and more structured financial data to be exchanged between systems and improves interoperability and straight-through processing.

But an important distinction must be made:

Using the same messaging standard does not automatically make two financial systems interoperable.

Every financial institution may have a different:

  • · payment platform
  • · internal data model
  • · field structure
  • · code system
  • · interface architecture
  • · transaction workflow
  • · status management process

Therefore, existing payment data must be analyzed and mapped to the required financial message structure before it can be exchanged reliably with a new settlement environment.

A typical integration flow is:


Existing Payment System→ Data Mapping→ ISO 20022 Message Generation & Transformation→ Message Validation→ Message Transmission→ Processing Result Integration
→ Status & Error Management


INSPIEN’s Approach to BOK-Wire Int Integration

INSPIEN approaches BOK-Wire Int readiness as an integration-layer project rather than a replacement of existing payment infrastructure.

For financial institutions, the integration scope may include existing-system analysis, ISO 20022 data mapping, message generation and transformation, message validation and transmission, processing-result integration, transaction-status management, and error handling.

By connecting these functions through an EAI/EDI-based integration layer, financial institutions can retain their existing payment systems while adapting to new financial messaging and settlement requirements.



ISO 20022 Integration Is More Than Message Conversion

Generating an ISO 20022 message is only one part of the project.

A payment transaction also needs to be tracked from initiation through processing and final result.

A production-grade integration environment may therefore need to manage:


  • · payment instruction generation
  • · data mapping
  • · ISO 20022 message transformation
  • · message validation
  • · message transmission and receipt
  • · transaction acceptance status
  • · settlement and processing results
  • · rejected transactions and error reasons
  • · unanswered or timed-out transactions
  • · transaction status enquiries
  • · integration of results into internal payment systems
  • · message transmission history
  • · monitoring and audit trails

This becomes particularly important when a response is delayed or a network interruption occurs.

Simply retransmitting the same payment instruction can create a risk of duplicate processing. The integration layer must therefore track transaction identifiers and processing states and maintain transaction consistency across retries, enquiries and exception handling.



7 Areas Foreign Financial Institutions Should Review

1. Define the Participation and Settlement Model

Determine how your institution will participate in the BOK-Wire Int-related settlement process.

The architecture will differ depending on whether the institution is a direct participant, works through a participating bank or uses an agent or settlement bank.

2. Analyze Existing Payment Systems

Identify the transaction, customer, account, amount, currency and status data currently managed by your payment infrastructure.

3. Build the Data Mapping Model

Map internal data fields to the applicable ISO 20022 message structure.

The mapping should include mandatory and conditional fields, code values, data formats, lengths and business rules.

4. Implement Message Generation, Transformation and Validation

The integration layer should generate and transform ISO 20022 messages and validate them against the applicable schema and business rules.

Depending on the implementation specification, an ISO 20022 Business Application Header (BAH) may be used with the business message. The final implementation should always follow the latest technical specifications and validation requirements provided for the relevant interface.

5. Manage Transaction Status and Errors

The system should consistently handle transaction states such as received, processed, completed, rejected, failed or unanswered.

6. Establish Monitoring and Audit Trails

Operations teams should be able to monitor message flows and transaction status and trace historical events for incident investigation and audits.

7. Test Normal and Exception Scenarios

Testing should cover not only successful transactions but also missing mandatory data, invalid codes, duplicate submissions, delayed responses, communication failures and transaction recovery.


Existing Payment Systems Do Not Necessarily Need to Be Replaced

Preparing for a new payment network does not automatically require replacing an institution's existing core banking or payment platform.

In many cases, a more practical architecture is to retain existing business systems and implement an integration layer between the current infrastructure and the new payment environment.

For example:

Existing Payment System→ Data Mapping & Transformation→ ISO 20022 Message Integration→ Payment Network Connectivity→ Transaction Status & Error Management

This approach can reduce the amount of change required within existing applications while providing the flexibility needed to support new message standards and interfaces.



How INSPIEN Supports ISO 20022 and Financial EDI Integration

INSPIEN provides EAI and EDI integration capabilities for connecting heterogeneous enterprise and financial systems.

For financial institutions preparing for new KRW settlement environments, INSPIEN can support integration areas such as:


Data Mapping→ ISO 20022 Message Generation & Transformation→ Message Validation→ Message Transmission→ Processing Result Integration→ Transaction Status & Error Management→ Monitoring & Audit Trail


The objective is not simply to generate an ISO 20022 message.

The more important goal is to establish an end-to-end integration flow in which transaction data created by an existing payment system can be transmitted to the required external environment and the resulting status and processing information can be returned accurately to the institution's internal systems.

The final implementation scope should be determined based on each financial institution's participation model, system architecture, business requirements and the latest technical specifications applicable to BOK-Wire Int connectivity.

If your organization is evaluating BOK-Wire Int connectivity, ISO 20022 integration, financial EDI, data mapping or payment-system integration, contact INSPIEN to discuss your integration requirements.



Frequently Asked Questions

What is BOK-Wire Int?

BOK-Wire Int is the Bank of Korea Won International Wire Network, a new KRW settlement infrastructure designed to improve access to won settlement for overseas market participants.

Is BOK-Wire Int the same as BOK-Wire+?

No. BOK-Wire+ is the Bank of Korea's existing large-value payment system. BOK-Wire Int is a separate international KRW settlement infrastructure.

Does every RFI connect directly to BOK-Wire Int?

No. The actual connectivity model depends on the institution's eligibility, participating or agent bank, account structure and settlement arrangement.

Do financial institutions need to replace their existing payment systems?

Not necessarily. Existing payment systems can often be retained while an integration layer handles data mapping, ISO 20022 message transformation, connectivity, processing results and transaction status.

What are the key components of ISO 20022 integration?

Key areas include data mapping, message generation and transformation, validation, message transmission, processing-result integration, transaction status management, error handling, monitoring and audit trails.

How can INSPIEN support BOK-Wire Int-related integration?

INSPIEN can support financial-system integration including data mapping, ISO 20022 message generation and transformation, EAI/EDI connectivity, processing-result integration and transaction status and error management. The final scope depends on the participating institution and applicable technical requirements.

New post
There is no new post.
Old post
There is no old post.