Singapore Gulf Bank Taps J.P. Morgan for 24/7 USD Clearing Access
The post Singapore Gulf Bank Taps J.P. Morgan for 24/7 USD Clearing Access appeared first on Coinpedia Fintech News
Singapore Gulf Bank (SGB), a fully licensed digital bank regulated by the Central Bank of Bahrain, has taken a major step in expanding its global payment capabilities by opening a correspondent banking account with J.P. Morgan. The move grants SGB direct access to J.P. Morgan’s established USD clearing network, strengthening its ability to deliver fast, secure, and reliable cross-border payment services to clients worldwide.
Based in Manama, SGB says the partnership is designed to support businesses and investors that rely on seamless international money flows, particularly across major financial corridors linking the Middle East, Asia, and global markets.
Rolling Out Wire 365 for Always-On USD Clearing
A key highlight of the collaboration is SGB’s adoption of J.P. Morgan Payments’ Wire 365 solution, making it one of the first digital banks in the MENA region to do so. Wire 365 enables USD clearing 365 days a year, removing traditional banking cut-off times and allowing near real-time settlement even on weekends and public holidays.
With this capability, SGB can now receive and credit incoming USD payments without interruption. This significantly enhances service availability and offers clients greater flexibility to manage liquidity, optimize cash flows, and meet payment obligations without being constrained by standard banking hours.
Strengthening Omnichannel Settlement Capabilities
The new correspondent banking relationship complements SGB’s existing network of global payment systems, including its proprietary real-time settlement infrastructure, SGB Net. By combining traditional global payment rails with its advanced digital infrastructure, SGB aims to provide more comprehensive omnichannel settlement solutions.
- Also Read :
- Grayscale Releases 36-Altcoin Watchlist for Q1 2026
- ,
According to the bank, this integrated approach allows clients to manage global liquidity more efficiently while benefiting from improved speed, certainty, and security in cross-border transactions.
Supporting Cross-Border Capital Flows
The partnership is particularly relevant as capital flows between the Gulf Cooperation Council (GCC) region and Asia continue to expand. Improved USD clearing capabilities can help facilitate investment flows, trade financing, and treasury operations for corporates and institutions operating across these regions.
Backed by Global Financial Strength
J.P. Morgan Payments processes more than $10 trillion in payments daily across over 160 countries and 120 currencies, bringing deep scale and reliability to the partnership. SGB, meanwhile, offers banking, digital asset management, and stablecoin settlement services, backed by Whampoa Group and Bahrain’s sovereign wealth fund, Mumtalakat. Together, the collaboration signals a push toward more continuous, always-on cross-border banking infrastructure.
Never Miss a Beat in the Crypto World!
Stay ahead with breaking news, expert analysis, and real-time updates on the latest trends in Bitcoin, altcoins, DeFi, NFTs, and more.
Subscribe to News
FAQs
Yes. Always-on clearing reduces delays caused by weekends or regional banking hours, which is especially useful for firms operating across the GCC, Asia, and the U.S. This can lower operational friction in treasury and trade workflows.
The impact is mainly indirect. While the setup targets corporates and institutions, improved backend settlement can lead to smoother international transfers and better service reliability for end users over time.
It raises the bar for infrastructure expectations. Other digital and regional banks may face pressure to secure similar correspondent relationships or always-on clearing capabilities to stay competitive.
The focus typically shifts to onboarding clients, optimizing compliance and risk processes, and scaling transaction volumes. Over time, this may enable new payment products or expanded treasury services built on continuous settlement.
Potrebbe anche piacerti
Tether Backs Ark Labs’ $5.2 Million Bet on Bitcoin’s Stablecoin Revival
MySQL Single Leader Replication with Node.js and Docker
command: --server-id=1 --log-bin=ON The --server-id option gives each MySQL server in your replication setup its own name tag. Each one has to be unique and without it, replication won’t work at all. Another cool option not included here is binlog_format=ROW. This tells MySQL how to keep track of changes before passing them along to the replicas. By default, MySQL already uses row-based replication, but you can explicitly set it to ROW to be sure or switch it to STATEMENT if you’d rather log the actual SQL statements instead of row-by-row changes. \ Run our containers on docker Now, in the terminal, we can run the following command to spin up our database containers: docker-compose up -d \ Setting Up Our Master (Primary) Server To configure our master server, we would have to first access the running instance on docker using the following command docker exec -it mysql-master bash This command opens an interactive Bash shell inside the running Docker container named mysql-master, allowing us to run commands directly inside that container. \ Now that we’re inside the container, we can access the MySQL server and start running commands. type: mysql -uroot -p This will log you into MySQL as the root user. You’ll be prompted to enter the password you set in your docker-compose.yml file. \ Next, we need to create a special user that our replicas will use to connect to the master server and pull data. Inside the MySQL prompt, run the following commands: \ CREATE USER 'repl_user'@'%' IDENTIFIED BY 'replication_pass'; GRANT REPLICATION SLAVE ON . TO 'repl_user'@'%'; FLUSH PRIVILEGES; Here’s what’s happening: CREATE USER makes a new MySQL user called repl_user with the password replication_pass. GRANT REPLICATION SLAVE gives this user permission to act as a replication client. FLUSH PRIVILEGES tells MySQL to reload the user permissions so they take effect immediately. \ Time to Configure the Replica (Secondary) Servers a. First, let’s access the replica containers the same way we did with the master. Run this command in your terminal for each of the replica containers: \ docker exec -it <replica_container_name> bash mysql -uroot -p <replica_container_name> should be replace with the name of the replica container you are trying to setup b. Now it’s time to tell our replica where to get its data from. While inside the replica’s MySQL shell, run the following command to configure replication using the master’s details: CHANGE REPLICATION SOURCE TO SOURCE_HOST='mysql-master', SOURCE_USER='repl_user', SOURCE_PASSWORD='replication_pass', GET_SOURCE_PUBLIC_KEY=1; With the replication settings in place, let’s fire up the replica and get it syncing with the master. Still inside the MySQL shell on the replica, run: START REPLICA; This starts the replication process. To make sure everything is working, check the replica’s status with:
SHOW REPLICA STATUS\G; Look for Replica_IO_Running and Replica_SQL_Running — if both say Yes, congratulations! 🎉 Your replica is now successfully connected to the master and replicating data in real time.
Testing Our Replication Setup from the Node.js App Now that our replication is successfully set up, we can configure our Node.js server to observe the real-time effect of data being replicated from the master server to the replica server whenever we write to it. We start by installing the following dependencies:
npm i express mysql2 sequelize \ Now create a folder called src in the root directory and add the following files inside that folder connection.js, index.js and model.js. Our current directory should look like this We can now set up our connections to our master and replica server in the connection.js file as shown below
const Sequelize = require("sequelize"); const sequelize = new Sequelize({ dialect: "mysql", replication: { write: { host: "127.0.0.1", username: "root", password: "master", database: "replicaDb", }, read: [ { host: "127.0.0.1", username: "root", password: "slave", database: "replicaDb", port: 3307 }, { host: "127.0.0.1", username: "root", password: "slave", database: "replicaDb", port: 3308 }, { host: "127.0.0.1", username: "root", password: "slave", database: "replicaDb", port: 3309 }, ], }, }); async function connectdb() { try { await sequelize.authenticate(); } catch (error) { console.error("❌ unable to connect to the follower database", error); } } connectdb(); module.exports = { sequelize, }; \ We can now create a User table in the model.js file
const {DataTypes} = require("sequelize"); const { sequelize } = require("./connection"); const User = sequelize.define("User", { name: { type: DataTypes.STRING, allowNull: false, }, email: { type: DataTypes.STRING, unique: true, allowNull: false, }, }); module.exports = User \ and finally in our index.js file we can start our server and listen for connections on port 3000. from the code sample below, all inserts or updates will be routed by sequelize to the master server. while all read queries will be routed to the read replicas.
const express = require("express"); const { sequelize } = require("./connection"); const User = require("./model"); const app = express(); app.use(express.json()); async function main() { await sequelize.sync({ alter: true }); app.get("/", (req, res) => { res.status(200).json({ message: "first step to setting server up", }); }); app.post("/user", async (req, res) => { const { email, name } = req.body; let newUser = await User.build({ name, email, }); // This INSERT will go to the write (master) connection newUser = newUser.save({ returning: false }); res.status(201).json({ message: "User successfully created", }); }); app.get("/user", async (req, res) => { // This SELECT query will go to one of the read replicas const users = await User.findAll(); res.status(200).json(users); }); app.listen(3000, () => { console.log("server has connected"); }); } main(); When you make a POST request to the /users endpoint, take a moment to check both the master and replica servers to observe how data is replicated in real time. Right now, we are relying on Sequelize to automatically route requests, which works for development but isn’t robust enough for a production environment. In particular, if the master node goes down, Sequelize cannot automatically redirect requests to a newly elected leader. In the next part of this series, we’ll explore strategies to handle these challenges
