Money movement

du Pay International Transfer: Fees, Limits, and Payout Fit

du Pay enables UAE-originating international remittances, but consumer transfer availability does not establish business payout suitability. Here is how to check costs, recipient details, delivery, and operational limits.

Illustration of a UAE mobile wallet sending payments to an overseas bank, mobile wallet, and cash pickup counter

A du Pay international transfer lets eligible UAE residents send money abroad through the du Pay wallet, with bank deposit, mobile wallet, and cash pickup options depending on the destination. Fees vary by country and amount; check the exchange rate, recipient amount, delivery estimate, and applicable limits in the app before confirming.

For finance teams, the key distinction is between an individual sending a remittance and a company running international payouts. The supplied product information establishes consumer remittance capabilities, not a corporate bulk-payment service. Teams paying hundreds of vendors, contractors, or sellers should verify permitted business use and operational controls before treating du Pay as a payout channel.

What du Pay international transfers support

du Pay is a UAE digital wallet operated by EITC Financial Services L.L.C., a subsidiary of du, and licensed by the Central Bank of the UAE. Registration requires UAE residency and an Emirates ID. It is a money-transfer product, not the same service as sharing du mobile airtime or buying an international mobile top-up.

The service supports international transfers to bank accounts, mobile wallets, and cash pickup locations. These are delivery categories, not a promise that every category is available in every country. Consult the destination options in the app and the provider’s December 2025 Key Fact Statement when checking product terms.

For an operator, the meaningful unit of coverage is the complete route: UAE origin, destination country, receiving currency, delivery method, and recipient eligibility. A country appearing in a coverage list does not establish that a particular bank or wallet can receive a particular payment.

How to send money with du Pay

The exact screens and requested fields can change. Use this workflow as a preparation checklist rather than a fixed description of the app interface:

  1. Register and complete verification. Use your own eligible UAE account and Emirates ID. Resolve verification issues before planning a time-sensitive transfer.
  2. Fund the wallet. Supported funding options described in the research include debit or prepaid cards, inward bank transfers, and payment machines. Check availability and any applicable funding conditions.
  3. Select the destination and delivery method. Confirm that the recipient can actually access the chosen bank account, wallet, or pickup service.
  4. Enter beneficiary details. Follow the app’s country-specific requirements and verify identifiers directly with the recipient.
  5. Review the complete quote. Check the total AED debit, transfer fee, exchange rate, receiving currency, recipient amount, and estimated arrival.
  6. Confirm and retain the reference. Keep the receipt and follow the transfer status until delivery is confirmed.

Recipient details depend on the delivery method

The table below is a verification framework, not a universal du Pay field specification. The app’s requirements for the selected destination take precedence.

Delivery methodDetails to verifyAccess checkCompletion evidence
Bank depositAccount name, account number or IBAN, required routing detailsAccount accepts the selected currency and transfer typeCredit to the beneficiary account
Mobile walletWallet provider, registered mobile number, required name fieldsWallet is active and can receive the amountCredit to the intended wallet
Cash pickupRecipient name matching ID, required contact informationRecipient meets collection requirementsCollection confirmation

Do not substitute one identifier for another: a wallet telephone number is not a bank account number. For bank-payment preparation across destinations, use the country-by-country contractor payment guide, then validate the actual fields required by du Pay.

Fees and FX: compare what the recipient receives

There is no single international transfer fee that applies to every du Pay destination and amount. A useful comparison holds either the sender’s total budget or the recipient’s required amount constant.

  • Fixed sender budget: Compare how much local currency arrives for the same total AED debit.
  • Fixed recipient amount: Compare the total AED required to deliver the same amount abroad.
  • Like-for-like delivery: Compare bank deposit with bank deposit, or wallet delivery with wallet delivery, at approximately the same time.

A waived transfer fee does not establish that the currency conversion is cost-free. Examine the offered FX rate as well as the explicit charge. Also check whether recipient-side charges or withdrawal costs affect access to the money; do not assume that these apply to every route.

Pakistan: check the conditions behind free transfers

du Pay’s Pakistan transfer guidance states that transfers of AED 750 or more are free, effective July 3, 2025, while smaller transfers incur a fee. The same guidance states that only one free international transfer to one beneficiary in Pakistan is permitted within 24 hours under the cited State Bank of Pakistan guidelines.

Treat this as a destination-specific policy, not a global price promise. Confirm the current offer and eligibility in the app. Do not assume repeated transfers to the same beneficiary will all qualify for a fee waiver.

Transfer limits: distinguish published history from current allowance

The January 2025 du Pay Key Fact Statement lists international transfer limits of AED 25,000 per transaction, AED 25,000 daily, and AED 25,000 monthly. These are dated published figures, not a guarantee of the allowance available to an account today.

The supplied research includes conflicting third-party figures, but does not establish why they differ. Do not attribute the discrepancy to verification tiers without confirmation. Check the current official statement and the account’s available allowance before funding a transfer.

For a payment run, the relevant constraint is remaining capacity, not just the maximum size of a single transfer. Ask how daily and monthly periods are calculated and how pending, failed, or refunded transfers affect available limits. Never split payments across personal accounts to bypass controls.

How long does a transfer take—and can it be cancelled?

There is no adequately supported universal arrival time for every du Pay international route. Use the estimate for the selected destination and delivery method, rather than applying one corridor’s speed claim to all transfers.

For example, reporting on the du Pay–GCash partnership describes instant wallet-to-wallet transfers from the UAE to GCash in the Philippines, available around the clock. That describes a specific wallet corridor, not a guarantee for international bank deposits or cash collection.

The supplied du Pay terms state that transfers cannot be cancelled once delivered to a beneficiary bank account or mobile wallet. Cash pickup transfers can be cancelled without a cancellation fee if the beneficiary has not collected the funds. Check the applicable terms and status before requesting cancellation; a cancellation request is not proof that a refund has completed.

If a transfer appears delayed, retain its reference, amount, submission time, destination, and current status. Ask support whether it is pending review, awaiting delivery, rejected, or returned. Avoid submitting a replacement until the original payment’s position is established.

Can finance teams use du Pay for business payouts?

Do not infer corporate payout permission from consumer remittance availability. The research does not establish corporate onboarding, bulk upload, payout APIs, delegated user access, or approval workflows. Their absence from this evidence is not proof that du Pay cannot offer them; it means buyers need written confirmation.

Before using the service for company obligations, obtain answers to these questions:

  • Are the business entity, payment purpose, and recipient types permitted?
  • Who owns the sending account and funds, and whose name appears on the payment record?
  • Can the required volume fit within the applicable limits?
  • Can one employee prepare payments while another approves them?
  • Can records be exported with beneficiary details, fees, FX, status, and references?
  • Who handles incorrect details, delayed delivery, returns, and refund reconciliation?

An employee receiving wages and independently remitting money abroad is a different activity from an employer using that employee’s wallet to pay overseas suppliers. Keep account ownership, authorization, and payment purpose explicit.

Choose the route that fits the obligation

For an eligible individual remittance, the next step is straightforward: verify the recipient, obtain a live quote, check limits and delivery conditions, and retain the transfer reference.

For recurring business disbursements, first validate permitted use and evidence of payment completion. Then evaluate whether the workflow can support approvals, accounting, and exception handling at your volume. Payouts.com’s payout automation is relevant when the requirement is a coordinated company payment operation rather than a sequence of individual wallet transfers. Start with your actual destinations, recipient types, and control requirements—not the headline country count.

Created with AI assistance. Sources are linked in the article; this content is general information, not legal, tax, or financial advice.

Discussion

31 comments
  • Diego Rahman ·

    The repeated emphasis on route-level verification is correct but the operational burden is the real story. If you're paying 80 contractors across 12 countries you can't manually validate every bank-wallet-currency combination in a consumer app before each payment cycle. This is why corporate payout platforms exist and why trying to repurpose a remittance product creates more work than it saves.

    Reply
  • Aarav Becker ·

    The delivery method verification table is useful but in practice the hardest part is that the app won't always tell you why a particular beneficiary detail fails validation until after you've funded the wallet. We lost two days last month when a contractor's IBAN format was technically correct but the receiving bank wasn't in du Pay's network for that corridor, and the error only surfaced at confirmation.

    Reply
    • Pablo Yamamoto ·

      We hit the same thing with a Pakistan account last quarter. The failure message was just 'invalid beneficiary' even though we'd triple-checked the IBAN with the contractor. Turned out du Pay needed the bank branch code in a separate field that only appeared after selecting a specific bank from their list, not as part of the IBAN string. Would have saved us a week if the validation error had actually said what was missing.

    • Hiroshi Muller ·

      We switched to validating recipient details with a test transaction first, even if it costs a small fee. The failed-after-funding loop isn't worth the time, especially when you're trying to hit a payment deadline and the wallet balance is now stuck pending a refund.

  • Aisha Rossi ·

    The funding-first problem is understated here. We've seen teams load a du Pay wallet assuming the limit applied to their account, only to discover the actual available capacity was lower after the funds were already sitting there. Now we verify the exact remaining monthly allowance before any wallet top-up, which adds friction but prevents capital being stuck in an unusable channel.

    Reply
    • Ingrid Patel ·

      We do the same now. The other piece is understanding how the monthly period resets—calendar month versus rolling 30 days makes a huge difference when you're planning payment runs at month-end. The KFS doesn't specify and support gave us conflicting answers.

    • Chen Romano ·

      We do the same now. The other piece is understanding how the monthly period resets—calendar month or rolling 30 days makes a huge difference when you're trying to schedule recurring contractor payments and can't afford to have funds stranded.

  • Liam Novak ·

    The route-specific verification point is critical and often missed in vendor onboarding. We had a case where India bank deposit was available but the specific IFSC code for a regional cooperative bank wasn't supported by the underlying rail, even though the country and method were both listed. Now we require full beneficiary details including intermediary codes before we finalize any channel decision.

    Reply
    • Sara Andersson ·

      We started requiring the recipient to send us a screenshot of their bank's accepted payment methods page before we add them to any new rail. It's annoying friction but cheaper than failed transfers and the reconciliation mess afterward.

    • Tomas Cohen ·

      We ran into the same thing with mobile wallet delivery in the Philippines. The provider was listed, the delivery method was available, but certain regional wallet accounts couldn't receive international transfers even though domestic wallet-to-wallet worked fine. Had to fall back to bank deposit for those beneficiaries.

  • Fatima Fernandez ·

    The point about fixed sender budget versus fixed recipient amount comparison is important and often overlooked when evaluating transfer services. We've seen AP teams get burned because they only looked at the headline fee and didn't check what actually arrived on the other side after FX spread and recipient charges.

    Reply
    • Sofia Nguyen ·

      We started putting both the all-in AED cost and the guaranteed recipient amount in the payment approval workflow after a similar issue. The FX spread variance between quote time and execution was the other surprise—especially on less liquid corridors where the rate can shift meaningfully if you delay confirmation.

    • Yuki Weber ·

      Exactly. We now build the comparison spreadsheet with both directions—what arrives for X sent, and what we need to send to deliver Y—because depending on the use case one matters more than the other. For fixed-price contractor agreements the recipient amount is the binding constraint.

  • Bianca Ali ·

    The point about checking recipient-side withdrawal costs is something we missed initially. We had several Kenya mobile wallet payments where the transfer arrived fine but the recipient lost 8-10% in cash-out fees, which completely changed the economics compared to direct bank deposit on the same route.

    Reply
    • Andre Sharma ·

      We now include recipient-side fees in the route comparison spreadsheet explicitly. For mobile wallet destinations we ask the beneficiary to confirm both the receive limit and the cash-out cost before we approve the route, otherwise the effective rate can be totally different from what the app quotes.

    • Amara Johansson ·

      We had the same blind spot with mobile wallet routes. Now we explicitly ask the recipient for the full fee schedule—both the transfer-in fee (if any) and the cash-out fee—before we select the delivery method. Otherwise you're optimizing the wrong half of the equation.

  • Grace Bauer ·

    The verification framework table is helpful but it doesn't address the scenario where a beneficiary uses different identifiers across multiple receiving banks in the same country. We've had contractors in India who needed payments to ICICI versus HDFC accounts with slightly different name formats, and du Pay's validation rejected one despite both being legitimate. Would be useful to know if there's any normalization logic or if it's purely exact-match per destination bank.

    Reply
    • Carmen Kim ·

      We've seen this too with contractors across Southeast Asia. The name mismatch issue is compounded when the du Pay validation logic is stricter than the receiving bank's—sometimes you can't even submit a transfer with the variant that the bank actually requires. Ended up standardizing on one account per payee to avoid the routing headache.

    • Elsa Chowdhury ·

      That's a name-matching control issue, not really a du Pay-specific problem. Most consumer remittance apps don't validate beneficiary name consistency across institutions because they're designed for one-off sends. If you're running structured payables you need either a single validated beneficiary record per legal entity or a reconciliation process that confirms the mismatch is intentional, not a typo or fraud risk.

  • Kwame Berg ·

    The 25,000 AED monthly limit makes this a non-starter for any actual business payout volume, and the fact that published limits conflict with what's actually available in-app is a red flag for operational reliability. We need predictable capacity planning, not scavenger hunts through KFS documents to figure out if we can fund next week's contractor run.

    Reply
    • Daniel Haas ·

      Agreed on the capacity issue, but the conflicting limits problem is bigger than just planning. If you can't even trust the published documentation to match reality, how do you write runbooks or set up approval workflows? Finance ops runs on predictable rules, not mystery boxes.

    • Zara Santos ·

      Exactly this. We evaluated du Pay last quarter for contractor payments and the monthly ceiling combined with zero clarity on how the cycle resets made it unusable. If you can't trust the limits documentation, you can't build a payment calendar around it.

  • Malik Diaz ·

    The conflicting limit figures without explanation is frustrating. If the official KFS says 25k monthly but the app shows something different, that's a reconciliation problem that wastes time when you're trying to plan a payment run. Has anyone actually tested where the real ceiling sits for a verified business account?

    Reply
    • Elena Petrov ·

      Same experience here. We called support and got a third number entirely, which they said depended on account age and transaction history. The documentation lag is real and makes it impossible to commit to du Pay as a primary channel when you can't reliably forecast capacity week to week.

    • Felix Nakamura ·

      We hit this exact issue when trying to set up a backup channel for UAE vendor payments. The app showed a higher daily limit than the published statement, but support couldn't confirm which governed until we actually attempted the transfer. Ended up treating the lower published figure as the planning constraint to avoid mid-run failures.

  • Hana Moreau ·

    The Pakistan transfer limit of one free transfer per beneficiary per 24 hours is a real operational constraint if you're paying multiple invoices to the same supplier. We ran into this exact scenario with a Karachi-based vendor who invoices us weekly—had to either batch everything into one consolidated payment or eat the fee on the second one. Worth modeling this into your payment calendar if you have repeat payees.

    Reply
    • Nadia Kowalski ·

      We ended up splitting payments across two beneficiary accounts for the same supplier to work around this. Not ideal from a reconciliation standpoint but it kept the fee waiver intact. Did you find a better workaround or just accept the fee on subsequent transfers?

    • Viktor Marino ·

      That beneficiary-level throttle is exactly why consumer remittance rails don't scale for AP operations. You need either proper bulk file submission or at minimum the ability to queue multiple payments to the same entity without artificial 24-hour gates between them.

  • Maya Park ·

    Appreciate the distinction between 'a country appearing in a coverage list' and actually being able to deliver to a specific bank or wallet. We've been burned by assuming global coverage means our exact routing combo works, especially with smaller regional banks in Southeast Asia.

    Reply
    • Leila Mbeki ·

      Same lesson for us with cash pickup in parts of Latin America. The country was listed, the partner network was supposedly national, but half the branches in smaller cities couldn't actually process the transaction code. Now we verify the exact branch or agent location before we promise delivery to anyone.

    • Julia Tanaka ·

      Same lesson. The route-level verification is essential. We now require a test transaction to the exact account and currency pair before adding any channel to our payout matrix, regardless of what the coverage page says.

Run your entire money cycle on one ledger

Global payouts, AP/AR automation, and AI agents with their own wallets and spend limits.

Get started