Skip to main content

Reporting Specifications

info

All reports shall be made available via the FI server. Participant that may require access to these reports shall apply the access credential through our administrator or Developer Portal.

Summary

Reports from RPP

Report CodeDescriptionNaming ConventionFormatFile TypeFrequencyStatus
PSR02Participant Settlement FileRPP_<BICFI>_PSR02_<yyyymmdd>_<cycle>TXTFixed-length2 cycles per dayActive
RPP_<BICFI>_PSR02_<yyyymmdd>_DAILYDaily
CBPSR02Cross Border Participant Settlement FileRPP_<BICFI>_CBPSR02_<yyyymmdd>_<cycle>TXTFixed-length2 cycles per dayActive
RPP_<BICFI>_CBPSR02_<yyyymmdd>_DAILYDaily
TAR02Transaction Daily FileRPP_<BICFI>_TAR02_<yyyymmdd>TXTDelimited by "|"DailyActive
CBTAR02Cross Border Transaction Daily FileRPP_<BICFI>_CBTAR02_<yyyymmdd>TXTDelimited by "|"DailyActive
TAR04Transaction Settlement Cycle FileRPP_<BICFI>_TAR04_<yyyymmdd>_<cycle>TXTDelimited by "|"2 cycles per dayActive
CBTAR04Cross Border Transaction Settlement Cycle FileRPP_<BICFI>_CBTAR04_<yyyymmdd>_<cycle>TXTDelimited by "|"2 cycles per dayActive
PFMR02Participant Fee Monthly FileRPP_<BICFI>_PFMR02_<yyyymmdd>TXTDelimited by "|"MonthlyActive
SRTR02SAF Rejected Transactions FileRPP_<BICFI>_SRTR02_<yyyymmdd>TXTDelimited by "|"DailyActive
SRTR04SAF Successful Transactions FileRPP_<BICFI>_SRTR04_<yyyymmdd>TXTDelimited by "|"DailyActive
SER02SAF Exception FileRPP_<BICFI>_SER02_<yyyymmdd>TXTDelimited by "|"DailyActive
NADM02NAD Maintenance FileRPP_<BICFI>_NADM02_<yyyymmdd>TXTDelimited by "|"DailyActive
NADM03NAD Deregistration Requests by ParticipantsRPP_<BICFI>_NADM03_<yyyymmdd_NN>
NN = Sequence Number e.g. 01,02...99
TXTDelimited by "|"Daily
(may be sent multiple times using sequence number)
Active
NUSR01NAD Usage Statistics ReportRPP_<BICFI>_NUSR01_<yyyymmdd>PDFDailyActive
MRR02Merchant Registration FileRPP_<BICFI>_MRR02_<yyyymmdd>TXTDelimited by "|"DailyActive
CMR02Consent Maintenance File (CMR02)RPP_<BICFI>_CMR02_<yyyymmdd>TXTDelimited by "|"DailyActive
CMR04Consent Maintenance File for Direct Debit (CMR04)RPP_<BICFI>_CMR04_<yyyymmdd>TXTDelimited by "|"DailyActive
CBSF02Service Fee for DuitNow Cross Border Fund Transfer (CBSF02)RPP_<BICFI>_CBSF02_<yyyymmdd>

RPP_PAYNET_<Settlement Bank/Switch>_CBSF02_<yyyymmdd>
TXTDelimited by "|"DailyActive

Reports from FIs

No.DescriptionNaming ConventionFormatFile TypeFrequencyStatus
1.On-Us Itemised Report<yyyymmdd><BICFI>01Data File (.txt)Delimited
(Delimiter: Pipe - |)
DailyActive
2.On-Us Summarised Report<yyyymmdd><BICFI>02Data File (.txt)Delimited
(Delimiter: Pipe - |)
MonthlyActive
3.QR Merchant Registration & Termination Report<yyyymmdd><BICFI>03Data File (.txt)Delimited
(Delimiter: Pipe - |)
MonthlyActive

Participant Settlement File (PSR02)

This is the RPP Settlement file generated for the Participants at each settlement cycle.

Layout

PSR02

PSR02 (Cycle)

Download sample file

PSR02 (Daily)

Download sample file

Fields

Header:

Field NameLengthDescription
RECORD TYPEPIC 9 (02)Value “01” to indicate HEADER record
REPORT DATEPIC X (08)Report Date in (yyyyMMdd) format. E.g. 20171023

Body:

Field NameLengthDescription
RECORD TYPEPIC 9 (02)Value “02” to indicate rejected transaction records for that cycle
SETTLEMENT CYCLEPIC 9 (02)Settlement Cycle Value. E.g. "001" or "002"
SERVICE TYPEPIC 9 (3)Business purpose of the transaction i.e. Credit Transfer, Payment Return etc. (E.g 011 – Reverse Credit Transfer)
TRANS VOLUME (DR)PIC 9 (18)Total volume of debited record count.
TRANS AMT (DR)PIC X (15)Transaction Debited Amount. This amount will be presented in 999999999999.99 format. For e.g. RM 1000.00 will be shown as 000000001000.00
TRANS VOLUME (CR)PIC 9 (18)Total volume of credited record count.
TRANS AMT (CR)PIC X (15)Transaction Credited Amount. This amount will be presented in 999999999999.99 format. For e.g. RM 1000.00 will be shown as 000000001000.00
DEBIT CREDITPIC X (2)This is the debit or credit for Nett Total amount. For e.g. CR is positive value while DR is negative value for Nett
NETT TOTALPIC X (15)NETT TOTAL PIC X (15) Nett Transaction Amount. This amount will be presented in 999999999999.99 format. For e.g. RM 1000.00 will be shown as 000000001000.00

Footer:

Field NameLengthDescription
RECORD TYPEPIC 9 (02)Value “03” to indicate FOOTER record
TOTAL RECORD COUNTPIC 9 (18)Total record count, excluding header and trailer records.

Cross Border Participant Settlement File (CBPSR02)

This is the RPP Settlement file generated for the Participants at each settlement cycle for Cross-Border transactions.

Layout

CBPSR02

CBPSR02 (Cycle)

Download sample file

CBPSR02 (Daily)

Download sample file


Fields

Header:

ColumnField NameDescriptionFormat
1Record TypeIndicate HEADER RecordValue “01”
Numeric (2)
2Report DateDate the report is generated<yyyyMMdd>
Numeric (8)

Body:

ColumnField NameDescriptionFormat
1Record TypeIndicate rejected transaction records for that cycleValue "02"
Numeric (2)
2Settlement CycleSettlement Cycle Value"001" or "002"
Numeric (3)
3Service TypeBusiness purpose of the transaction :
- 031 – Cross Border QR (POS)
Numeric (3)
4Currency CodeApplicable currency used in the transactionE.g. THB, SGD, IDR
Alphabet (3)
5Trans Volume (DR)Total volume of debited record count.Numeric (15)
6Trans Amt (DR)Total transaction debit amount in MYRPresented in 999999999999.99 format. Eg: RM 1000.00 will be shown as 000000001000.00
Decimal (15,2)
7Foreign Amount (DR)Total transaction debit amount in foreign currencyDecimal (15,2)
8Trans Volume (CR)Total volume of credited record countNumeric (15)
9Trans Amt (CR)Total transaction credit amount in MYRPresented in 999999999999.99 format. Eg: RM 1000.00 will be shown as 000000001000.00
Decimal (15,2)
10Foreign Amount (CR)Total transaction credit amount in foreign currencyDecimal (15,2)
11Debit CreditThis is the debit or credit for Nett Total amount. For e.g. CR is positive value while DR is negative value for Nett Total.Decimal (15,2)
12Nett TotalNett Transaction Amount in MYRPresented in 999999999999.99 format. Eg: RM 1000.00 will be shown as 000000001000.00
Decimal (15,2)

Footer:

ColumnField NameDescriptionFormat
1Record TypeIndicate FOOTER RecordValue “03”
Numeric (2)
2Total Record CountTotal record count, excluding header and trailer records.Numeric (15)

Participant Fee Monthly Report (PFMR01)

This is a monthy report generated to inform Participants of the fees incurred within the month.

Fields

ColumnField NameDescription
1TRANS DATETransaction Date
2SCHEMEFee Scheme ID
3OFI TRANS VOLUMETransaction Volume Initiated as OFI
4TRANS PRFProcessing Fee for OFI Transactions due to RPP
5TRANS CRFCapture Reimbursement Fee for OFI Transactions due to RPP
6CC TRANS VALUECredit Card Transaction Value for OFI Transactions
7CC FEECredit Card Transaction Fee for OFI Transactions due to RPP
8NAD VOLUMENAD Message Volume
9NAD FEENAD Message Fees
10TOTAL PAYABLE FEETotal Fee Due to RPP for OFI Transactions
11RFI TRANS VOLUMETransaction Volume Received as RFI
12TRANS CRFCapture Reimbursement Fee for RFI Transactions due from RPP
13CC TRANS VALUECredit Card Transaction Value as RFI
14CC FEECredit Card Transaction Fee for RFI Transactions due from RPP
15TOTAL RECEIVABLE FEETotal Fee Due from RPP for RFI Transactions
16NETT TOTALTOTAL RECEIVABLE FEE - TOTAL PAYABLE FEE

Participant Fee Monthly File (PFMR02)

This is the RPP Settlement file generated for the Participants at each settlement cycle for Cross-Border transactions.

Layout

PFMR02


Fields

Header:

ColumnField NameDescriptionFormat
1Record TypeIndicate HEADER RecordValue “01”
Numeric (2)
2Report DateDate the report is generated<yyyyMMdd>
Numeric (8)

Body:

ColumnField NameDescriptionFormat
1Record TypeIndicate Transaction recordsValue "02"
2SchemeFee Scheme ID
3Minimum Monthly Transaction Fee (RM)Minimum Monthly Transaction Fee (RM)Presented in 2 decimal places
4Ad Hoc FeeAd Hoc FeePresented in 2 decimal places
5Service TypeService Type
6On-Us Transaction (By Participant)On-Us Transaction Volume that Participant processed internally (volume and value for certain service type)
7On-Us Transaction (By RPP)On-Us Transaction Volume that RPP processed (volume and value for certain service type)
8Off-Us TransactionOff-Us Transaction Volume (outgoing/incoming and volume/value for certain service type)
9On-Us Transaction Processing FeeOn-Us Transaction Processing FeePresented in 2 decimal places
10Off-Us Transaction Processing FeeOff-Us Transaction Processing FeePresented in 2 decimal places
11Off-Us Transaction Capture Reimbursement FeeOff-Us Transaction Capture Reimbursement FeePresented in 2 decimal places
12Off-Us Transaction LOCAF FeeOff-Us Transaction LOCAF FeePresented in 2 decimal places
13Inquiry VolumeInquiry Volume
14Proxy Resolution FeeProxy Resolution FeePresented in 2 decimal places
15Total FeeTotal FeePresented in 2 decimal places
16Nett TotalNett TotalPresented in 2 decimal places
17MTDMonth-to-Date (from start until the end of the month)
18Transaction VolumeTotal numbers of industry transaction volume by service type within the month
19Transaction ValueTotal value of industry transaction by service type within the monthPresented in 2 decimal places

Footer:

ColumnField NameDescriptionFormat
1Record TypeIndicate FOOTER RecordValue “03”
Numeric (2)
2Total Record CountTotal record count, excluding header and trailer records.Numeric (15)

Transaction Daily File (TAR02)

This is a daily file generated that contains all the RPP transactions initiated by the Participants. This can be used by the Participants to reconcile transactions against the settlement amount.

Layout

TAR02

TAR02 Sample File

Download sample file


Fields

Header:

Field NameLengthDescription
RECORD TYPEPIC 9 (02)Value “01” to indicate Header record
REPORT DATEPIC X (08)Report Date in yyyyMMdd format. E.g. 20171023

Body:

Field NameLengthDescription
RECORD TYPEPIC 9 (02)Value “02” to indicate Transaction records
SETTLEMENT CYCLEPIC 9 (03)Settlement Cycle Value. E.g. "001" or "002"
INITIATION DATEPIC X (14)Date and time at which the transaction was created (yyyymmddhhmmss)
MSG IDPIC X (35)Transaction reference set by the Originator bank (OFI)
BUSINESS MSG IDPIC X (35)Business Message Id from the OFI
SERVICEPIC 9 (3)Business purpose of the transaction i.e. Credit Transfer, Payment Return etc. (E.g 011 – Reverse Credit Transfer)
SCHEME IDPIC X (8)Name of the scheme that manages a creditor or debtor of the non-participating bank to process their payments. Scheme has a direct relationship with the process
OFI CODEPIC X (8)Financial institution servicing an account for the debtor
OFI ACC NOPIC 9 (34)Debtor’s Account Number
OFI ACC TYPEPIC X (4)Debtor’s Account Type
OFI ACC NAMEPIC X (140)Debtor’s Name
RFI CODEPIC X (8)Financial institution servicing an account for the creditor
RFI ACC NOPIC 9 (34)Creditor Account Number
RFI ACC TYPEPIC X (4)Creditor’s Account Type
RFI ACC NAMEPIC X (140)Creditor Name
TRANS AMOUNTPIC X (15)Transaction Amount or Reversed Amount. This amount will be presented in 999999999999.99 format. For e.g. RM 1000.00 will be shown as 000000001000.00
TRANS STATUSPIC X (4)Status of the transaction
TRANS SUB CODEPIC X (4)Transaction's sub response code for Transactions under ACCEPTED status
COMPLETED DATEPIC X (14)Date and time at which the transaction was completed (yyyymmddhhmmss)

Footer:

Field NameLengthDescription
RECORD TYPEPIC 9 (02)Value “03” to indicate Footer record
TOTAL RECORD COUNTPIC 9 (18)Total record count, excluding header and trailer records.

Cross Border Transaction Daily File (CBTAR02)

This is a daily file generated that contains all the cross-border RPP transactions initiated by the Participants. This can be used by the Participants to reconcile transactions against the settlement amount.

Layout

CBTAR02

CBTAR02 Sample File

Download sample file


Fields

Header:

ColumnField NameDescriptionFormat
1Record TypeIndicate HEADER RecordValue “01”
Numeric (2)
2Report DateDate the report is generated<yyyyMMdd>
Numeric (8)

Body:

ColumnField NameDescriptionFormat
1Record TypeIndicate Transaction recordsValue "02"
Numeric (2)
2Settlement CycleSettlement Cycle Value"001" or "002"
Numeric (3)
3Initiation DateDate and time at which the transaction was created<yyyymmddhhmmss>
Numeric (14)
4Message IDTransaction reference set by the Originator bank (OFI)AlphaNumeric (35)
5Business Message IDBusiness Message Id from the OFIAlphaNumeric (35)
6Service TypeBusiness purpose of the transaction
i.e. 031 – Cross Border QR (POS)
Numeric(3)
7Scheme IdName of the scheme that manages a creditor or debtor of the non-participating bank to process their payments. Scheme has a direct relationship with the processAlphanumeric(3)
8OFI CodeFinancial institution servicing an account for the payerAlphanumeric (8)
9OFI Acct AccPayer’s Account NumberAlphanumeric (40)
10Acct TypePayer’s Account TypeAlphabet (4)
11Acct NamePayer’s NameFreeform (140)
12RFI CodeFinancial institution servicing an account for the merchantAlphanumeric (8)
13RFI Acct NoMerchant Account NumberAlphanumeric (40)
14Acct TypeCreditor’s Account TypeAlphabet (4)
15Acct NameCreditor NameFreeform (140)
16Trans AmountTransaction Amount in MYRDecimal (15,2)
17CurrencyTransaction CurrencyAlphabet (3)
18Foreign Amt.Transaction Amount in Foreign CurrencyDecimal (15,2)
19FX RateApplicable FX RatePresented in 4 – 6 decimals
20FX Ref. No.Ref. No. for FX Rate quotedNumeric (12)
21Trans StatusStatus of the transactionAlphabet (4)
22Trans Sub CodeTransaction's sub response code for TransactionsAlphanumeric (4)
23Completed DateDate and time at which the transaction was completed<yyyymmddhhmmss>
Numeric (14)
24Payment DescriptionParticipating Switch’s Transaction IDAlphanumeric (40)

Footer:

ColumnField NameDescriptionFormat
1Record TypeIndicate FOOTER RecordValue “03”
Numeric (2)
2Total Record CountTotal record count, excluding header and trailer records.Numeric (15)

Transaction Settlement Cycle File (TAR04)

This is a daily file generated that contains all the RPP transactions initiated by the Participants as well as received by the Participants.

Layout

TAR04

TAR04 Sample File

Download sample file


Fields

Header:

Field NameLengthDescription
Record TypePIC 9 (02)Value “01” to indicate HEADER record
Report DatePIC X (08)Report Date in yyyymmdd format. E.g. 20171023
Settlement CyclePIC 9 (03)Settlement Cycle Value. E.g. "001" or "002"

Body:

Field NameLengthDescription
Record TypePIC 9 (02)Value “02” to indicate Transaction records
Initiation DatePIC X (14)Date and time at which the transaction was created (yyyymmddhhmmss)
Message IdPIC X (35)Transaction reference set by the Originator bank (OFI)
Business Message IdPIC X (35)Business Message Id from the OFI
ServicePIC 9 (3)Business purpose of the transaction i.e. Credit Transfer, Payment Return etc. (E.g 011 – Reverse Credit Transfer)
Scheme IdPIC X (8)Name of the scheme that manages a creditor of the non-participating bank to process their payments. Scheme has a
(Creditor Bank)direct relationship with the process
OFI CodePIC X (8)Financial institution servicing an account for the debtor
OFI Account NumberPIC 9 (34)Debtor’s Account Number
OFI Account TypePIC X (4)Debtor’s Account Type
OFI Account NamePIC X (40)Debtor’s Name
RFI CodePIC X (8)Financial institution servicing an account for the creditor
RFI Account NumberPIC 9 (34)Creditor Account Number
RFI Account TypePIC X (4)Creditor’s Account Type
RFI Account NamePIC X (40)Creditor Name
Transaction AmountPIC X (15Transaction Amount or Reversed Amount. This amount will be presented in 999999999999.99 format. For e.g. RM1000.00 will be shown as 000000001000.00
Transaction StatusPIC X (4)Status of the transaction
Transaction Sub CodePIC X (4)Transaction's sub response code for Transactions under ACCEPTED status
Completed DatePIC X (14)Date and time at which the transaction was completed (yyyymmddhhmmss)

Footer:

Field NameLengthDescription
Record TypePIC 9 (02)Value “03” to indicate FOOTER record
Total Record CountPIC 9 (18)Total record count, excluding header and trailer records.

Cross Border Transaction Settlement Cycle (CBTAR04)

This is a daily file generated that contains all the cross-border transactions initiated by the Participants as well as received by the Participants.

Layout

CBTAR04

CBTAR04 Sample File

Download sample file

CBPSR02 (Daily)

Download sample file


Fields

Header:

ColumnField NameDescriptionFormat
1Record TypeIndicate HEADER RecordValue “01”
Numeric (2)
2Report DateDate the report is generated<yyyyMMdd>
Numeric (8)
3Settlement CycleSettlement Cycle Value"001" or "002"
Numeric (3)

Body:

ColumnField NameDescriptionFormat
1Record TypeIndicate Transaction recordsValue "02"
Numeric (2)
2Initiation DateDate and time at which the transaction was created<yyyymmddhhmmss>
Numeric (14)
3Message IDTransaction reference set by the Originator bank (OFI)AlphaNumeric (35)
4Business Message IDBusiness Message Id from the OFIAlphaNumeric (35)
5Service TypeBusiness purpose of the transaction
i.e. 031 – Cross Border QR (POS)
Numeric(3)
6Scheme IdName of the scheme that manages a creditor or debtor of the non-participating bank to process their payments. Scheme has a direct relationship with the processAlphanumeric(3)
7OFI CodeFinancial institution servicing an account for the payerAlphanumeric (8)
8OFI Acct AccPayer’s Account NumberAlphanumeric (40)
9Acct TypePayer’s Account TypeAlphabet (4)
10Acct NamePayer’s NameFreeform (140)
11RFI CodeFinancial institution servicing an account for the merchantAlphanumeric (8)
12RFI Acct NoMerchant Account NumberAlphanumeric (40)
13Acct TypeCreditor’s Account TypeAlphabet (4)
14Acct NameCreditor NameFreeform (140)
15Trans AmountTransaction Amount in MYRDecimal (15,2)
16CurrencyTransaction CurrencyAlphabet (3)
17Foreign Amt.Transaction Amount in Foreign CurrencyDecimal (15,2)
18FX RateApplicable FX RatePresented in 4 – 6 decimals
19FX Ref. No.Ref. No. for FX Rate quotedNumeric (12)
20Trans StatusStatus of the transactionAlphabet (4)
21Trans Sub CodeTransaction's sub response code for TransactionsAlphanumeric (4)
22Completed DateDate and time at which the transaction was completed<yyyymmddhhmmss>
Numeric (14)
23Payment DescriptionParticipating Switch’s Transaction IDAlphanumeric (40)

Footer:

ColumnField NameDescriptionFormat
1Record TypeIndicate FOOTER RecordValue “03”
Numeric (2)
2Total Record CountTotal record count, excluding header and trailer records.Numeric (15)

SAF Rejected Transactions File (SRTR02)

This report contains transactions that were rejected by the RFI during the store and forward process. These records will be extracted from the SAF table whose transaction status is RJCT. This will only include those transactions that were rejected outright by the RFI. It will not include those rejected transactions due to timeout.

Layout

SRTR02

SRTR02 Sample File

Download sample file

Fields

Header:

Field NameLengthDescription
Record TypePIC 9 (02)Value “01” to indicate HEADER record
Report DatePIC X (08)Report Date in (yyyyMMdd) format. E.g. 20171023

Body:

Field NameLengthDescription
Record TypePIC 9 (02)Value “02” to indicate rejected transaction records for that cycle
Initiation DatePIC X (14)Date and time at which the transaction was created (yyyymmddhhmmss)
Message IDPIC X (35)Transaction reference set by the Originator bank (OFI)
Business Message IdPIC X (35)Business Message Id from the OFI
ServicePIC 9 (3)Business purpose of the transaction i.e. Credit Transfer, Payment Return etc. (E.g 011 – Reverse Credit Transfer)
Scheme Id(Creditor Bank)PIC X (8)Name of the scheme that manages a creditor of the non-participating bank to process their payments. Scheme has adirect relationship with the process
OFI CodePIC X (8)Financial institution servicing an account for the debtor
OFI Account IdPIC 9 (34)Debtor’s Account Number
OFI Account TypePIC X (4)Debtor’s Account Type
OFI NamePIC X (40)Debtor’s Name
RFI CodePIC X (8)Financial institution servicing an account for the creditor
RFI Account IdPIC X (35)Creditor Account Number
RFI Account TypePIC X (4)Creditor’s Account Type
RFI NamePIC X (40)Creditor’s Name
Transaction AmountPIC X (15)Transaction Amount or Reversed Amount. This amount will be presented in 999999999999.99 format.

Footer:

Field NameLengthDescription
Record TypePIC 9 (02)Value “03” to indicate FOOTER record
Total Record CountPIC 9 (18)Total record count, excluding header and trailer records

SAF Successful Transactions File (SRTR04)

This report contains transactions that were successful accepted by the RFI during the store and forward process.

Layout

SRTR04

SRTR04 Sample File

Download sample file


Fields

Header:

Field NameLengthDescription
Record TypePIC 9 (02)Value “01” to indicate HEADER record
Report DatePIC X (08)Report Date in (yyyyMMdd) format. E.g. 20171023

Body:

Field NameLengthDescription
Record TypePIC 9 (02)Value “02” to indicate rejected transaction records for that cycle
Initiation DatePIC X (14)Date and time at which the transaction was created (yyyymmddhhmmss)
Message IDPIC X (35)Transaction reference set by the Originator bank (OFI)
Business Message IdPIC X (35)Business Message Id from the OFI
ServicePIC 9 (3)Business purpose of the transaction i.e. Credit Transfer, Payment Return etc. (E.g 011 – Reverse Credit Transfer)
Scheme Id(Creditor Bank)PIC X (8)Name of the scheme that manages a creditor of the non-participating bank to process their payments. Scheme has adirect relationship with the process
OFI CodePIC X (8)Financial institution servicing an account for the debtor
OFI Account IdPIC 9 (34)Debtor’s Account Number
OFI Account TypePIC X (4)Debtor’s Account Type
OFI NamePIC X (40)Debtor’s Name
RFI CodePIC X (8)Financial institution servicing an account for the creditor
RFI Account IdPIC X (35)Creditor Account Number
RFI Account TypePIC X (4)Creditor’s Account Type
RFI NamePIC X (40)Creditor’s Name
Transaction AmountPIC X (15)Transaction Amount or Reversed Amount. This amount will be presented in 999999999999.99 format.

Footer:

Field NameLengthDescription
Record TypePIC 9 (02)Value “03” to indicate FOOTER record
Total Record CountPIC 9 (18)Total record count, excluding header and trailer records

NAD Maintenance File (NADM02)

This file contains all the NAD transactions initiated by the Participant within the day.

Layout

NADM02

NADM02 Sample File

Download sample file

Fields

Header:

Field NameDescriptionFormat
Record TypeTo indicate HEADER recordValue “01”
Report DateThe Date the Report is generated foryyyyMMdd

Body:

Field NameDescriptionFormat
Record TypeIndicate maintained NAD records for that dayValue “02”
Business Message IDBusiness Message Id from the OFIyyyymmddhhmmss
OFI BIC CodeBIC Code of OFI
Maintenance TypeType of maintenance that was carried out on the NAD proxy record
Proxy TypeType of proxy record being maintained
Proxy IDValue being set as the Proxy IDRevel Account Detail (Clear Text)
Secondary ID TypeType of Secondary ID record used
SECONDARY IDCustomer's secondary ID value being setRevel Account Detail (Clear Text)
Bank CodeBIC Code of Account Holder Bank
Account NumberAccount number being tagged to the proxy record
Account TypeAccount Type being tagged to the proxy record
Account NameAccount name being tagged to the proxy record
Registration IDUnique ID to represent the NAD proxy record
Completion DateDate of transactionyyyyMMdd

Footer:

Field NameDescriptionFormat
Record TypeIndicate FOOTER recordValue “03”
Total Record CountTotal record count, excluding header and trailer records

NAD Deregistration Requests by Participants (NADM03)

The file is used to deregister the proxy or proxies for a Secondary ID from the NAD in case the proxy or Seconday ID of the Customer has changed. It is submitted by the Participants to PayNet daily and contains all Customer’s proxies or Secondary IDs that have been updated. PayNet will use this file to deregister the Participant’s Customers’ proxy or proxies for a Secondary ID.

Layout

NADM03

NADM03 Sample File

Download sample file

Fields

Header:

Field NameDescriptionFormat
Record TypeTo indicate HEADER recordValue “01”
Report DateThe Date the Report is generated foryyyyMMdd

Body:

Field NameDescriptionFormat
Record TypeIndicate Transaction recordsValue “02”
Maintenance TypeType of maintenance that was carried out on the NAD proxy recordDefault to "DEAC"
Proxy TypeType of proxy record being maintainedValid values NRIC, PSPT, BREG, MBNO, ALL . “ALL” shall be used if Secondary ID is updated.
Proxy IDValue being set as the proxy IDCustomer's old proxy that was changed. “ALL” shall be used if Secondary ID is updated.
Secondary ID TypeType of secondary ID record usedValid values NRIC, PSPT, BREG, MBNO
Secondary IDCustomer's unique ID tied to their accounts. Possible values are:
  • NRIC (without hyphens)
  • Passport Number (include Country of Issuance)
  • Business Registration Number (without hyphens)

Passport Number: Follow with the ALPHA-3 country code of the country of issuance. e.g. E394029340VSGP

Refer to this list for the ALPHA-3 Country codes

Mobile Number : (International Dialling Code preceding with '+') plus (up to 15 digits Mobile Number) *include the full mobile number (including country code/area code) in the field. e.g. +60104940394

Refer to this list for the International dialling country codes

Footer:

Field NameDescriptionFormat
Record TypeIndicate FOOTER recordValue “03”
Total Record CountTotal record count, excluding header and trailer records

NAD Usage Statistics Report (NUSR01)

NAD Usage Statistics Report contains reports on proxy administration and usage per channel and customer types. This report will be generated per Participant.

Layout

NUSR01

NUSR01 Sample Report

Download sample file

Fields

Report Header:

ColumnField NameDescription
1Report NameName of the Report
2Report DateDate the report is generated
3Participant IDBIC Code of the Bank

Report Body:

ColumnField NameDescription
1Customer TypeCustomer Type (E.g. Retail or Corporate)
2ChannelChannel Name (E.g. Internet Banking, Mobile Banking etc)
3No of Look-Ups RequestedThe number of Look-Ups requested
4No of Look-Ups RespondedThe number of Look-Ups performed where the recipient is the Participant's customer(s)
5Successful RegistrationThe number of successful registrations (new)
6Unsuccessful RegistrationThe number of unsuccessful registrations (new)
7DeregistrationThe number of deactivated registrations

Report Footer:

ColumnField NameDescription
1Active DuitNow NADTotal active DuitNow NAD
2Inactive DuitNow NADTotal inactive DuitNow NAD

SAF Exception File (SER02)

SAF Exception File contains all those transactions that have not been cleared from SAF. Reasons for the exception can be any of the following:

  • Timeout in RPP when sending SAF transactions
  • RFI is inactive so SAF transactions cannot be sent

Layout

SER02

SER02 Sample File

Download sample file

Fields

Header:

Field NameLengthDescription
Record TypePIC 9 (02)Value “01” to indicate HEADER record
Report DatePIC X (08)Report Date in (yyyyMMdd) format. E.g. 20171023

Body:

Field NameLengthDescription
RECORD TYPEPIC 9 (02)Value “02” to indicate Transaction records
SETTLEMENT CYCLEPIC 9 (03)Settlement Cycle Value. E.g. "001" or "002"
INITIATION DATEPIC X (14)Date and time at which the transaction was created (yyyymmddhhmmss)
MSG IDPIC X (35)Transaction reference set by the Originator bank (OFI)
BUSINESS MSG IDPIC X (35)Business Message Id from the OFI
SERVICEPIC 9 (3)Business purpose of the transaction i.e. Credit Transfer, Payment Return etc. (E.g 011 – Reverse Credit Transfer)
SCHEME IDPIC X (8)Name of the scheme that manages a creditor or debtor of the non-participating bank to process their payments. Scheme has a direct relationship with the process
OFI CODEPIC X (8)Financial institution servicing an account for the debtor
OFI ACC NOPIC 9 (34)Debtor’s Account Number
OFI ACC TYPEPIC X (4)Debtor’s Account Type
OFI ACC NAMEPIC X (40)Debtor’s Name
RFI CODEPIC X (8)Financial institution servicing an account for the creditor
RFI ACC NOPIC 9 (34)Creditor Account Number
RFI ACC TYPEPIC X (4)Creditor’s Account Type
RFI ACC NAMEPIC X (40)Creditor Name
TRANS AMOUNTPIC X (15)Transaction Amount or Reversed Amount. This amount will be presented in 999999999999.99 format. For e.g. RM 1000.00 will be shown as 000000001000.00

Footer:

Field NameLengthDescription
Record TypePIC 9 (02)Value “03” to indicate FOOTER record
Total Record CountPIC 9 (18)Total record count, excluding header and trailer records.

Merchant Registration File (MRR02)

This file contains the merchant acquired by Participants.

Layout

MRR02

MRR02 Sample File

Download sample file

Fields

Header:

Field NameDescription
Record TypeValue “01” to indicate HEADER record
Report DateDate the Report generated for in format (yyyyMMdd)

Body:

Field NameDescription
Record TypeValue “02” to indicate Transaction records
Merchant NameMerchant Name
BRN No.Merchant’s Business Registration Number
SegmentMerchant's Segment
SectorMerchant Business Sector
Business CategoryMerchant’s Business Category
Merchant IDMerchant ID
Product IDProduct ID
Product NameName of Product
Acquiring BankMerchant's Acquiring Bank
Registered ServicePaynet's Service(s) that the Merchant is registered
Request Submission DateDate the Registration Request is submitted
Requested Go Live DateThe date that the service would go live for the merchant, as request by the merchant

Footer:

Field NameDescription
Record TypeValue “03” to indicate FOOTER record
Total Record CountTotal record count, excluding header and trailer records

This file contains all the Consent transactions initiated by the Participant within the day.

Layout:

CMR02

Fields:

Header:

ColumnField NameDescriptionFormat
1Record TypeValue “01” to indicate HEADER record
2Report DateReport Date in yyyyMMdd format. E.g. 20171023<yyyyMMdd>

Body:

ColumnField NameDescriptionFormat
1Record Typeto indicate Registration recordsValue “02”
2Message IDTransaction reference set by the OFI
3Business Message IDBusiness Message ID from OFI
4OFI CodeBIC Code of OFI
5Maintenance TypeType of maintenance that was carried out on the Consent
  • New Registration (803, 813, 822, 823)
  • Edit (761)
  • Transfer (762)
  • Terminate (763, 764)
6Consent IDID of consent being maintained
7Merchant IDMerchant ID tagged
8Product IDProduct ID tagged
9Secondary Id TypeType of Secondary Id record used
10Secondary IdSecondary ID being tagged to the consentAccount Detail (Clear Text)
11Debtor BICDebiting Bank of the consent.
12Account TypeDebiting account type of the consent
13Debiting AccountDebiting account of the consentClear Text
14Debiting Account NameDebiting account name
15Consent AmountMaximum debiting amountPresented in 999999999999.99 format.
Eg: RM 1000.00 will be shown as 000000001000.00
16Consent FrequencyConsent frequency
  • 01="Unlimited
  • 02="Daily
  • 03="Weekly"
  • 04="Monthly"
  • 05="Quarterly"
  • 06="Yearly"
17Consent ExpiryExpiry date of consent<yyyyMMdd>
18Creditor BICCrediting Participant of the consent

Footer:

ColumnField NameDescriptionFormat
1Record TypeValue '03' to indicate FOOTER record
2Total Record CountTotal record count, excluding header and trailer records

This file contains all the Consent transactions initiated by the Participant within the day.

Layout:

CMR04

Fields:

Header:

ColumnField NameDescriptionFormat
1Record TypeValue “01” to indicate HEADER record
2Report DateReport Date in yyyyMMdd format. E.g. 20171023<yyyyMMdd>

Body:

ColumnField NameDescriptionFormat
1Record Typeto indicate Registration recordsValue “02”
2Message IDTransaction reference set by the OFI
3Business Message IDBusiness Message ID from OFI
4OFI CodeBIC Code of OFI
5Maintenance TypeType of maintenance that was carried out on the Consent (802)
6Consent IDID of consent being maintained
7Merchant IDMerchant ID tagged
8Product IDProduct ID tagged
9Secondary Id TypeType of Secondary Id record used
10Secondary IdSecondary ID being tagged to the consentAccount Detail (Clear Text)
11Debtor BICDebiting Bank of the consent.
12Account TypeDebiting account type of the consent
13Debiting AccountDebiting account of the consentClear Text
14Debiting Account NameDebiting account name
15Consent AmountMaximum debiting amountPresented in 999999999999.99 format.
Eg: RM 1000.00 will be shown as 000000001000.00
16Consent FrequencyConsent frequency
  • 01="Unlimited
  • 02="Daily
  • 03="Weekly"
  • 04="Monthly"
  • 05="Quarterly"
  • 06="Yearly"
17Consent ExpiryExpiry date of consent<yyyyMMdd>
18Creditor BICCrediting Participant of the consent
19Reference IDDirect Debit Mandate Payment Reference number

Footer:

ColumnField NameDescriptionFormat
1Record TypeValue "03" to indicate FOOTER record
2Total Record CountTotal record count, excluding header and trailer records

Service Fee for DuitNow Cross Border Fund Transfer (CBSF02)

This file contains the service fee for DuitNow Cross Border Fund Transfer transactions initiated by the Participant within the day.

Layout:

CBSF02

Fields:

Header:

ColumnField NameDescriptionFormat
1Record TypeValue “01” to indicate HEADER recordValue “01”
2Report DateReport Date in yyyyMMdd format. E.g. 20240216<yyyyMMdd>

Body:

ColumnField NameDescriptionFormat
1Record TypeTo indicate service fee recordsValue “02”
2Service TypeService type for transaction (111)
3OFI CodeBIC Code of OFI
4RFI CodeBIC Code of RFI
5FX RateFX rate value
6Service Fee ChargedService fee charged value:

Remmitance flowService fee value
Outbound transaction (Malaysia remit to Singapore)SGD 1.00
Inbound transaction (Singapore remit to Malaysia)MYR 3.50


*Service fee value will be fixed value
7Transaction CountTotal count of successful transaction
8Total Service FeeValue of (Service Fee * Transaction Count)
9Total Transaction Value - SGDTotal transaction value in SGD
10Total Transaction Value - MYRTotal transaction value in MYR

Footer:

ColumnField NameDescriptionFormat
1Record TypeValue "03" to indicate FOOTER recordValue “03”
2Total Record CountTotal record count, excluding header and trailer records

On-Us Report

This is the On-Us report generated by the FI that should contain all the transactions triggered through RPP.

Itemised Report

The itemised On-Us report should be submitted before 10AM daily for transactions from the previous day.

Layout

On-Us Itemised

Fields

Header:

Field NameLengthDescription
Record TypePIC 9 (2)Value “01” to indicate HEADER record
Report DatePIC X (8)Report Generation Date in yyyyMMdd format. E.g. 20171023
ORI CodePIC X (8)Financial institution servicing an account for the debtor/creditor
Total Record CountPIC 9 (18)Total record count, excluding header and trailer records.

Body:

Field NameLengthDescription
Record TypePIC 9 (2)Value “02” to indicate Transaction records
Initiation DatePIC X (14)Date and time at which the transaction was created (yyyyMMddHHmmss)
Message Id (MsgId)PIC X (35)Transaction reference set by the Originator bank (OFI)
Business Message Id (BizMsgId)PIC X (35)Business Message Id from the OFI
ServicePIC 9 (3)Business purpose of the transaction i.e. Credit Transfer, QR transaction, Payment Return etc. (E.g 011 – Reverse Credit Transfer)
Scheme Id(Creditor Bank)PIC X (8)Name of the scheme that manages a creditor of the non-participating bank to process their payments. Scheme has a direct relationship with the process
OFI BankPIC X (8)ORI Bank Code
OFI Customer typePIC X (1)Individual or Business. R: Retail C: Corporate
OFI Account NumberPIC 9 (34)Debtor’s Account Number
OFI Account TypePIC X (4)Debtor’s Account Type
OFI Account NamePIC X (140)Debtor’s Name
RFI BankPIC X (8)RFI Bank Code
RFI Customer TypePIC X (1)Individual or Business. R: Retail, C: Corporate
RFI Account NumberPIC 9 (34)Creditor Account Number
RFI Account TypePIC X (4)Creditor’s Account Type. Valid value: CACC, LOAN, SVGS, CCRD
RFI Account NamePIC X (140)Creditor Name
Transaction AmountPIC X (15)Transaction Amount or Reversed Amount. This amount will be presented in 999999999999.99 format. For e.g. RM 1000.00 will be shown as 000000001000.00
Proxy TypePIC X (4)Mobile, NRIC, Army/Police Number, Passport or Business Registration Number. Valid value: NRIC, ARMN, MBNO, BREG, PSPT
Proxy ValuePIC X (140)Variable
Proxy Registration IDPICX (35)Proxy unique registration id
Transaction StatusPIC X (4)Status of the transaction. Valid value: ACSP, RJCT
Transaction Reason CodePIC X (4)Transaction reason code for Transactions under ACCEPTED status(e.g. U000-Success/ Transaction accepted, U110-Payment not accepted, U804-Alias Not Found)
Transfer ChannelPIC X (2)Mobile / ATM / IB. RM: Retail Mobile Banking, CM: Corporate Mobile Banking, CB: Corporate Internet Banking, RB: Retail Internet Banking, OT: Other
Future Dated FlagPIC X (1)To indicate if this is a future dated transaction, Y/N
Completed DatePIC X (14)Date and time at which the transaction was completed (yyyyMMddHHmmss)
On-us / Off usPIC X (2)To indicate if this is on-us or off-us transaction. 01: On-us 02: Off-us

Summarised Report

The summarised On-Us report should be submitted before 10AM on the first (1st) day of the following month for the transactions from the previous month.

Layout

On-Us Summarised

Fields

Header:

Field NameLengthDescription
Record TypePIC 9 (2)Value “01” to indicate HEADER record
Report DatePIC X (8)Report Generation Date in yyyyMMdd format. E.g. 20171023
ORI CodePIC X (8)Financial institution servicing an account for the debtor/creditor
Total Record CountPIC 9 (18)Total record count, excluding header and trailer records.

Body:

Field NameLengthDescription
Record TypePIC 9 (2)Value “02” to indicate Transaction records
Transaction TypePIC X (3)Type of the transaction. 010 – CT, 110 – DuitNow, 011 – Reversal, 030 – QR Merchant, 040 – QR P2P
Transaction StatusPIC X (4)Status of the transaction. Valid value: ACSP, RJCT
Total Transaction CountPIC 9 (18)Total transaction count
Total Transaction AmountPIC X (18)Transaction Amount or Reversed Amount. This amount will be presented in 999999999999999.99 format. For e.g. RM 1000.00 will be shown as 000000000001000.00

QR Merchant Registration & Termination Report

This is a monthly report to be generated by Participants in text format to inform PayNet on the itemized QR Merchant registration and termination record by the Participant.

Layout:

QR Merchant Registration and Termination Report

Fields:

Header:

Field NameDescription
Record TypeValue “01” to indicate HEADER record
Report DateReport Date in yyyyMMdd format. E.g. 20171023
Total Record CountTotal record count, excluding header and trailer records.

Body:

Field NameDescription
Record TypeValue “02” to indicate Registration records
Acquirer ParticipantAcquirer Participant’s BIC Code
Registration DateDate and time at which the Merchant registration was submitted (yyyyMMddHHmmss)
Approval DateDate and time at which the Merchant registration was approved. If not applicable, to be the same as Registration date. (yyyyMMddHHmmss)
Effective DateDate and time at which the Merchant start receiving payments via DuitNow QR. If not applicable, to be the same as Approval date. (yyyyMMddHHmmss)
Collection Account ParticipantParticipant’s BIC Code where Merchant collection account is maintained. If same as Acquirer Participant, use Acquirer Participant BIC Code.
Merchant NameMerchant Company Name. This should be same as in the QR Code.
QR IDMerchant QR ID. This should be same as in the QR Code.
Merchant Category Code (MCC)Defined by ISO18245. This should be same as in the QR Code.
Merchant Acceptable Source of FundMerchant acceptable source of fund. Valid values: CACC, SVGS, CCRD, WALL.
Dynamic QRDynamic QR Status: Y/N
Services SubscribedServices that Merchant will be using. Valid values: 030, 240, 250, 032.
Business Registration NumberMerchant’s business registration number.
Mobile NumberMerchant’s mobile number. Please include country code.
StatusStatus of Merchant. Valid values: REG (Registration), TER (Termination)
ReasonOnly applicable if Status = TER. Reason description for terminated merchant

FI Server Paths

DescriptionPath

This is where Participants upload the reports, e.g.:

  • On-us transaction report
  • Merchant registration report

SIT: <BICCODE>/RPP/<mmm>/inbound_sit/onus/<report or file name>

UAT: <BICCODE>/RPP/<mmm>/inbound_uat/onus/<report or file name>

PROD: <BICCODE>/RPP/<mmm>/inbound/onus/<report or file name>

This is where Participants upload the batch files, e.g.:

  • RTP batch file
  • Consent batch file
  • RTD batch file

SIT: <BICCODE>/RPP/<mmm>/inbound_sit/batchfile/<report or file name>

UAT: <BICCODE>/RPP/<mmm>/inbound_uat/batchfile/<report or file name>

PROD: <BICCODE>/RPP/<mmm>/inbound/batchfile/<report or file name>

This is where Participants upload the QR Merchant Registration report

SIT: <BICCODE>/RPP/<mmm>/inbound_sit/QR_reg/<report or file name>

UAT: <BICCODE>/RPP/<mmm>/inbound_uat/QR_reg/<report or file name>

PROD: <BICCODE>/RPP/<mmm>/inbound/QR_reg/<report or file name>

This is where Participants download the phase-1 reports from RPP, e.g.:

  • Transaction reports
  • SAF reports
  • Settlement reports

SIT: <BICCODE>/RPP/<mmm>/outbound_sit/<yy-mm-dd>/<report or file name>

UAT: <BICCODE>/RPP/<mmm>/outbound_uat/<yy-mm-dd>/<report or file name>

PROD: <BICCODE>/RPP/<mmm>/outbound/<yy-mm-dd>/<report or file name>

This is where Participants download the reports from RPP, e.g.:

  • Transaction reports
  • SAF reports
  • Settlement reports
  • Request-to-Pay reports
  • Consent reports

SIT: <BICCODE>/RPP/<mmm>/outbound_p2_sit/<yy-mm-dd>/<report or file name>

UAT: <BICCODE>/RPP/<mmm>/outbound_p2_uat/<yy-mm-dd>/<report or file name>

PROD: <BICCODE>/RPP/<mmm>/outbound/<yy-mm-dd>/<report or file name>

This is where Participants download the batch file results, e.g.:

  • RTP batch result file
  • Consent batch result file
  • RTD batch result file

SIT: <BICCODE>/RPP/<mmm>/outbound_sit/batchfile_return/<report or file name>

UAT: <BICCODE>/RPP/<mmm>/outbound_uat/batchfile_return/<report or file name>

PROD: <BICCODE>/RPP/<mmm>/outbound/batchfile_return/<report or file name>