Transfer operations
Record inbound and outbound instructions with standardized references and controlled status changes.
Clear control for cross-border payment operations.
Coordinate international transfer records, SWIFT GPI status visibility, receiving account requests, reconciliation, and settlement workflows for configured global banking corridors from one secure workspace.
Access is restricted to approved organizations and authorized users.
Example workflow
UETR · 9e6f…4a21
In transit
- Created09:21 SGT
- Received by bank09:27 SGT
- Sent via SWIFT09:30 SGT
- In transit09:34 SGT
- Beneficiary bankPending
- CreditedPending
Illustrative workflow. Actual events depend on connected institutions.
One workspace. Every operational handoff.
Bring transfer records, status events, account instructions, review decisions, and settlement evidence into a consistent operational flow.
GPI status visibility
Follow UETR-linked progress and operational events supplied by your connected institution or integration.
Receiving accounts
Request approved receiving instructions and keep assigned account details visible to authorized users.
Compliance controls
Separate review responsibilities, document decisions, and maintain an auditable activity trail.
Reconciliation & settlement
Match movements, review balances, and coordinate settlement requests from one workspace.
UETR · 9e6f…4a21
In transitOverviewEventsPartiesDocuments
- Direction
- Outbound
- Value date
- May 15, 2026
- Amount
- USD 125,000.00
- Reference
- INV-2026-0157
- Latest event
- Connected institution
SWIFT network fundamentals
Global reach starts with precise financial messaging.
SWIFT is a secure messaging network used by banks, financial institutions, market infrastructures, and corporates to exchange standardized financial instructions. It does not hold customer funds or operate bank accounts. Onecloudpay organizes authorized operational records around that institutional workflow; it does not provide direct SWIFT membership or universal bank access.
- 11,500+
- institutions connected to SWIFT
- 200+
- countries and territories represented
- 40,000+
- possible payment routes across the network
Standardized instructions
Structured MT and ISO 20022 messages help institutions exchange consistent payment data. ISO 20022 is the global standard for richer, structured cross-border payment information.
BIC and routing context
Business Identifier Codes help identify institutions and branches. A valid BIC identifies a party; it does not by itself prove an active route, account relationship, or transfer eligibility.
UETR and GPI visibility
A UETR is the unique end-to-end reference carried with a SWIFT payment instruction. GPI visibility depends on status data supplied by participating institutions and approved integrations.
Controls remain institution-specific
Screening, sanctions checks, account validation, fees, foreign exchange, settlement, and final crediting remain subject to each institution, corridor, currency, and jurisdiction.
Network figures describe SWIFT’s own reach—not Onecloudpay’s direct coverage. Sources: SWIFT network overview, UETR guidance, and ISO 20022 overview.
Illustrative operational view
See the payment journey, not just the endpoint.
Follow authorized payment records from instruction through reconciliation when status events are supplied by participating institutions or approved integrations.
Example workflow
Six operational checkpoints
Status event received
- Instruction recordedReference created
- Review completedControls documented
- Institution acceptedRecord updated
- Message sentUETR retained
- Beneficiary bankEvent dependent
- ReconciledEvidence preserved
04 / 06
Message sent
UETR retained with the payment instruction for operational follow-up.
Example workflow—not live network data. Actual events, routing, and completion times vary by institution, corridor, and integration.
From instruction to evidence—without losing context.
- 1
Create or receive
Capture the payment instruction and required references.
- 2
Review and route
Apply role-based operational and compliance checks.
- 3
Track and reconcile
Follow status events and match financial records.
- 4
Report and settle
Preserve evidence for reporting and settlement review.
Operational clarity is part of security.
Sensitive payment workflows need clear ownership, controlled access, and evidence that can be reviewed.
Role-based access
Users see and act on the workflows permitted for their organization and role.
Traceable decisions
Status changes, reviews, and administrative actions retain operational context.
Protected access
Verified accounts, session controls, two-factor authentication, and passkeys support safer sign-in.
Human oversight
Human judgment where automation stops.
Cross-border operations still require accountable people to review exceptions, validate supporting evidence, and coordinate with the institutions responsible for processing and final credit.
- 01
Review exceptions
Bring incomplete references, mismatched records, and delayed updates into a consistent review queue.
- 02
Record decisions
Preserve the reason, actor, and supporting context behind authorized operational changes.
- 03
Coordinate resolution
Keep internal teams and approved external institutions aligned around the same payment reference.
Onecloudpay supports operational coordination; it does not replace bank, network, legal, or compliance decisions.
Connected workflows across global banking networks.
Support operational teams coordinating cross-border activity with banks and financial institutions around the world through approved banking-partner and integration channels, including corridors across Laos, Thailand, Vietnam, Cambodia, Singapore, Malaysia, and wider international markets.
Availability, currencies, and processing timelines depend on your organization, banking partners, and compliance requirements.
Connected operational context
Operational context that travels with the payment.
A clearer record helps authorized teams understand what was instructed, what changed, and what evidence remains available for follow-up.
- 01
Reference
Keep UETR, institutional references, parties, and value details together.
- 02
Event
Add institution-supplied status updates and authorized review actions.
- 03
Evidence
Retain documents and reconciliation context for operational follow-up.
Payment network context
One controlled workspace for every approved channel.
Onecloudpay gives authorized teams a single operational view for configured cross-border workflows. Each external network remains separate and requires its own commercial approval, technical connection, compliance controls, and production credentials.
SWIFTOperational records available
Manage BIC- and UETR-linked records, status events, documents, approvals, and reconciliation when information is supplied by a connected institution or approved integration.
MoneyGramPartner connector required
MoneyGram operates a separate global money-transfer network and partner API. No live MoneyGram connector is enabled in this deployment; production use requires an approved MoneyGram partnership and completed integration.
Official MoneyGram developer informationWestern UnionAuthorization required
Western Union operates a separate global remittance network. No live Western Union connector is enabled in this deployment; any future use requires written authorization, a supported commercial program, and technical implementation.
Official Western Union network informationIndependent platform disclosure: Onecloudpay is not SWIFT, MoneyGram, Western Union, a bank, or a money-transfer operator. Brand names are used only to identify separate networks and do not imply partnership, certification, endorsement, or live connectivity.
Connected financial ecosystem
Our Partners
Working together to make global financial services more connected, transparent, and accessible. Our partner ecosystem brings together specialised API providers and technology enablers across payments, compliance, messaging, and ISO 20022.
View the Swift Developer Portal partner catalogue33Partner organisations
3Specialised API providers
30Swift API enablers
03 organisations
Providers
Specialised APIs designed for the global financial community.
30 organisations
Enablers
Technology organisations supporting easier access to Swift APIs through embedded applications and integration services.
Official Swift resources
Partner programmes and directories
Explore the official directories maintained by Swift for compatible solutions, certified specialists, service providers, assessors, and ISO 20022 readiness.
01
Compatible Applications
Applications designated by Swift against programme criteria focused on interoperability with relevant Swift services.
Open official directory
02
Compatible Interfaces
Interfaces developed by partners and customers and assessed against Swift interoperability and security requirements.
Open official directory
03
Certified Specialists
Specialists tested against programme criteria that evolve with Swift services, products, and market practices.
Open official directory
04
Platform Partners
Organisations participating in Swift platform programmes that support third-party services and customer experiences.
Open official directory
05
Business Solutions Providers
Providers offering Swift connectivity embedded in business solutions through supported connectivity models.
Open official directory
06
Service Bureaus
Providers of indirect or shared Swift connectivity operating under the Shared Infrastructure Programme.
Open official directory
07
CSSP Providers
Cyber-security service providers supporting implementation of applicable Customer Security Programme controls.
Open official directory
08
CSP Certified Assessors
Eligible organisations employing certified assessors for Customer Security Programme assessments.
Open official directory
09
Business Partners
Swift-appointed organisations providing commercial support to selected customer groups in specific markets.
Open official directory
10
ISO 20022 Ready
Providers that have shared their commitment to support the CBPR+ message collection alongside equivalent MTs.
Open official directory
Partner catalogue reference. Partner names are aligned with the Swift Developer Portal catalogue. Programme status, available services, and technical coverage can vary by solution, market, contract, and implementation. All trademarks remain the property of their respective owners.
Answers before you sign in.
Clear explanations for teams evaluating the platform and its operating boundaries.
What is the Onecloudpay SWIFT Operations Platform?
It coordinates cross-border payment operations—including transfer records, GPI status visibility, receiving account requests, reconciliation, compliance review, and settlement workflows—for authorized organizations.
Who can access the platform?
Access is limited to authorized users from approved organizations. Each user receives permissions based on their organization and assigned operational role.
Can users track a SWIFT transfer?
Authorized users can follow UETR-linked status events and related operational records when updates are supplied by a connected institution or integration.
How does the platform support global banking connectivity?
Onecloudpay coordinates records for configured cross-border workflows through approved banking-partner and integration channels. Coverage depends on each organization, corridor, currency, institution, and compliance requirement; the platform does not guarantee access to every bank.
Does Onecloudpay connect directly to every bank worldwide?
No. Onecloudpay provides one controlled operational workspace for configured institutions and corridors. Direct network access, correspondent relationships, account availability, and transfer execution depend on participating banks and approved integrations.
Are MoneyGram and Western Union transfers live in Onecloudpay?
No live MoneyGram or Western Union connector is enabled in this deployment. They are separate remittance networks, and production use requires provider authorization, a commercial agreement, compliance approval, credentials, and a completed technical integration.
Does Onecloudpay replace a bank or the SWIFT network?
No. Onecloudpay is operations software. It does not replace a bank, the SWIFT network, or the official records and confirmations supplied by participating financial institutions.
How are receiving accounts assigned?
A merchant team submits a request. An authorized platform administrator reviews it and, when approved, assigns the account number, SWIFT or BIC code, country, and operating instructions.
Is an API available?
Yes. Approved integrations can use the Onecloudpay API for supported transfer, GPI event, BIC, balance, withdrawal, and webhook workflows. Authentication and scopes are required.