Nomupay provides the following set of reports, and this section will describe the Transaction Activity Report:
| Product Offer | Report name | Cadence | Format | Delivery method |
| Informational Cash Flow | Daily | CSV |
|
|
| Funding Statement | Daily (after funding) |
|
||
| MDR Funding Report | Daily (after funding) | CSV |
|
|
| IC++ Funding Report | Daily (after funding) | CSV |
|
|
| Transaction Activity Report | Daily, weekly, or monthly | CSV | ||
| Payment Status Report | Daily, weekly, or monthly | CSV |
Overview
The transaction activity report provides you with detailed payout transaction information within a given day [DATE]T00:00:00.000Z to [DATE]:23:59:59.999Z UTC whereby the format is [yyyymmdd] Thh:mm:ss.sssZ. The data in this report can be used to help you track the movement of funds through the unified platforms disbursements system through to the recipient’s preferred transfer method. The transaction activity report is ordered by transaction date and transaction sequence and captures all of the transaction for your account and all of the recipients (i.e., sub accounts) that are linked to your account. The transaction activity report is formatted with the file name transaction_activity_report_[accountId]_[yyyymmddhhmmss].csv.
Reports for the Payouts solution are provided in comma-separated values (CSV) file format. They are delivered through email. Reports can be generated on a daily, weekly or monthly basis, depending on your requirements, and they are based on UTC.
Report Data
| Column / Field Name | Description | Supported Options (if applicable) | Format / Example Value |
|---|---|---|---|
| Account ID | The unique merchant identifier assigned by uP POM during onboarding preceded by the EID identifier | EID-63ec06ef0c0ac4359 | |
| Sub Account ID | This is the unique uP Recipient ID of a recipient in the uP Platform preceded by the SID identifier. NOTE: Sub Account ID is only populated if there is an activity on the sub-account. |
SID-63ed218545405edec | |
| Amount | Transaction amount. Two decimal digits. Amounts are formatted using a dot (".") | 2358.20 | |
| Currency | Payment currency. Currency three letter code ISO 4217-Alpha 3 | MYR | |
| Transaction Type |
The transaction types. Can be as follows:
|
|
Text, as defined in Supported Options column |
| Transaction Description | Description of the transaction. Can either be passed by the merchant (for a payment transaction) or will be generated by the system (e.g. Foreign Exchange Fee.) | ||
| Transaction Direction |
Denotes if the transaction is a debit or a credit. Can be as follows:
|
|
Text, as defined in Supported Options column |
| Transaction Date | Transaction date and time. NOTE: the time zone will be set based on the merchant’s location |
YYYY-MM-DDThh:mm:ss | |
| Fee Amount | Fee amount. Two decimal digits. Amounts are formatted using a dot (".") When not applicable this field will be left empty. |
2.00 | |
| Fee Currency | Fee currency three letter code ISO 4217-Alpha 3 | MYR | |
| FX Rate Used | The foreign exchange rate that is used on the transaction. When not applicable this field will be left empty. |
1.67865265 | |
| Payment ID | Payment's unique identifier assigned by the unified Platform preceded by the PMT identifier | PMT-64180286ed496113a | |
| Payment Reference | Unique identifier assigned to payment by merchant | testPayment001 |