Skip to main content

DuitNow QR (Foreign Switch as Issuer)

1. QR Account Enquiry

Test IDDescriptionTest DataExpected Result
QRTC#001Issuer to RPP: Field Value Validation
(Positive)
Issuer sends an AE request to RPP with Debtor Account Type whichever applicable for Point of Initiation Method = 11 (Static QR)

Accepts the following values:
  • CACC - Current Account
  • SVGS - Savings Account
  • WALL - eWallet
  • DFLT - either Current or Savings
Acquirer responds with a successful AE response:
  • ACSP 00

Issuer receives successful transaction:
  • ACSP U000
  • Category returned = 01 (Point of Sales)
QRTC#002Issuer to RPP: Field Value Validation
(Positive)
Issuer sends an AE request to RPP with Debtor Account Type whichever applicable for Point of Initiation Method = 12 (Dynamic QR)

Amount in QR: Numeric only (i.e. 10)

Accepts the following values:
  • CACC - Current Account
  • SVGS - Savings Account
  • WALL - eWallet
  • DFLT - either Current or Savings
Acquirer responds with a successful AE response:
  • ACSP 00
Issuer receives successful transaction:
  • ACSP U000
  • Category returned = 01 (Point of Sales)
QRTC#003Issuer to RPP: Field Value Validation
(Positive)
Issuer sends an AE request to RPP with Debtor Account Type whichever applicable for Point of Initiation Method = 12 (Dynamic QR)

Amount in QR: Numeric and decimal (i.e. 10.00)

Accepts the following values:
  • CACC - Current Account
  • SVGS - Savings Account
  • WALL - eWallet
  • DFLT - either Current or Savings
Acquirer responds with a successful AE response:
  • ACSP 00

Issuer receives successful transaction:
  • ACSP U000
  • Category returned = 01 (Point of Sales)
QRTC#004Issuer to RPP: Whitelisted Special Characters
(Positive)
Issuer bank sends an AE request with whitelisted special characters in the Debtor Name

Field Type: NameSplChars
List Value: [A-Za-z0-9 @'/&()._-,\`*]:#+!";$%^{}~
Acquirer responds with a successful AE response:
  • ACSP 00

Issuer receives successful transaction:
  • ACSP U000
QRTC#005Issuer to RPP: Whitelisted Special Characters
(Positive)
Issuer bank sends an AE request with whitelisted special characters in the Merchant Name/Creditor Name

Field Type: NameSplChars
List Value: [A-Za-z0-9 @'/&()._-,\`*]:#+!";$%^{}~

NOTE:
Issuer should send the XML escape characters of the above special characters. Otherwise, txn will be rejected
Acquirer responds with a successful AE response:
  • ACSP 00

Issuer receives successful transaction:
  • ACSP U000
QRTC#006Issuer to RPP: Field Value Validation
(Positive)
Issuer bank sends an AE request with QR String contains value 0000 in MCC Field
Acquirer responds with a successful AE response:
  • ACSP 00

Issuer receives successful transaction:
  • ACSP U000
QRTC#007Issuer to RPP: Account Status Validation
(Negative)
Issuer sends an AE request but rejected:
  • Beneficiary Account is dormant
  • Beneficiary Account is invalid
  • Beneficiary Account is closed
  • Beneficiary Account is blaclisted
  • Beneficiary Account is on hold or blocked
  • Beneficiary is deceased
Acquirer responds with a negative response:
  • RJCT 45
Issuer receives a negative response:
  • RJCT 45

QRTC#008Issuer to RPP: Expired QR
(Negative)
Issuer sends an AE request but rejected
  • QR expired
Expiry time for MY Participants as below
  • Public Bank Berhad (PBBEMYKL) : 60s
  • Razer Merchant Services Sdn Bhd (RZMSMYNB) : 60s
  • United Overseas Bank Berhad (UOVBMYKL) : 60s
  • Axiata Digital eCode Sdn Bhd (BOSTMYNB) : 60s
  • FINEXUS CARDS Sdn Bhd (FNXSMYNB) : 5m
  • Maybank Berhad (MBBEMYKL) : 60s
  • CIMB Bank Berhad (CIBBMYKL) : 2h
  • Hong Leong Bank Berhad (HLBBMYKL) : 60s
  • Ambank Malaysia Berhad (ARBKMYKL) : 60s
  • TNG Digital Sdn Bhd (TNGDMYNB) : 60s
  • OCBC Bank Berhad (OCBCMYKL) : 15m
  • Bank Islam Malaysia Berhad (BIMBMYKL) : 60s
Acquirer responds with a negative response:
  • RJCT 48

Issuer receives a negative response:
  • RJCT 48
QRTC#009Issuer to RPP: QR Merchant Status Validation
(Negative)
Issuer sends an AE request but rejected
  • Merchant Inactive / Suspended / Terminated
Acquirer responds with a negative response:
  • RJCT 49

Issuer receives a negative response:
  • RJCT 49
QRTC#010Issuer to RPP: Account Number Validation
(Negative)
Issuer sends an AE request but rejected
  • Account does not exist or invalid
Acquirer responds with a negative response:
  • RJCT 52 / RJCT 53 / RJCT N3

Issuer receives a negative response:
  • RJCT 52 / RJCT 53 / RJCT N3

2. QR Credit Transfer

Test IDDescriptionTest DataExpected Result
QMTC#001QR Pay to Merchant (POS): Field Value Validation
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request using Static QR by input the amount: Numeric only (i.e. 1)
Successful Transaction
Acquirer responds with a successful CT response:
  • ACSP 00

Issuer receives successful transaction
  • ACSP U000
QMTC#002QR Pay to Merchant (POS): Field Value Validation
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request using Static QR by input the amount: Numeric and Decimal (i.e. 1.20)
Successful Transaction
Acquirer responds with a successful CT response:
  • ACSP 00

Issuer receives successful transaction
  • ACSP U000
QMTC#003QR Pay to Merchant (POS): Field Value Validation
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request with Dynamic QR by populating the value based on the amount from AE response. Amount in QR: Numeric only (i.e. 1)
Successful Transaction
Acquirer responds with a successful CT response:
  • ACSP 00

Issuer receives successful transaction
  • ACSP U000
QMTC#004QR Pay to Merchant (POS): Field Value Validation
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request with Dynamic QR by populating the value based on the amount from AE response. Amount in QR: Numeric and Decimal (i.e. 1.20)
Successful Transaction
Acquirer responds with a successful CT response:
  • ACSP 00

Issuer receives successful transaction
  • ACSP U000
QMTC#005QR Pay to Merchant (POS): Timeout
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request but no response
Transaction accepted - Timeout
Acquirer does not send any response

Issuer receives success / transaction accepted stored in SAF
  • ACTC U002
  • Issuer to check the final response in the next day report : SER - Where SER = SAF EXCEPTION REPORT
QMTC#006QR Pay to Merchant (POS): Timeout
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request but no response
Transaction accepted - Timeout
Acquirer send successful response during SAF retry

Issuer receives success / transaction accepted stored in SAF
  • ACTC U002
  • Issuer to check the final response in the next day report : SRTR03 and SRTR04 - Where SRTR = SAF SUCCESSFUL TRANSACTION REPORT
QMTC#007QR Pay to Merchant (POS): Timeout
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request but no response
Transaction accepted - Timeout
Acquirer send rejected response during SAF retry

Issuer receives success / transaction accepted stored in SAF
  • ACTC U002
  • Issuer to check the final response in the next day report : SRTR01 and SRTR02- Where SRTR = SAF REJECTED TRANSACTION REPORT
QMTC#008QR Pay to Merchant (POS): Whitelisted Special Characters
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer bank sends CT request with whitelisted special characters in the Debtor Name

Field Type: NameSplChars
List Value: [A-Za-z0-9 @'/&()._-,\`*]:#+!";$%^{}~

NOTE:
Issuer should send the XML escape characters of the above special characters. Otherwise, transaction will be rejected
Successful Transaction
Acquirer responds with a successful CT response:
  • ACSP 00

Issuer receives successful transaction
  • ACSP U000
QMTC#009QR Pay to Merchant (POS): Whitelisted Special Characters
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer bank sends CT request with whitelisted special characters in the Merchant Name / Creditor Name

Field Type: NameSplChars
List Value: [A-Za-z0-9 @'/&()._-,\`*]:#+!";$%^{}~

NOTE:
Issuer should send the XML escape characters of the above special characters. Otherwise, transaction will be rejected
Successful Transaction
Acquirer responds with a successful CT response:
  • ACSP 00

Issuer receives successful transaction
  • ACSP U000
QMTC#010QR Pay to Merchant (POS): Field Value Validation
(Positive)
Pre-requisite: QR Enquiry is successful

Issuer bank sends CT request with QR String contains value 0000 in MCC Field

Successful Transaction
Acquirer responds with a successful CT response:
  • ACSP 00

Issuer receives successful transaction
  • ACSP U000
QMTC#011QR Pay to Merchant (POS): Invalid Transaction
(Negative)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request with invalid transaction
Rejected transaction by Acquirer - Invalid Transaction
Acquirer responds with a negative response:
  • RJCT 12

Issuer receives a negative response:
  • RJCT 12
QMTC#012QR Pay to Merchant (POS): Invalid Amount
(Negative)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request with invalid amount
Rejected transaction by Acquirer - Invalid Amount
Acquirer responds with a negative response:
  • RJCT 13

Issuer receives a negative response:
  • RJCT 13
QMTC#013QR Pay to Merchant (POS): Invalid Account Status
(Negative)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request but rejected
  • Beneficiary Account is dormant
  • Beneficiary Account is invalid
  • Beneficiary Account is closed
  • Beneficiary Account is blacklisted
  • Beneficiary Account is on hold or blocked
  • Beneficiary is deceased

Rejected transaction by Acquirer - Invalid Account Status
Acquirer responds with a negative response:
  • RJCT 45

Issuer receives a negative response:
  • RJCT 45
QMTC#014QR Pay to Merchant (POS): Expired QR
(Negative)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request but rejected due to expired QR

Expiry time for each foreign switches as below
  • Public Bank Berhad (PBBEMYKL) : 60s
  • Razer Merchant Services Sdn Bhd (RZMSMYNB) : 60s
  • United Overseas Bank Berhad (UOVBMYKL) : 60s
  • Axiata Digital eCode Sdn Bhd (BOSTMYNB) : at 60s
  • FINEXUS CARDS Sdn Bhd (FNXSMYNB) : 5m
  • Maybank Berhad (MBBEMYKL) : 60s
  • CIMB Bank Berhad (CIBBMYKL) : 2h
  • Hong Leong Bank Berhad (HLBBMYKL) : 60s
  • Ambank Malaysia Berhad (ARBKMYKL) : 60s
  • TNG Digital Sdn Bhd (TNGDMYNB) : 60s
  • OCBC Bank Berhad (OCBCMYKL) : 15m
  • Bank Islam Malaysia Berhad (BIMBMYKL) : 60s
Rejected Transaction by Acquirer - Expired QR
Acquirer responds with a negative response:
  • RJCT 48

Issuer receives a negative response:
  • RJCT 48
QMTC#015QR Pay to Merchant (POS): Invalid Merchant
(Negative)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request but rejected
  • Merchant Inactive / Suspended / Terminated

Rejected Transaction by Acquirer - Invalid Merchant
Acquirer responds with a negative response:
  • RJCT 49

Issuer receives a negative response:
  • RJCT 49
QMTC#016QR Pay to Merchant (POS): Invalid Account
(Negative)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request but rejected
  • Account does not exist or invalid

Rejected transaction by Acquirer - Invalid Account
Acquirer responds with a negative response:
  • RJCT 52 / RJCT 53 / RJCT N3

Issuer receives a negative response:
  • RJCT 52 / RJCT 53 / RJCT N3
QMTC#017QR Pay to Merchant (P2P): Invalid QR Category
(Negative)
Pre-requisite: QR Enquiry is successful

Issuer sends CT request but rejected
  • QR Category does not match with transaction type

Rejected transaction by RPP - Invalid QR Category
RPP responds with a negative response:
  • RJCT U307

Issuer receives a negative response:
  • RJCT U307

3. QR Transaction Enquiry

Test IDDescriptionTest DataExpected Result
TETC#001Issuer: Successful Single Transaction Enquiry for Successful Transaction
(Positive)

Pre-requisite: Issuer customer must have successful transaction.

  1. Issuer to key in BizMsgIdr from the bank channel
  2. Bank backend will initiate the Transaction Enquiry to RPP
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Successful Transaction Enquiry
  • Enquiry Status Code: ACSP
  • Enquiry Status Reason Code: U000

  • Payment Status Code: ACSP
  • Payment Status Reason Code: U000

Message Schema: camt.006.001.08
TETC#002Issuer: Successful Single Transaction Enquiry for Accepted Transaction
(Positive)

Pre-requisite: Issuer customer must have accepted transaction.

  1. Issuer to key in BizMsgIdr from the bank channel
  2. Bank backend will initiate the Transaction Enquiry to RPP
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Successful Transaction Enquiry
  • Enquiry Status Code: ACSP
  • Enquiry Status Reason Code: U000

  • Payment Status Code: ACTC
  • Payment Status Reason Code: U002

Message Schema: camt.006.001.08
TETC#003Issuer: Successful Single Transaction Enquiry for Rejected Transaction
(Positive)

Pre-requisite: Issuer customer must have rejected transaction.

  1. Issuer to key in BizMsgIdr from the bank channel
  2. Bank backend will initiate the Transaction Enquiry to RPP
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Successful Transaction Enquiry
  • Enquiry Status Code: ACSP
  • Enquiry Status Reason Code: U000

  • Payment Status Code: RJCT
  • Payment Status Reason Code: Any rejection code

Message Schema: camt.006.001.08
TETC#004Issuer: Successful Single Transaction Enquiry for Business Error Transaction
(Positive)

Pre-requisite: Using the BizMsgIdr from QMTC#017.

  1. Issuer to key in BizMsgIdr from the bank channel
  2. Bank backend will initiate the Transaction Enquiry to RPP
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Successful Transaction Enquiry
  • Status Code: ACSP
  • Status Reason Code: U000

  • Payment Status Code: U307
  • Payment Status Reason Code: U307

Message Schema: camt.006.001.08
TETC#005Issuer Request to RPP: Successful (No QR Payment)
(Negative)
  1. Issuer key in wrong/not exist BizMsgIdr from the bank channel
  2. Bank backend will initiate the Transaction Enquiry to RPP
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Successful Transaction Enquiry
  • Status Code: ACSP
  • Status Reason Code: U000
  • "Record Not Found"

Message Schema: camt.006.001.08
TETC#006Issuer Request to RPP: Bank Timeout (No request send to RPP)
(Negative)
  1. Issuer to key in BizMsgIdr from the bank channel
  2. Bank backend will initiate the Transaction Enquiry to RPP but timeout
  3. No request reach RPP
  4. Bank to display error information
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Timeout Transaction Enquiry
  • Status Code: None
  • Status Reason Code: None

  • Bank to display the error information
No message schema sent out
TETC#007Issuer Request to RPP: Timeout (No response received by bank)
(Negative)
  1. Issuer to key in BizMsgIdr from the bank channel
  2. Bank backend will initiate the Transaction Enquiry to RPP
  3. RPP responds to the request but bank timeout
  4. Bank unable to receive the response
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Timeout Transaction Enquiry
  • Status Code: None
  • Status Reason Code: None
  • Bank to display the error information

Message Schema: camt.006.001.08
TETC#008Issuer Requests to RPP: Request within 24 hours
(Positive)
  1. Issuer send request for 031 BizMsgIdr in within 24 hours
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Timeout Transaction Enquiry
  • Enquiry Status Code: ACSP
  • Enquiry Status Reason Code: U000
Message Schema: camt.006.001.08
TETC#009Issuer Requests to RPP: Request after 24 hours
(Positive)
  1. Issuer send request for 031 BizMsgIdr after 24 hours
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Successful Transaction Enquiry
  • Enquiry Status Code: ACSP
  • Enquiry Status Reason Code: U000
  • "Record Not Found"
Message Schema: camt.006.001.08
TETC#010Issuer: Single Transaction Enquiry for Successful 031 Transaction from Non Issuer
(Positive)

Pre-requisite: Non issuer must have successful transaction.

  1. Issuer to key in the successful BizMsgIdr of the non issuer
  2. Bank backend will initiate the Transaction Enquiry to RPP
  3. Bank unable to receive the response
  • Message Schema: camt.005.001.08
  • Transaction Type: 630
Timeout Transaction Enquiry
  • Status Code: None
  • Status Reason Code: None

  • Bank to display the error information
No message schema sent out

4. Report Verification via FI Report Server

Test IDDescriptionTest DataExpected Result
RPTC#001CBPSR01: Participant Settlement ReportThis is the RPP Settlement report generated for the Participant at each settlement cycle (Cycle 1 & Cycle 2).
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_CBPSR01_yyyymmdd_cycle
  • Frequency: Per cycle (2 cycles per day)
  • Format: PDF (.pdf)
RPTC#002CBPSR01: Participant Settlement ReportThis is the RPP Settlement report generated for the Participant daily.
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_CBPSR01_yyyymmdd_DAILY
  • Frequency: End of Day
  • Format: PDF (.pdf)
RPTC#003CBPSR02: Participant Settlement ReportThis is the RPP Settlement report generated for the Participant at each settlement cycle (Cycle 1 & Cycle 2).
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_CBPSR02_yyyymmdd_cycle
  • Frequency: Per cycle (2 cycles per day)
  • Format: PDF (.pdf)
RPTC#004CBPSR02: Participant Settlement ReportThis is the RPP Settlement report generated for the Participant daily.
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_CBPSR02_yyyymmdd_DAILY
  • Frequency: End of Day
  • Format: PDF (.pdf)
RPTC#005CBTAR01: Transaction Daily ReportThis is the daily report generated that contains all the RPP transactions (with status ACSP, ACTC and RJCT) initiated or received by the Participant.
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_CBTAR01_yyyymmdd
  • Frequency: End of Day
  • Format: PDF (.pdf)
RPTC#006CBTAR02: Transaction Daily FileThis is the daily file generated that contains all the RPP transactions (with status ACSP, ACTC and RJCT) initiated or received by the Participant.
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_CBTAR02_yyyymmdd
  • Frequency: End of Day
  • Format: DATA FILE (.txt)
Delimited File (Using Pipe Char - |)
RPTC#007CBTAR03: Transaction Settlement Cycle ReportThis is the daily report generated that contains all the RPP transactions (with status ACSP and ACTC) initiated or received by the Participant at each settlement cycle (Cycle 1 & Cycle 2).
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_CBTAR03_yyyymmdd_cycle
  • Frequency: Per cycle (2 cycles per day)
  • Format: PDF (.pdf)
RPTC#008CBTAR04: Transaction Settlement Cycle FileThis is the daily file generated that contains all the RPP transactions (with status ACSP and ACTC) initiated or received by the Participant at each settlement cycle (Cycle 1 & Cycle 2).
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_CBTAR04_yyyymmdd_cycle
  • Frequency: Per cycle (2 cycles per day)
  • Format: DATA FILE (.txt)
Delimited File (Using Pipe Char - |)
RPTC#009SRTR01: SAF Rejected Transactions ReportThis is the report generated that contains transactions that were rejected by the RFI during the store and forward (SAF) process.
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_SRTR01_yyyymmdd
  • Frequency: End of Day
  • Format: PDF (.pdf)
RPTC#010SRTR02: SAF Rejected Transactions FileThis is the file generated that contains transactions that were rejected by the RFI during the store and forward (SAF) process.
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_SRTR02_yyyymmdd
  • Frequency: End of Day
  • Format: DATA FILE (.txt)
Delimited File (Using Pipe Char - |)
RPTC#011SRTR03: SAF Successful Transactions ReportThis is the report generated that contains transactions that were successfully accepted by the RFI during the store and forward (SAF) process.
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_SRTR03_yyyymmdd
  • Frequency: End of Day
  • Format: PDF (.pdf)
RPTC#012SRTR04: SAF Rejected Transactions FileThis is the file generated that contains transactions that were successfully accepted by the RFI during the store and forward (SAF) process.
  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_SRTR04_yyyymmdd
  • Frequency: End of Day
  • Format: DATA FILE (.txt)
Delimited File (Using Pipe Char - |)
RPTC#013SER01: SAF Exception ReportThis is the report generated that contains transactions that have not been cleared from SAF. Reasons for the exception can be any of the following:
  • Timeout happens in RPP when sending SAF transactions
  • RFI is inactive so SAF transactions cannot be sent

  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_SER01_yyyymmdd
  • Frequency: End of Day
  • Format: PDF (.pdf)
RPTC#014SER02: SAF Exception FileThis is the file generated that contains transactions that have not been cleared from SAF. Reasons for the exception can be any of the following:
  • Timeout happens in RPP when sending SAF transactions
  • RFI is inactive so SAF transactions cannot be sent

  • Login to FI Report Server
  • Bank able to see folder
  • Download the particular report
  • Verify the details of transaction in RPP Report
Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
  • Naming Convention: RPP_BICCODE_SER02_yyyymmdd
  • Frequency: End of Day
  • Format: DATA FILE (.txt)
Delimited File (Using Pipe Char - |)