Overview
An API for every single payment you can think of. Accept payments, automate bank transfers, issue virtual cards and create recurring payments programmatically.
Welcome to Mamo's API
Mamo is one flexible platform for all your business payments. Whether you need to accept payments via API, automate bank transfers, issue virtual credit cards, or create recurring payments programmatically, Mamo makes it all effortless, secure, and scalable.
What can you do with Mamo?
- Get paid faster, however you sell: create a payment link and share it with customers via email, text message, or social media, or embed payments that let customers pay without leaving your website.
- Put recurring revenue on autopilot: automate subscription payments and get repeat revenue without chasing invoices.
- Send bank transfers to third parties worldwide: make payments to customers, vendors, or any third party around the world in seconds, and eliminate the manual work.
- Keep expenses under control: manage, classify and export the expenses incurred on your team's cards, and sync them to your accounting software.
- Issue cards: issue virtual cards for your team, and Partner cards that let you send funds to vendors, freelancers and suppliers outside your business.
- Run a marketplace: accept payments from buyers, take out a commission and send the rest to sellers.
Who is this for?
- Businesses: start with ready-to-use integrations for platforms like Shopify and WooCommerce — see the Help Center. Our APIs are fully documented and accessible to anyone, but we recommend that you work with a developer to complete a custom integration.
- Developers: use direct API access to implement fully customized solutions. Leverage our well-documented APIs, webhooks, and sandbox environment to build and test integrations with ease.
Get started in 3 steps
- Get your API key: log in to your Mamo dashboard, open the Developer section, and create your API key. See Authentication.
- Test in the sandbox: your sandbox account is an exact replica of production, with its own dashboard and API key. See Sandbox testing.
- Build your integration: follow the Quick start to create your first payment link, pay it with a test card and receive the webhook.
Explore products
Get paid faster, however you sell.
Recurring revenue, on autopilot.
Send bank transfers to third parties worldwide.
Expense management that keeps up with your business.
Pay vendors and freelancers, without the back and forth.
Payments. Commissions. Payouts. All-in-one.
Walkthroughs
Step-by-step code in cURL, Node.js, Python and PHP. See all of them in Recipes.
Key concepts
Recipient vs. seller vs. sub-merchant
A recipient is a payout destination registered via POST /recipients — a UAE IBAN, a name, and a reason. It is not a sub-merchant: there's no trade license, MOA, KYC review, or separate dashboard/login for the seller. Registration is immediate because the IBAN itself is treated as sufficient verification.
"Seller" or "provider" are the business terms for whoever a recipient represents in your marketplace (a vendor, a driver, a host). In the API they're just a recipient — the API doesn't model a distinct "seller" entity with its own merchant-of-record status. Your business (the marketplace) is the merchant of record for every transaction and carries chargeback, refund, and VAT liability; recipients are not merchants of record. See Marketplace for the full flow.
Split payments
payouts_share is a field on Create payment link that splits a payment at capture time: a percentage or fixed amount of the payment routes to a recipient's balance, with the rest staying in yours. It is not a delayed or escrowed split — the recipient's share is credited as soon as the payment captures, and reaches their bank account on the next scheduled payout run (see Marketplace for timing and hold-pattern options).
Settlement vs. payout
These describe two different money-movement flows — conflating them is a common mistake.
Settlement is what pays out your own captured revenue to your own bank account. It's a single combined event: Mamo clears the captured amount and transfers it to the bank account on file, which is what produces the settlement_amount, settlement_fee, and settlement_date you see on the Payment Object. On automatic settlement (the default) this happens on your configured schedule (immediate, weekly, or monthly) with no API call on your part. On manual settlement, there is no public API to trigger it yourself either — it's a Mamo-side action; talk to your Mamo contact about your account's specific behavior.
Payout (the Payouts API) is a distinct, narrower action: it moves funds out of a recipient's accrued balance (from payouts_share) to that recipient's bank account. It requires a recipient_id — there is no way to target your own account through this API, so it's not a mechanism for receiving your own revenue under any settlement configuration.
For card fees, refund fees and how long you can hold funds, see the Commercial FAQ.
Stay up to date
The Changelog lists every change to the API. For help with your account, see Support or the Help Center.
Updated about 5 hours ago