Skip to main content

We've Launched a New Documentation Website (Beta Launch)

The documentation for DuitNow is now available on our newly launched documentation platform. This is an initial beta rollout of our new documentation site, designed to become the long-term home for all documentation moving forward.

You'll find the familiar content you're used to—now hosted on a new platform that will progressively receive updates and enhancements.

We encourage you to start accessing DuitNow materials there to explore the new experience and ensure you're viewing the latest documentation updates. If you have any feedback, please reach out to us.

Visit the New Documentation Website

Batch Files Processing

NoReport CodeDescriptionFile NamingFormatFile TypeFrequency
1.
RTPB001 – RTP Bank Request File Request file for Request-to-Pay via Proxy or Account Number
  • This file can only be used by Bank
  • Supported transaction codes are 851, 853 and 854
  • Participant is expected to perform Account Enquiry or Proxy Enquiry before generating the file to ensure information accuracy
  • Participant shall send records that are maintained the day before (T-1) only
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_RTPB001_SSSSSSSS_NNNNN
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number

Example: 20191122_HBMBMYKL_RTPB001_MERAMYKL_00001

TXTDelimited (Delimiter: Pipe – |)Daily – 12.30am
2.
RTPB001 – RTP Bank Return File Response file for Request-to-Pay via Proxy or Account Number
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_RTPB001_SSSSSSSS_NNNNN_R
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number
  • R – Return file indicator
Example: 20191122_HBMBMYKL_RTPB001_MERAMYKL_00001_R
TXTDelimited (Delimiter: Pipe – |)Daily – 08.00am
3.
RTPB002– RTP Merchant Request File Request file for Request-to-Pay via Proxy or Account Number
  • This file can only be used by Merchant
  • Supported transaction codes are 851, 853 and 854
  • Participant is expected to perform Account Enquiry or Proxy Enquiry before generating the file to ensure information accuracy
  • Participant shall send records that are maintained the day before (T-1) only
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_RTPB002_SSSSSSSS_NNNNN
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number
Example: 20191122_MERBMYKL_RTPB002_UniFiBil_00001
TXTDelimited (Delimiter: Pipe – |)Daily – 12.30am
4.
RTPB001 – RTP Merchant Return File Response file for Request-to-Pay via Proxy or Account Number
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_RTPB002_SSSSSSSS_NNNNN
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number
  • R – Return file indicator
Example: 20191122_MERBMYKL_RTPB002_UniFiBil_00001_R
TXTDelimited (Delimiter: Pipe – |)Daily – 08.00am
5.
CRB001 – Consent Registration Request File Request file for consent registration via Proxy or Account Number
  • This file can only be used by Bank or Merchant
  • Supported transaction codes are 801 and 802
  • Participant shall send records that are maintained the day before (T-1) only
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_CRB001_SSSSSSSS_NNNNN
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number
Example: 20191122_HBMBMYKL_CRB001_MERAMYKL_00001
TXTDelimited (Delimiter: Pipe – |)Daily – 12.30am
6.
CRB001 – Consent Registration Return File Response file for consent registration via Proxy or Account Number
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_CRB001_SSSSSSSS_NNNNN_R
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number
  • R – Return file indicator
Example: 20191122_HBMBMYKL_CRB001_MERAMYKL_00001
TXTDelimited (Delimiter: Pipe – |)Daily – 8.00am
7.
DDB001 – RTD Request File Request file for Real-time Debit
  • This file can only be used by Bank or Merchant
  • Supported transaction codes are 210 and 220
  • Participant shall send records that are maintained the day before (T-1) only
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_DDB001_SSSSSSSS_NNNNN
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number
Example: 20191122_HBMBMYKL_DDB001_MERAMYKL_00001
TXTDelimited (Delimiter: Pipe – |)Daily – 12.30am
8.
DDB001 – RTD Return File Response file for Real-time Debit
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_DDB001_SSSSSSSS_NNNNN
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number
  • R – Return file indicator
Example: 20191122_HBMBMYKL_DDB001_MERAMYKL_00001_R
TXTDelimited (Delimiter: Pipe – |)Daily – 08.00am
9.
DDB002 –RTD Request File Request file for Real-time Debit
  • This file can only be used by Merchant
  • Supported transaction code is 220
  • Participant shall send records that are maintained the day before (T-1) only
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_DDB001_SSSSSSSS_NNNNN
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number
Example: 20191122_TMMYMYKL_DDB002_UniFiBil_00001
TXTDelimited (Delimiter: Pipe – |)Daily – 12.30am
10.
DDB002 –RTD Return File Response file for Real-time Debit
  • On a daily basis, it is possible to receive and process a maximum of 99,999 files. Each of these files can hold up to 500 records
YYYYMMDD_BBBBBBBB_DDB001_SSSSSSSS_NNNNN
  • YYYYMMDD – Date
  • BBBBBBBB – Participant BIC
  • SSSSSSSS – Unique identifier used by each participant (e.g. to identify different merchants)
  • NNNNN – File sequence number
  • R – Return file indicator
Example: 20191122_TMMYMYKL_DDB002_UniFiBil_00001_R
TXTDelimited (Delimiter: Pipe – |)Daily – 08.00am