Card limits and spend policies help you stay in control of how your Mamo Cards are used. When issuing multiple cards across your team, they let you automate your company's expense rules so spending stays within set limits, while cutting down on admin work.

There are two levels of spend controls on Mamo:

Together, these let you separate who sets the guardrails for the whole company from who issues cards and manages day-to-day limits for their team.

The following controls can be set as global policies, card-specific controls, or both:

Set a maximum amount per single transaction, giving you control over the size of the purchases your team can attempt. Any transaction that exceeds this limit will be declined.

Set total spending limits on a card in two ways:

With category restrictions, you can define the types of purchases allowed on a card, making sure it's used for its intended purpose. Current categories include:

On an individual card, you can define either a block list or an allow list, but not both at the same time:

Note: Global spend policies currently support block lists only. Allow lists remain available as a card-specific control.

You can prevent physical cards from being used to withdraw cash at an ATM. When enabled, the card still works for online purchases and in-store payments, but any ATM withdrawal will be declined.

Global spend policies are company-wide rules that apply automatically to your cards, so you don't have to configure the same limits over and over. You can choose whether a policy applies to all cards or only a subset of cards, and this is fully configurable. When a new card is issued, it inherits any global policies that apply to it by default, and these can't be overridden at the card level.

For example, an admin can set a global monthly limit of AED 20,000 on all cards, or block categories like Fuel & Transportation for specific users. A sales manager issuing cards for their team can then set a lower limit, say AED 1,000 per card, but they can't set anything higher than the global cap.

What you can set as a global policy:

Who each policy applies to:

Global policies apply to all existing and future cards. If a new, more restrictive global policy is applied to a card that has already spent above the new limit, that's fine, the card is simply treated as having reached its limit, and future transactions will decline.

Global policies do not apply to partner cards.

You can edit or remove a global policy at any time.

Card-specific controls are set on an individual card, either while issuing it or from the card details page. They're useful when a particular cardholder needs tighter limits than the company-wide default.

The four limit types work together in a hierarchy, from the highest ceiling to the tightest restriction:

If you set limits that conflict with this hierarchy, you'll see an inline error and won't be able to save until it's resolved.

Card-specific controls can only make a card more restrictive than its global policies, never less.

For category restrictions, a global block list is always enforced. If a card has its own block list, the two are merged, and items inherited from the global policy can't be removed. If a card has an allow list, any category that appears on the global block list is removed from it and can't be added back.

Spend controls are applied when issuing a new card:

Spend controls can be amended at any time by users with the right permissions:

Sometimes a cardholder needs to spend more than their assigned limits. In these cases, admins can submit an out-of-policy spend request on their behalf. This temporarily extends the spend limit by a specific amount so the cardholder can make the necessary purchase. Once the extended amount is used, the card automatically reverts to its standard limits.