Payment gateway for online merchants in India, Korea and Latin America
ATLAS is a payment gateway for online merchants: it takes payments from your customers in the methods they use at home, sends pay-outs to their accounts and cards, and settles with you in USDT. One integration covers six markets.
Who ATLAS is for
ATLAS works for online businesses whose customers live in India, South Korea, Argentina, Venezuela, Turkey, or Europe and the UK, and pay from a local bank or wallet app. You create a payment through the API or send the buyer to our pay page. The money arrives through a local method, and your balance grows in USDT. Pay-outs run the other way: you reserve USDT, and the recipient gets local currency.
Because you settle in USDT on TRC-20, you don't need a bank account in every country you sell into. The rate is fixed at the moment of each operation.
Payment providers can work with us from the other side as well. If you run your own processing in one of these markets, you can plug it in as a route and receive a weighted share of merchant traffic, with automatic failover between routes.
Where we process today
Six markets are live for pay-ins and pay-outs. In each one, buyers pay with the methods they already know, and you receive USDT for every completed payment.
| Market | Pay-in | Pay-out | Currency |
|---|---|---|---|
 India | UPI, UPI Intent, IMPS | UPI, IMPS | INR |
 South Korea | Bank transfer, Kakao Pay | Bank transfer | KRW |
 Argentina | Transfer to a CVU or CBU | Bank transfer to a CBU | ARS |
 Venezuela | Pago Móvil | Pago Móvil / bank transfer | VES |
| Turkey | Havale, IBAN | Havale, IBAN | TRY |
| Europe and the UK | Visa, Mastercard, Apple Pay, Google Pay | OCT to cards, SEPA Instant | EUR, GBP (UK), USD (OCT, EU/EEA/CH) |
We're launching in North Africa and the Middle East, and we build routes to new markets on request.
Three ways to connect
Every path runs the same pay-in: you create it, the buyer pays from a banking or wallet app, ATLAS checks the amount, the bank reference and the time, your balance is credited in USDT, and a signed webhook goes to your server. The back end you build stays the same whichever front end you choose, and pay-ins covers methods, statuses and the contract.
- Payment link: create a pay-in and send the buyer to
checkout.url. Nothing to build on the front end. - Embedded checkout: the same pay page inside your own checkout. Add our script and call
Atlas.mount('#atlas-pay', { url: checkout.embedUrl }). It opens only on the domains you register, set withPUT /api/merchant/checkout-settings/originsor by the ATLAS team. - H2H API: server to server with HMAC-signed requests. You show the payment details in your own interface.
Integration starts in the sandbox, which runs the same contracts as production. Signed webhooks report final statuses and dispute events, with up to 10 delivery attempts.
POST /api/merchant/pay-in{ "amount": 3049, "currency": "INR", "paymentMethod": "upi", "merchantOrderId": "order-12345", "checkout": { "returnUrl": "https://shop.example/done" }}201 Created{ "payInId": "5e6f7a8b-9c0d-41e2…", "amount": 3049, "checkout": { "url": "https://api.atlas-online.io/pay/…" }}A pay page buyers finish
The hosted page speaks English, Hindi and Korean, and the buyer can switch between them. PhonePe and Paytm open with the amount filled in, any other UPI app pays by QR or UPI ID, and a Pay, Confirm, Done tracker updates on its own before the page returns the buyer to your site. Preview colours, fonts and corner radius in the sandbox. For production, save the theme through the settings API or ask the ATLAS team.
The hosted payment page covers everything the page does.
Pay-outs to local accounts and cards
Pay-outs go to UPI IDs and to bank accounts by IMPS in India, to Korean bank accounts, by Pago Móvil / bank transfer in Venezuela, by bank transfer to a CBU in Argentina, by Havale and IBAN in Turkey, and by SEPA Instant or OCT to cards in Europe and the UK.
They draw on your pay-out balance. The USDT is reserved when you create a pay-out and charged only after the transfer is confirmed, and a pay_out.completed webhook tells you when it's done. Recipient fields for each rail are on pay-outs.
Every payment and every USDT in your dashboard
-
Accepted, minus commission, equals credited, for any period next to the previous one
-
Conversion and median time to pay
-
Two balances: pay-ins collect, pay-outs spend, and you move USDT between them
-
A log of every API call and webhook delivery, with CSV export
-
A test payment page
-
Balances shown in the currency you prefer
Pay-in and pay-out lists filter by status, market and dates. Each payment opens as a card with the fiat and USDT amounts, the rate and its webhooks.
When your balance reaches your threshold, USDT goes to your TRC-20 wallet automatically. You can also withdraw on request, from the dashboard or through the API. USDT settlement explains thresholds and withdrawals.
Disputes and security
If a completed pay-in or pay-out looks wrong, you open a dispute through the API, for the full amount or part of it. The platform holds the funds involved until a decision, a 24-hour evidence deadline applies, and you get dispute.opened and dispute.resolved webhooks.
What protects the account and the money:
-
HMAC-SHA256 signatures over the timestamp and the body. Expired and unsigned requests are rejected before processing
-
Idempotency: a retry with the same order id returns the original answer, so nothing is charged twice
-
Two-factor sign-in: your access key plus a code in Telegram or by email
-
Roles with an audit log of every staff action
-
Allowed embedding domains: the checkout opens only on the sites on your list
How to start
-
Tell us the market, the volume and how you want to connect
-
Get a sandbox dashboard and API keys. Same contracts as production
-
Run a payment end to end: pay, confirm, webhook, return. The test payment page creates a real sandbox payment
-
Go live with our team on the line. Markets, limits and terms are agreed in advance
FAQ
Which payment methods can I accept in India?
UPI, UPI Intent and IMPS. On the hosted page, PhonePe and Paytm open with the amount filled in, and any other UPI app pays by QR or UPI ID.
How do I receive my money?
In USDT. When your balance reaches your threshold, USDT goes to your TRC-20 wallet automatically. You can also withdraw on request.
Do you have a sandbox?
Yes. It runs the same contracts as production, so the code you test is the code you ship.
Can the pay page match my brand?
Yes. Preview colours, fonts and corner radius in the sandbox. For production, save the theme through the settings API or ask the ATLAS team. You can also hide the ATLAS wordmark.
Do you support pay-outs?
Yes, in every market we list: local bank transfers, UPI and IMPS in India, Pago Móvil in Venezuela, SEPA Instant and card pay-outs in Europe.
Which countries does ATLAS cover?
India, South Korea, Argentina, Venezuela, Turkey, and Europe with the UK. We're launching in North Africa and the Middle East, and we build routes to new markets on request.
Do I need a bank account in every country?
No. ATLAS settles with you in USDT on TRC-20, at the rate fixed at the moment of each operation.
How do I know a payment is confirmed?
Signed webhooks report final statuses and dispute events, with up to 10 delivery attempts. You can also read the status through the API or in your dashboard.
Accept local payments, get paid in USDT
Send the market, the expected volume and how you want to connect. We come back with the methods and the route, and open the sandbox.
or write to business@atlas-online.io