Nomupay provides the following set of reports, and this section will describe the MDR - and IC++ Funding 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
Designed to support reconciliation efforts between the merchant’s payment acceptance and the associated funding made available on the merchant’s bank account. The funding report is generated and delivered daily, after the merchant funding has taken place.
The type of data you receive in your funding report will depend on your solution's pricing model, which can be either:
- Single Merchant Discount Rate (MDR)
- Multi Merchant Discount Rate (MDR)
- Interchange Plus Plus (IC++)
For the difference between the three types please visit the Transaction Fees chapter.
In both the MDR and IC++ version the funding report provides a line item per transaction included in your daily funding. This includes per transaction:
- The funding amount (i.e., the transaction amount minus any applicable fees and taxes have been deducted - see the Merchant Funding section for more information on the funding process), and,
- The date the funding occurred as well as,
- The associated funding ID.
To have a detailed view of the data shared in the funding report please visit the Report Data section below.
The funding report is provided in a comma-separated values (CSV) file format and are delivered through Secure File Transfer Protocol (SFTP) folder or via email, and is available for download via the Customer Portal. The file is formatted in such a way that you can automate the processing of the report data into their existing systems.
The CSV version of the funding report is formatted with the file name:
- For merchants, platforms and marketplaces:
- SFTP: daily_funding_report_funding_date=[yyyy-mm-dd]_[AccountID]__[PayOutWalletID]_[yyyy-mm-dd].csv
- Email with title: “Daily Funding Report for [yyyy-mm-dd]” sharing attachment to download the associated report: Daily_Funding_Report_[AccountID]_[PayOutWalletID]_[yyyy-mm-dd].csv
- For reseller partners:
- SFTP: daily_funding_report_funding_date=[yyyy-mm-dd]_[PartnerID]_[AccountID]__[PayOutWalletID]_[yyyy-mm-dd].csv
- Email with title: “Daily Funding Report for [yyyy-mm-dd]” sharing url(s) to download the associated report(s): [PartnerID]__[AccountID]_[PayOutWalletID]_[Counter].csv
Funding ID
When the Merchant Funding takes place, then the unified platform will annotate the bank transfer using a unique identifier, called the Funding ID. The funding ID can be used to reconcile your bank account statement with the transactions stated in your funding report. Each transaction will have a funding ID assigned to it in the "Funding ID" column of the report. Multiple transactions can be grouped into a single funding ID; this simply means that the funds from each of these transactions were "funded" to the bank account in the same transfer. Therefore, it is recommended that you use the Funding ID to reconcile deposits into your bank account with the transactions listed in the funding report.
A funding report is triggered per confirmed bank transfer to a nominated bank account (i.e., per funding ID).
- Reseller partners will receive individual funding reports for each of the merchants that they have onboarded to the unified platform provided a funding event has occurred. Each report will contain said merchant's transactions and associated funding data for a given funding ID (for example, if you have onboarded 50 merchants as a reseller client, and they have transaction activity that triggers funding daily, you will receive 50 unique funding Reports per day -- 1 per merchant and their associated funding ID).
- Merchants, platforms and marketplaces will receive 1 funding report following a funding event, which will contain all of their transactions and associated funding data for a given funding ID.
Report Data
| Column / Field Name | Description | Supported Options (If applicable) | Format / Example Value | Applicability |
|---|---|---|---|---|
| NP Transaction ID | Transaction’s unique identifier assigned by the unified Platform. | NP-69b73a945 f167503724 54403492 |
|
|
| Transaction Date | Transaction date and time. NOTE: the time zone will be set based on the merchant’s location. | YYYY-MM-DD hh:mm:ss |
|
|
| Transaction Type |
Transaction type. Can be as follows:
|
|
|
|
| Transaction Status |
Transaction status. Can be as follows:
|
|
Text, as defined in Supported Options column |
|
| Transaction Amount | Transaction amount. Two decimal digits. Amounts are formatted using a dot ("."). Amount is preceded with (-) if your balance is to be debited. |
2327.24 (for a debit) |
|
|
| Transaction Currency | Transaction currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| MDR Amount | Merchant Discount Rate amount. Two decimal digits. Amounts are formatted using a dot ("."). Amount is preceded with a (-) sign in instances where the MDR has been deducted. |
13.67 (for a deduction) |
|
|
| MDR Currency | Merchant Discount Rate currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| GRT Amount | Gross Receipt Tax amount. Two decimal digits. Amounts are formatted using a dot ("."). Amount is preceded with a (-) sign in instances where the GRT has been deducted. Only applicable for specific countries. When not applicable this field will be left empty. |
27.24 (for a deduction) |
|
|
| GRT Currency | Gross Receipt Tax currency. Currency three letter code ISO 4217-Alpha 3. Only applicable for specific countries. When not applicable this field will be left empty. | PHP |
|
|
| WHT Amount | Withholding Tax amount. Two decimal digits. Amounts are formatted using a dot ("."). Amount is preceded with a (-) sign in instances where the WHT has been deducted. Only applicable for specific countries. When not applicable this field will be left empty. |
57.22 (for a deduction) |
|
|
| WHT Currency | Withholding Tax currency. Currency three letter code ISO 4217-Alpha 3. Only applicable for specific countries. When not applicable this field will be left empty. | EUR |
|
|
| VAT Amount | Value-Added Tax amount. Two decimal digits. Amounts are formatted using a dot ("."). Amount is preceded with a (-) sign in instances where the VAT has been deducted. Only applicable for specific countries. When not applicable this field will be left empty. |
7.89 (for a deduction) |
|
|
| VAT Currency | Value-Added Tax currency. Currency three letter code ISO 4217-Alpha 3 Only applicable for specific countries. When not applicable this field will be left empty. |
THB |
|
|
| ST Amount | Sales and Service Tax amount. Two decimal digits. Amounts are formatted using a dot ("."). Amount is preceded with a (-) sign in instances where the SST has been deducted. Only applicable for specific countries. When not applicable this field will be left empty. |
146.45 (for a deduction) |
|
|
| ST Currency | Sales and Service Tax currency. Currency three letter code ISO 4217-Alpha 3 Only applicable for specific countries. When not applicable this field will be left empty. |
MYR |
|
|
| Funding Amount | Amount due to be funded to the nominated funding account. Two decimal digits. Amounts are formatted using a dot ("."). Amount is preceded with (-) if your balance is to be debited |
27.24 (for a debit) |
|
|
| Funding Currency | Funding currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| Funding Date | Date that Nomupay funds the merchant’s nominated funding account. | YYYY-MM-DD |
|
|
| Funding ID | Unique ID to be found on the merchant’s bank statement, allowing to match the transactions in the funding report and funding amount. | 45r139b5d f24fc6528 3502899 |
|
|
| Payment Method | Payment method type. |
NOTE: More payment methods are continuously added. Please ask your onboarding manager for the most recent list. |
|
|
| Card Type |
Card type. Only applicable when a card is in the payment method field (Visa, Mastercard, China UnionPay, America Express, Diners Club International).
|
|
Text, as defined in Supported Options column |
|
| Acceptance Channel |
Channel that the transaction was accepted on. Can be as follows:
|
|
Text, as defined in Supported Options column |
|
| RRN | Transaction Retrieval Reference Number (RRN). When not applicable this field will be left empty. |
123456789012 |
|
|
| ARN | Transaction Acquirer Reference Number (ARN). When not applicable this field will be left empty. |
23456789 0123 |
|
|
| Billing Date | Date fees are calculated for billing by Nomupay. | YYYY-MM-DD |
|
|
| Authorization Code | Authorisation code returned by the scheme. When not applicable this field will be left empty. |
123456 |
|
|
| Response Code | Response code returned by the issuer. When not applicable this field will be left empty. |
0 |
|
|
| Issuer locality |
Issuer locality.
|
|
Text, as defined in Supported Options column |
|
| Issuer country | Payment method issuer country. Country two letter code ISO 3166-1 Alpha 2 | HK |
|
|
| MCC | Merchant category code. Identifier that classifies a business by the type of goods or services it provides. | 1234 |
|
|
| Terminal ID | Unique ID assigned by NomuPay to terminals. | 87654321 |
|
|
| Terminal Batch | End of day ID assigned to in-store processing. | 12345678 |
|
|
| MID | Unique merchant ID assigned by the processor. | 987654321 987 |
|
|
| Store ID | Unique Location ID assigned by NomuPay preceded by the LID identifier. | LID-123456789 |
|
|
| Store Name | Unique name assigned to each store. | HAPPY STORE |
|
|
| Store country | Store’s country location. Applicable to digital ecommerce stores and physical stores. Country two letter code ISO 3166-1 Alpha 2 | HK |
|
|
| Store City | Store’s city location. Applicable to digital ecommerce stores and physical stores. | KOWLOON |
|
|
| Account ID | Unique merchant identifier assigned during onboarding preceded by the EID identifier. | EID-123456789 |
|
|
| Account Name | Merchant’s legal entity name. | HAPPY STORE SUPPLIES LTD. |
|
|
| Card Number | Masked account number. This field is used for all payment method account types (not just cards) if/when applicable. | 553312XX XXXX1234 |
|
|
| Merchant Reference | Arbitrary text provided by the merchant. | Free-text |
|
|
| Gateway Reference | Unique ID shared by partner processor. | Free-text |
|
|
| Remarks | Additional info on transaction (Optional). | Free-text |
|
|
| Interchange Amount | Fee due to the issuer of the card. Two decimal digits. Amounts are formatted using a dot (".") Amount is preceded with a (-) sign in instances where the amount has been deducted. |
200.50 (for a deduction) |
|
|
| Interchange Currency | Interchange fee currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| Pre-Authorization Amount | Fee due to the scheme for the usage of the pre-authorisation transaction (each pre-authorisation is billed). Two decimal digits. Amounts are formatted using a dot ("."). Amount is preceded with a (-) sign in instances where the amount has been deducted. |
100.50 (for a deduction) |
|
|
| Pre-Authorization Currency | Pre-authorisation scheme fee currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| Authorization Amount | Fee due to the scheme for the authorisation transaction. Two decimal digits. Amounts are formatted using a dot (".") Amount is preceded with a (-) sign in instances where the amount has been deducted. |
200.50 (for a deduction) |
|
|
| Authorization Currency | Authorisation scheme fee currency. Currency three letter code ISO 4217-Alpha 3. |
HKD |
|
|
| Three Ds Amount | Fee due to the scheme for the usage of 3D Secure authentication. Two decimal digits. Amounts are formatted using a dot (".") Amount is preceded with a (-) sign in instances where the amount has been deducted. |
342.50 (for a deduction) |
|
|
| Three Ds Currency | 3DS scheme fee currency. Currency three letter code ISO 4217-Alpha 3. |
HKD |
|
|
| Non Three Ds Amount | Fee is due to the scheme for insecure transaction, without usage of 3D Secure authentication. Two decimal digits. Amounts are formatted using a dot (".") Amount is preceded with a (-) sign in instances where the amount has been deducted. |
1100.50 (for a deduction) |
|
|
| Non Three Ds Currency | Non-3DS scheme fee currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| Cross Border Amount | Fee is due to the scheme for a transaction where the country of the merchant differs from the country of the issuer. Two decimal digits. Amounts are formatted using a dot (".") Amount is preceded with a (-) sign in instances where the amount has been deducted. |
900.50 (for a deduction) |
|
|
| Cross Border Currency | Cross border scheme fee currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| Cross Currency Amount | Fee due to the scheme for a transaction where the merchant country currency differs from the transaction currency. Two decimal digits. Amounts are formatted using a dot ("."). Amount is preceded with a (-) sign in instances where the amount has been deducted. |
1243.50 (for a deduction) |
|
|
| Cross Currency Currency | Cross currency scheme fee currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| Clearing Amount | Fee due to the scheme for each financial transaction initiated by the merchant (purchase and refund). Two decimal digits. Amounts are formatted using a dot (".") Amount is preceded with a (-) sign in instances where the amount has been deducted. |
300.50 (for a deduction) |
|
|
| Clearing Currency | Clearing scheme fee currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| Scheme Fee Bucket Amount | Sum of all the other scheme fees which cannot be otherwise categorised. Two decimal digits. Amounts are formatted using a dot (".") Amount is preceded with a (-) sign in instances where the amount has been deducted. |
12.50 (for a deduction) |
|
|
| Scheme Fee Bucket Currency | Scheme fee bucket currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| Payout ID | Unique identify of the payout wallet. | POW-012345678 912345 |
|
|
| Merchant ISO ID | Unique partner identifier assigned by during onboarding preceded by the PID identifier. | PID-123456789 |
NOTE: Field only applicable in the email version of the reports. |
|
| Gateway Fee Amount | Gateway fee amount. Two decimal digits. Amounts are formatted using a dot (".") Amount is preceded with a (-) sign in instances where the Gateway Fee has been deducted. It can be at transaction level or applied in lumpsum, for all gateway events of the previous day. |
13.67 (for a deduction) |
|
|
| Gateway Fee Currency | Gateway fee currency. Currency three letter code ISO 4217-Alpha 3. | HKD |
|
|
| Expected Funding Date | Date that Nomupay expects to fund the merchant’s nominated funding account. | YYYY-MM-DD |
|
|
| Order Description | Arbitrary text provided by the merchant. | Free-text |
|
|
| Merchant ISO ID | Unique partner identifier assigned by during onboarding preceded by the PID identifier. | PID-123456789 |
NOTE: Field only applicable in the SFTP version of the reports. |