Overview
uP Payouts
Send mass payments to individuals and businesses quickly and compliantly with the uP Payouts solution. Purpose-built for Enterprises and Marketplaces to send payout disbursements in Southeast Asia (Europe and Turkey coming soon), uP Payouts helps streamline the payout process and ensure an intuitive, frictionless experience for your recipients. This documentation is broken into distinct sections:
-
Introduction
- Learn how the uP Payouts solution is architected and the customer types that will benefit from implementing this type of disbursement product. Includes a deep dive on the supported Payout Models.
-
Components
- Review definitions for important Components of the uP Payouts solution, as well as how they are used. This includes uP IDs, overviews of available transfer types and methods, details on how to fund your payouts and an explanation of the uP Payouts solution’s standard reports.
-
SFTP
- Understand how to setup your SFTP access and how your SFTP directories will be configured (this will be dependent on your chosen integration method).
-
Integration: UP API
- Review important information outlining how to enable the uP Payouts solution using the uP API integration method. The uP API is the preferred integration method for the uP Payouts solution.
-
uP API Payout Reference
- This is where you will find detailed technical documentation for the uP API integration method.
-
uP API Webhooks
- Understand how webhooks can help increase visibility into your payment statuses.
Solution architecture

The uP Payouts solution is a standalone disbursement solution. It is built on a Good Funds Model which means that your organisation will be required to send funds to NomuPay prior to making payments to your recipients. These funds will be deposited into a dedicated For Benefit Of (or FBO) Funding Account. This FBO account allows NomuPay to safely and securely manage funds on your behalf.
Funds that are deposited into your Funding Account are shown within your Unified Balance. The heart of the uP Platform, the Unified Balance is composed of 3 sub-balance types: the Pending Balance, the Available Balance, and the Reserve Balance. In the uP Payouts solution, funds that are deposited into your Funding Account will be visible in the Available Balance and thus can be used for payout activities.
When you’re ready to send mass payments to your recipients, simply provide NomuPay with the required payment instructions uP API, and the uP Platform will debit funds from your Unified Balance (removing them from your Available Balance) and, depending on the Payout Model that you’ve selected, either transfer them directly to your recipients’ previously onboarded transfer method, or send them to your recipients’ uP Wallets where the recipient will have the ability to initiate a transfer to an onboarded transfer method (see Payout Model section for more details).
As the owner of the Unified Balance, you can, at any time, withdraw any available funds and send them into your designated bank account.
Customer types
The uP Payouts solution can be architected to handle 2 customer types and their corresponding use cases:
-
Enterprises and Marketplaces: Large organisations that have their own in-house payment infrastructure and are eager to technically integrate with the uP Platform to improve their fee, reward, commission or claims payout disbursement capabilities.
-
Referral Clients: Customers that have a network of potential Enterprises and Marketplaces that they wish to refer to NomuPay. Referral Clients do not technically integrate with the uP Platform themselves, rather, they assist the NomuPay team with relationship management and solutioning the proper uP Payouts solution. This could include consultants, industry associations, etc.
The remainder of the uP Payouts solution documentation will focus on aspects of the technical integration for the first customer type (Enterprises/Marketplaces). If you are interested in becoming a NomuPay Referral Client for our uP Payouts solution, please contact our solutioning team directly for more information specific to this use case.