DuitNow QR (Issuer)
1. QR Account Enquiry
| Test ID | Description | Test Data | Expected Result |
|---|---|---|---|
| QRTC#001 | Issuer 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:
| Acquirer responds with a successful AE response:
|
| QRTC#002 | Issuer 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:
| Acquirer responds with a successful AE response:
|
| QRTC#003 | Issuer 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:
| Acquirer responds with a successful AE response:
|
| QRTC#004 | Issuer 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:
|
| QRTC#005 | Issuer to RPP: Whitelisted Special Characters (Positive) | Issuer bank sends an AE request with whitelisted special characters in the Recipient Reference Field Type: ReferenceSplChars List Value: +'_-.,\()/:?A-Za-z0-9@ | Acquirer responds with a successful AE response:
|
| QRTC#006 | Issuer 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:
|
| QRTC#007 | Issuer to RPP: Account Status Validation (Negative) | Issuer sends an AE request but rejected:
| Acquirer responds with a negative response:
|
| QRTC#008 | Issuer to RPP: Expired QR (Negative) | Issuer sends an AE request but rejected
| Acquirer responds with a negative response:
|
| QRTC#009 | Issuer to RPP: QR Merchant Status Validation (Negative) | Issuer sends an AE request but rejected
| Acquirer responds with a negative response:
|
| QRTC#010 | Issuer to RPP: Account Number Validation (Negative) | Issuer sends an AE request but rejected
| Acquirer responds with a negative response:
|
2. QR Credit Transfer
| Test ID | Description | Test Data | Expected Result |
|---|---|---|---|
| QMTC#001 | QR Pay to Merchant (POS): Field Value Validation (Positive) | Pre-requisite: QR Enquiry is successful Issuer sends CT request with Debtor Account Type whichever applicable. Accepts the following values:
| Successful Transaction Acquirer responds with a successful CT response:
|
| QMTC#002 | QR Pay to Merchant (POS): Field Value Validation (Positive) | Pre-requisite: QR Enquiry is successful Issuer sends CT request with Creditor Account Type whichever applicable. Accepts the following values:
| Successful Transaction Acquirer responds with a successful CT response:
|
| QMTC#003 | QR Pay to Merchant (POS): Field1 Value Validation (Positive) | Pre-requisite: QR Enquiry is successful Issuer sends CT request with Static QR by populating the value based on the merchant amount | Successful Transaction Acquirer responds with a successful CT response:
|
| QMTC#004 | QR Pay to Merchant (POS): Field1 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 | Successful Transaction Acquirer responds with a successful CT response:
|
| QMTC#005 | QR Pay to Merchant (POS): Field2 Value Validation (Positive) | Pre-requisite: QR Enquiry is successful Issuer sends CT request by populating values based on AE response | Successful Transaction Acquirer responds with a successful CT response:
|
| QMTC#006 | QR Pay to Merchant (POS): Field3 Value Validation (Positive) | Pre-requisite: QR Enquiry is successful Issuer sends CT request using same value with <IntrBkSttlmAmt> | Successful Transaction Acquirer responds with a successful CT response:
|
| QMTC#007 | QR 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
|
| QMTC#008 | QR 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 @'/&()._-,\`*]:#+!";$%^{}~ (exactly this value) 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:
|
| QMTC#009 | QR 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 @'/&()._-,\`*]:#+!";$%^{}~ (exactly this value) 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:
|
| QMTC#010 | QR 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 Recipient Reference Field Type: ReferenceSplChars List Value: +'_-.,\()/:?A-Za-z0-9@ (exactly this value) 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:
|
| QMTC#011 | QR 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:
|
| QMTC#012 | QR 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:
|
| QMTC#013 | QR Pay to Merchant (POS): Invalid Account Status (Negative) | Pre-requisite: QR Enquiry is successful Issuer sends CT request but rejected
| Rejected transaction by Acquirer - Invalid Account Status Acquirer responds with a negative response:
|
| QMTC#014 | QR Pay to Merchant (POS): Invalid Source of Fund (Negative) | Pre-requisite: QR Enquiry is successful Issuer sends CT request but rejected due to invalid Source of Fund (different with AE response) | Rejected transaction by Acquirer - Invalid SOF Acquirer responds with a negative response:
|
| QMTC#015 | QR 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
| Rejected Transaction by Acquirer - Expired QR Acquirer responds with a negative response:
|
| QMTC#016 | QR Pay to Merchant (POS): Invalid Merchant (Negative) | Pre-requisite: QR Enquiry is successful Issuer sends CT request but rejected
| Rejected Transaction by Acquirer - Invalid Merchant Acquirer responds with a negative response:
|
| QMTC#017 | QR Pay to Merchant (POS): Invalid Account (Negative) | Pre-requisite: QR Enquiry is successful Issuer sends CT request but rejected
| Rejected transaction by Acquirer - Invalid Account Acquirer responds with a negative response:
|
3. QR Reverse Credit Transfer
| Test ID | Description | Test Data | Expected Result |
|---|---|---|---|
| RQTC#001 | Success Scenario of Credit Reversal - 011 (Positive) | Pre-requisite: Issuer (original acquirer of 031) sends Reverse Credit Transfer for QR Payment Acquirer (original issuer of 031) Respond to Reverse Credit Transfer for QR Payment Note: Currently only support auto-reversal for NETS Dynamic QR | Successful Transaction - Original Issuer of 031 Response
|
4. QR Transaction Enquiry
| Test ID | Description | Test Data | Expected Result |
|---|---|---|---|
| TETC#001 | Issuer: Successful Single Transaction Enquiry for Successful Transaction (Positive) | Pre-requisite: Issuer customer must have successful transaction.
| Successful Transaction Enquiry
|
| TETC#002 | Issuer: Successful Single Transaction Enquiry for Accepted Transaction (Positive) | Pre-requisite: Issuer customer must have accepted transaction.
| Successful Transaction Enquiry
|
| TETC#003 | Issuer: Successful Single Transaction Enquiry for Rejected Transaction (Positive) | Pre-requisite: Issuer customer must have rejected transaction.
| Successful Transaction Enquiry
|
| TETC#004 | Issuer Request to RPP: Successful (No QR Payment) (Negative) |
| Successful Transaction Enquiry
|
| TETC#005 | Issuer Request to RPP: Bank Timeout (No request send to RPP) (Negative) |
| Timeout Transaction Enquiry
|
| TETC#006 | Issuer Request to RPP: Timeout (No response received by bank) (Negative) |
| Timeout Transaction Enquiry
|
| TETC#007 | Issuer Requests to RPP: Request within 24 hours (Positive) |
| Timeout Transaction Enquiry
|
| TETC#008 | Issuer Requests to RPP: Request after 24 hours (Positive) |
| Successful Transaction Enquiry
|
| TETC#009 | Issuer: Single Transaction Enquiry for Successful 031 Transaction from Non Issuer (Positive) | Pre-requisite: Non issuer must have successful transaction.
| Timeout Transaction Enquiry
|
5. Report Verification via FI Report Server
| Test ID | Description | Test Data | Expected Result |
|---|---|---|---|
| RPFI#001 | CBPSR01: Participant Settlement Report | This is the RPP Settlement report generated for the Participant at each settlement cycle (Cycle 1 & Cycle 2).
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#002 | CBPSR01: Participant Settlement Report | This is the RPP Settlement report generated for the Participant daily.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#003 | CBPSR02: Participant Settlement Report | This is the RPP Settlement report generated for the Participant at each settlement cycle (Cycle 1 & Cycle 2).
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#004 | CBPSR02: Participant Settlement Report | This is the RPP Settlement report generated for the Participant daily.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#005 | CBTAR01: Transaction Daily Report | This is the daily report generated that contains all the RPP transactions (with status ACSP, ACTC and RJCT) initiated or received by the Participant.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#006 | CBTAR02: Transaction Daily File | This is the daily file generated that contains all the RPP transactions (with status ACSP, ACTC and RJCT) initiated or received by the Participant.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#007 | CBTAR03: Transaction Settlement Cycle Report | This 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).
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#008 | CBTAR04: Transaction Settlement Cycle File | This 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).
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#009 | SRTR01: SAF Rejected Transactions Report | This is the report generated that contains transactions that were rejected by the RFI during the store and forward (SAF) process.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#010 | SRTR02: SAF Rejected Transactions File | This is the file generated that contains transactions that were rejected by the RFI during the store and forward (SAF) process.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#011 | SRTR03: SAF Successful Transactions Report | This is the report generated that contains transactions that were successfully accepted by the RFI during the store and forward (SAF) process.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#012 | SRTR04: SAF Rejected Transactions File | This is the file generated that contains transactions that were successfully accepted by the RFI during the store and forward (SAF) process.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#013 | SER01: SAF Exception Report | This is the report generated that contains transactions that have not been cleared from SAF. Reasons for the exception can be any of the following:
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#014 | SER02: SAF Exception File | This is the file generated that contains transactions that have not been cleared from SAF. Reasons for the exception can be any of the following:
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#015 | PFMR01: Participant Fee Monthly Report | This is the report generated for the Participant monthly to inform on the fees incurred within the month.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPFI#016 | PFMR02: Participant Fee Monthly File | This is the file generated for the Participant monthly to inform on the fees incurred within the month.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
6. Report Verification via Back Office Portal
| Test ID | Description | Test Data | Expected Result |
|---|---|---|---|
| RPBO#001 | CBPSR01: Participant Settlement Report | This is the RPP Settlement report generated for the Participant at each settlement cycle (Cycle 1 & Cycle 2).
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#002 | CBPSR01: Participant Settlement Report | This is the RPP Settlement report generated for the Participant daily.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#003 | CBPSR02: Participant Settlement Report | This is the RPP Settlement report generated for the Participant at each settlement cycle (Cycle 1 & Cycle 2).
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#004 | CBPSR02: Participant Settlement Report | This is the RPP Settlement report generated for the Participant daily.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#005 | CBTAR01: Transaction Daily Report | This is the daily report generated that contains all the RPP transactions (with status ACSP, ACTC and RJCT) initiated or received by the Participant.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#006 | CBTAR02: Transaction Daily File | This is the daily file generated that contains all the RPP transactions (with status ACSP, ACTC and RJCT) initiated or received by the Participant.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#007 | CBTAR03: Transaction Settlement Cycle Report | This 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).
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#008 | CBTAR04: Transaction Settlement Cycle File | This 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).
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#009 | SRTR01: SAF Rejected Transactions Report | This is the report generated that contains transactions that were rejected by the RFI during the store and forward (SAF) process.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#010 | SRTR02: SAF Rejected Transactions File | This is the file generated that contains transactions that were rejected by the RFI during the store and forward (SAF) process.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#011 | SRTR03: SAF Successful Transactions Report | This is the report generated that contains transactions that were successfully accepted by the RFI during the store and forward (SAF) process.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#012 | SRTR04: SAF Rejected Transactions File | This is the file generated that contains transactions that were successfully accepted by the RFI during the store and forward (SAF) process.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#013 | SER01: SAF Exception Report | This is the report generated that contains transactions that have not been cleared from SAF. Reasons for the exception can be any of the following:
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#014 | SER02: SAF Exception File | This is the file generated that contains transactions that have not been cleared from SAF. Reasons for the exception can be any of the following:
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#015 | PFMR01: Participant Fee Monthly Report | This is the report generated for the Participant monthly to inform on the fees incurred within the month.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|
| RPBO#016 | PFMR02: Participant Fee Monthly File | This is the file generated for the Participant monthly to inform on the fees incurred within the month.
| Bank able to download the report successfully which follow the correct naming convention, format and perform verification:
|