Refund Breakdown on Transaction DetailsThe
GET /charges/{chargeId}response now includes arefundsarray with a breakdown of each individual refund issued against the charge (id,amount,amount_currency,billing_amount,billing_amount_currency). We've also addedsettlement_fee,settlement_vat,payment_link_id,payment_link_url,external_id,max_refund_amount, and card expiry (card_expiry_month,card_expiry_year) andcard_idfields to the response.23/07/26
Phone Number for Prefilled Customer DetailsWe've added a new field called
phone_numberto thePOST /linksandPATCH /links/{linkId}endpoints. Along withprefilled_customerobject in the response.20/07/26
International PayoutsWe've added a new endpoint,
POST /international_payouts, to initiate an international payout to an existing recipient created via the Create Recipient API. The destination currency, corridor, and FX rate are determined automatically from the recipient's bank details, and the endpoint requires anIdempotency-Keyheader to safely retry requests.17/07/26
IBAN ValidationWe've added a new endpoint,
GET /iban/validate, which validates a UAE IBAN and returns the bank it belongs to. This is useful for verifying a recipient's bank details before creating them with the Create Recipient API.17/07/26
Payout to a Saved RecipientWe've added a new field called
recipient_idto thePOST /disbursementsendpoint. When provided, the disbursement uses the bank details already saved against that recipient, so you no longer need to pass raw bank details (first_name_or_business_name,last_name,account) on every payout.17/07/26
Recipient ID FieldThe Create Recipient response now also returns an
idfield. The existingidentifierfield is kept for backward compatibility, but new integrations should useid.17/07/26
Change Customer SubscriptionWe've added a new endpoint,
PATCH /subscriptions/{subscriptionId}/subscribers/{subscriberId}/change_customer_subscription, which upgrades a subscriber to a target subscription without requiring the customer to re-enter their card details. The difference between plans is prorated and charged automatically before the subscriber is moved onto the new subscription.14/07/26
Create Subscription APIWe've added a new endpoint,
POST /subscriptions, which lets you create a subscription's billing schedule (frequency, interval, start/end date) independently of a payment link. Pass the returned identifier as the newsubscription_idfield on the Create Payment Link or Update Payment Link APIs to attach it — the previous inlinesubscriptionobject is still supported for backward compatibility.14/07/26
Subscription Terminology UpdateWe've updated our API docs to consistently use "subscription" instead of "recurring payment" throughout, including renaming the Cancel Recurring Payment endpoint to Cancel Subscription. This is a documentation/terminology change only — no request or response fields were affected.
07/07/26
Invoices APIWe've added a new endpoint,
POST /invoices, to create and send an invoice to a customer via email. You can configure the amount, currency, customer details, VAT, processing fees, and an external ID, and the response includes a hostedpayment_urlfor the customer to pay the invoice.20/04/26
Account BalancesWe've added a new endpoint,
GET /finances, which returns the balances of your business's different Mamo accounts (main wallet, debit, cashback, etc.) along with each account's currency and type.16/04/26
Subscriptions Available to All MerchantsSubscription payment links (the
subscriptionobject on the Create Payment Link API) no longer require the Premium Business Plan and are now available to all merchants.16/04/26
Partner CardsWe've added a full Partner Cards API for issuing and managing virtual cards for your business partners:
POST /partner_cardsto create a card,GET /partner_cardsandGET /partner_cards/{identifier}to list and view cards,PATCH /partner_cards/{identifier}to update a card's spending limit,PATCH /partner_cards/{identifier}/cancelto cancel a card, andGET /partner_cards/{identifier}/transactionsto fetch a card's transaction history.16/04/26
Update Expense & New Webhook EventsWe've added a
PATCH /expenses/{expenseId}endpoint to update an expense's description, invoice number, and status. We've also added 4 new webhook events —expense.create,expense.update,card_transaction.create, andcard_transaction.update— that you can subscribe to via the Register Webhook API.16/04/26
Hold and Charge Later for Merchant Initiated TransactionsWe've added a new field called
hold_and_charge_laterto thePOST /charges(Merchant Initiated Transaction) endpoint. This allows you to place a payment on hold and capture it later using the Capture API, the same way this was already possible for payment links.16/04/26
Card Transactions, Expenses & ReceiptsWe've added new endpoints to track card spend:
GET /cards/transactionsandGET /cards/transactions/{transactionId}return card transactions along with their associated expense details, andGET /expenses/receipts/GET /expenses/receipts/{identifier}return uploaded receipt files for an expense.16/04/26
Terms and Conditions for Payment LinksWe've added a new field called
terms_and_conditions_urlto thePOST /linkendpoint. If provided, the customer will be required to accept your terms and conditions before proceeding to payment.16/04/26
Custom Data and External ID for Merchant Initiated TransactionsWe've added 2 new fields called
custom_dataandexternal_idto thePOST /chargeendpoint. This allows you to send custom objects and your own ID to associate with the charge.13/08/24
Receipt for Merchant Initiated TransactionsWe've added a new field called
send_customer_receiptto thePOST /chargeendpoint to enable or disable automated receipts after each charge using a saved card.24/07/24
Hold Funds and Charge LaterWe've added a new field named
hold_and_charge_laterto thePOST /linkendpoint. This functionality allows you to hold funds on a card and then capture the payment later using the Capture API.23/04/24
Payment Link RulesWe've added a new
rulefield to thePOST /linkendpoint. This field allows users to define business rules for the payment link, such as restricting accepted card types based on their BIN numbers.14/03/24
Virtual Corporate CardsWe've introduced a new API for creating Virtual Corporate Cards, single-use cards designed to streamline corporate expenses such as travel and accommodations.
28/02/24
Payout Shares & RecipientsWe've introduced a new field called
payout_shareto thePOST /linkendpoint. This feature automates splitting a portion of the payment to a recipient you create using the Create Recipient API.We've also added functionalities to delete, retrieve, and update recipients you've created.
20/02/24