Alchemy Pay Partners with dLocal to Launch Instant Bank Transfers in Argentina
Alchemy Pay is pushing deeper into Latin America after striking a partnership with dLocal (NASDAQ: DLO), and the first visible change will be instant bank transfers in Argentina. The deal plugs Alchemy Pay into dLocal’s local payment rails and USD settlement plumbing, and it’s designed to make buying and selling crypto with pesos feel a lot less like a hassle.
Put simply, instead of waiting for slow cross-border rails or paying steep fees, people in Argentina will be able to move between fiat and crypto faster and in their local currency. That’s the point of the integration: local payment infrastructure on the backend, local currency on the frontend, and fewer ugly surprises for users and merchants.
Alchemy Pay already supports fiat payments in 173 countries with more than 300 payment methods. Adding dLocal’s regional know-how is a logical next step: it gives Alchemy Pay a way to scale compliant on- and off-ramps across Latin America without rebuilding local payment relationships from scratch. dLocal’s “One dLocal” approach, one API, one platform, one contract, means global companies can accept payments and settle funds in emerging markets more easily, and Alchemy Pay gets to lean on that instead of trying to replicate it.
Faster Access to Crypto
This partnership isn’t just about instant transfers in one country. It plugs into a broader Alchemy Pay ecosystem that includes a Web3 Digital Bank for multi-fiat accounts and instant fiat-crypto conversions, an NFT Checkout that lets customers buy NFTs directly with fiat, and a newly launched RWA platform that opens tokenized real-world assets, like U.S. stocks and ETFs, to users who want to invest with local currency. Combine those products with dLocal’s local rails and settlement capabilities, and you get a smoother, more integrated experience for regional users and the merchants who serve them.
For platforms and dApps that already integrate Alchemy Pay, this should make user onboarding cleaner: people who prefer to transact in their own currency won’t have to jump through costly or time-consuming hoops to access digital assets. For Alchemy Pay, it’s another step toward making fiat-crypto flows feel as routine as any other online payment.
Founded in 2017, Alchemy Pay positions itself as that bridge between traditional finance and crypto. Its network token, ACH, runs on Ethereum, but the company’s bigger play is payments, and with dLocal’s reach across APAC, the Middle East, Latin America and Africa, the partnership feels like a practical move to bring modern payment efficiency to markets where crypto adoption is growing fast.
This isn’t an overnight transformation, but it’s a clear push to remove friction where it matters most: locally, in local currency, and with local settlement. For users in Argentina and potentially other Latin American markets down the line, that should mean faster access to crypto and fewer headaches when moving money between fiat and digital assets.
You May Also Like
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
