Atlas Pay is a payment platform for businesses that want to accept cards and be paid into their own bank account. Ask for the money with a link, a QR code, a contract, a subscription, or an online store, and run the whole thing from a mobile app, a desktop app, or the web. Live in 28 countries.
Accepting a card should not require renting a machine, commissioning a checkout, or joining a queue at a merchant-services desk. It should require a phone and a bank account.
That is the entire brief we work to. Every product we ship is measured against one question: does this shorten the distance between “please pay me” and money in the business’s account, without making the customer do anything unusual?
Most businesses do not lack customers willing to pay by card. They lack a way to accept the card that does not involve hardware, a developer, or a spreadsheet of payment screenshots.
Money software earns trust slowly and loses it instantly. These are the habits that keep the product honest.
If a screen needs payments jargon to make sense, the screen is wrong. We write what a shop owner would say across a counter, and the same rule governs this website. Fees are quoted as the number that comes out of the payment, not as a range with an asterisk.
The person paying opens a link or points a camera at a code. No app, no account, no sign-up. Every design decision that would push work onto the payer has to justify itself against the sale it might cost you.
The mobile app, the desktop app, and the merchant portal are views of the same account. A payment taken on a phone at the counter is in the portal before you have put the phone down, and there is no second set of books to reconcile.
Card Issuing, the Chrome extension, and the Shopify integration are not available yet, so they carry a “soon” label everywhere they appear. Nigeria is in early access rather than general availability, and the site says so. A roadmap item is never sold as a feature.
Four moving parts between a customer deciding to pay and the money reaching your bank. Anyone evaluating Atlas Pay should be able to hold the whole thing in their head.
The mobile app, the desktop app, and the merchant portal are three windows onto the account in the middle — not three products. If you would rather build your own checkout on top of it, the API, SDKs, and integration guides are on the developer page.
Six preferences that settle most arguments before they start.
A product designed for a business in a market with fewer payment options tends to work everywhere. The reverse is rarely true, so that is the order we work in.
Create an account, verify your identity, link a bank account. Anything that adds a fourth step to that sequence has to earn its place very convincingly.
Records, refunds, and permissions should be predictable and dull. The creativity belongs in the parts a paying customer actually sees.
Whatever screen you are looking at, it is reading the same account. A payment does not exist twice, and a refund does not have to be recorded in two places.
A payment question is urgent by definition. Getting a real answer should not require explaining the whole platform to somebody first.
The roadmap says what is coming and the changelog says what arrived. Anything that is only on the first page is labelled as such, everywhere it is mentioned.
A product group working across payments, platform, design, support, and risk. We list the responsibilities rather than the people — the crew changes, the work does not.
Owns the checkout and everything behind it: card acceptance, wallets, subscriptions, refunds, and the records each one writes.
Runs the API the apps are built on, the release process for mobile and desktop, and the monitoring that tells us when something is wrong before you do.
Keeps the account legible across three surfaces, and keeps the payment page short enough that a customer does not abandon it halfway.
Builds and maintains the WordPress and WooCommerce plugin, the developer documentation, and the SDKs that sit on top of the API.
Answers questions, walks new businesses through identity verification and bank linking, and turns every recurring question into a product fix.
Reviews what we collect, what we keep, and what we promise — including which markets we can honestly say we are live in.
The initials above stand for the role, not for a named individual. We will introduce the people behind them when there is a team page to do it properly.
Free to download
No monthly fee on Free
Live in 28 countries
