Annexures

This section will host all annexures to this pack.

Scan to Pay System Integration Test Pack

SIT Process

When the Merchant is ready to test and integrate into Scan to Pay a mail will need to be sent to Scan to [email protected] who will then load the Merchant/PSP onto the Scan to Pay Test system.
This must include the Name that the Merchant/PSP chooses to use as well as an email of the Administrator to access the Scan to Pay portal.

The Administrator will usually be the person responsible for the technical side of the of Merchant/PSP’s development.
Once the Merchant/PSP is successfully loaded onto the test system by Scan to Pay team – the administrator or the Merchant/PSP will receive an email to access the Scan to Pay portal. A password will need to be created. Please note this email expires after 24 hours and will need to be reset thereafter.
This is where the Administrator will create API Key for the test system. This will be used to link the merchant system to the Scan to Pay test system.

Once logged on. The Merchant/PSP will be able to retrieve your API key as well as set up sub-users and merchant notification details.

Ready to Test

For testing on Test make sure that your app is in Test mode. The Scan to Pay app can be downloaded from the Android and iOS stores. You will need to scan the below code to switch your app between Live and Test.

#CardOn / Off Us
T1DCOn Us
T2DCOn Us
T3DCOn Us
T4DCOff Us
235

QR

Thereafter, you can use the below for testing your integration when completing a payment after scanning
the QR code.

Add 4 more digits to the card ranges below and they will return the desired response.
These below test cards will test only the below-mentioned scenarios and will only work once your Scan to Pay application is switched to test.

Debit Card

Any 18 digit card starting with 50010001000105 with any bank PIN = 00 response (success)
Any 18 digit card starting with 50010001000101 with any bank PIN = 51 response (insufficient funds)
Any 18 digit card starting with 50010001000103 with any bank PIN = 91 response (issuer or switch inoperative/bank unavailable)

Credit Card

Any 18 digit card starting with 50020001000105 with any bank PIN = 00 response (success)
Any 18 digit card starting with 50020001000101 with any bank PIN = 51 response (insufficient funds)
Any 18 digit card starting with 50020001000103 with any bank PIN = 91 response (issuer or switch
inoperative/bank unavailable)

Scan to Pay User Acceptance Test Pack

Integrator NameIntegrator TypeIntegrators Web URL/USSDTest Designation
*

Test Slot

DateTimeSlot Number
*

Integrator Test Resource

NamePhoneEmail
*

Signoff Sheet

NameDesignationDateSignature
*
*
*
*
*

Branding Tests

ResultDescription
Left BlankTest still to be performed
YPassed all checks
NFailed
N/ANot applicable to integrator
Test CaseTest DetailResultComments
B1Buy with Scan to Pay branding present on the merchant website landing page
B2Buy with Scan to Pay branding present on the Merchant's landing App
B3Buy with Scan to Pay payment option presented before the checkout page on the merchants website
B4Buy with Scan to Pay payment option presented before the checkout page on the merchants APP
B5Buy with Scan to Pay payment option present on the merchant website
B6Buy with Scan to Pay payment option present on the merchant APP
B7App to App Call according to the Secure MOTO API executed
B8Buy with Scan to Pay payment option present on the merchant USSD Menu
B9Customer engagement – Is the customer being referred to his mobile phone to authorise the transaction
B10Customer engagement – Is the customer advised to have his phone unlocked in order to receive the PIN request
B11Customer engagement – Are the Scan to Pay info graphics present on the website
B12Are the Scan to Pay T&Cs present on the website
B13Are the Scan to Pay T&Cs present on the APP
B14Scan to Pay keys loaded on Back Office?
B15Notification http loaded by merchant on Portal
B16Notification SMS loaded by merchant on Portal
B17Notification Email loaded by merchant on Portal
B18Merchant accepts notification
B19Merchant acknowledges notification
B20Initiate reversal, is this handled correctly by merchant

Implementation Tests

ResultDescription
Left BlankTest still to be performed
YPassed all checks
NFailed
N/ANot applicable to integrator

🚧

NB

The following Test cases are applicable to USSD Integration only!

Test CaseCardOn / Off UsRegistration StateResultCommentSettlement
T1On UsNew RegistrationSuccessful - The user Initiates the trans Via USSD β†’ User will be prompted for registration first and then pin.
T2On UsAlready RegisteredSuccessful - The user Initiates the trans Via USSD β†’ User will be prompted for pin only
T3On UsAlready RegisteredFailed - Incorrect pin - The user Initiates the trans Via USSD β†’ User will be prompted for pin only. Response Code 55.
T4Off UsNew RegistrationSuccessful - The user Initiates the trans Via USSD β†’ User will be prompted for registration first and then pin.
T5Off UsAlready RegisteredSuccessful - The user Initiates the trans Via USSD β†’ User will be prompted for pin only
T6Off UsAlready RegisteredFailed - Incorrect pin - The user Initiates the trans Via USSD β†’ User will be prompted for pin only. Response Code 55.
T7On UsNew RegistrationSuccessful - The user Initiates the trans Via USSD β†’ User will be prompted for registration first, then CVV and pin.
T8On UsAlready RegisteredSuccessful - The user Initiates the trans Via USSD β†’ User will be prompted for PIN and CVV only.
T9On UsAlready RegisteredFailed - Incorrect pin - The user Initiates the trans Via USSD β†’ User will be prompted for pin and CVV only. Response Code 55.
T10On UsAlready RegisteredFailed - Incorrect CVV - The user Initiates the trans Via USSD β†’ User will be prompted for pin and CVV only. Response Code 05.
T11Off UsNew RegistrationSuccessful - The user Initiates the trans Via USSD β†’ User will be prompted for registration first, then CVV and pin.
T12Off UsAlready RegisteredSuccessful - Successful - The user Initiates the trans Via USSD β†’ User will be prompted for PIN and CVV only.
T13Off UsAlready RegisteredFailed - Incorrect pin - The user Initiates the trans Via USSD β†’User will be prompted for pin and CVV only Response Code 55.
T14Off UsAlready RegisteredFailed - Incorrect CVV - The user Initiates the trans Via USSD β†’ User will be prompted for pin and CVV only. Response Code 05.
T15Off /
On Us
Already RegisteredFailed – Insufficient Funds - The user Initiates the trans Via USSD β†’ User will be prompted for pin and CVV only. Response Code 51.
T16On UsAlready RegisteredSuccessful – The user Initiates the trans Via USSD β†’ User to select add card during transaction, will be prompted to enter new card details β†’The users enter new card details and PIN.
T17Off /
On Us
New RegistrationExpired Card: Credit / Cheque Card - The user Initiates the trans Via USSD β†’ The user is prompted to input the incorrect Expiry Date on the App β†’ Unsuccessful message appears on Website β†’ Unsuccessful message appears on App. Response 54.

Test Summary

Test SummaryTotal
Successful Tests
Failed Tests
Not Applicable Tests
TOTAL

Failed Test Summary

Test Case NumberReason for Failure
x
x
x

🚧

NB

The following Test cases are applicable to all integrations excluding USSD!

Test CaseCardOn / Off UseTest DescriptionResultCommentSettlement
T1DCOn UsSuccessful - The user Initiates the trans Via WEB/APP β†’ The User is prompted to input the PIN on the App.
T2DCOn UsFailed - Incorrect pin β†’ The user Initiates the trans Via WEB/APP - User will be prompted for PIN on the APP. Response Code 55.
T3DCOff UsSuccessful - The user Initiates the trans Via WEB/APP β†’ The User is prompted to input the PIN on the App.
T4DCOff UsFailed - Incorrect pin - The user Initiates the trans Via WEB/APP β†’ User will be prompted for PIN on the APP.
Response Code 55.
T5CCOn UsSuccessful - The user Initiates the trans Via WEB/APP β†’ The User is prompted to input the PIN on the App.
T6CCOn UsFailed - Incorrect pin - The user Initiates the trans Via WEB/APP β†’ User will be prompted for PIN on the APP.
Response Code 55.
T7CCOn UsFailed - Incorrect CVV - The user Initiates the trans Via WEB/APP β†’ User will be prompted for pin and CVV only.
Response Code 05.
T8CCOff UsSuccessful - The user Initiates the trans Via WEB/APP β†’ The User is prompted to input the PIN on the App.
T9CCOff UsFailed - Incorrect pin - The user Initiates the trans Via WEB/APP β†’ User will be prompted for PIN on the APP.
Response Code 55.
T10CCOff UsFailed - Incorrect CVV β†’ The user Initiates the trans Via USSD β†’ User will be prompted for pin and CVV only. Response Code 05.
T11CCOff /
On Us
3D Secure The user Initiates the trans Via App. The Issuing Bank 3DS page appears in the app The user captures either the mobile number / email address for the Issuer to deliver the OTP β†’ The user receives the OTP (SMS/Email) β†’ The user enters the OTP into the 3DS page within the App β†’ The user enters the CVV2 of the card within the App β†’ Success message appears on App β†’ Successful message appears on Website.
T12CCOff /
On Us
Failed – Insufficient Funds β†’ The user Initiates the trans Via β†’ User will be prompted for pin and CVV only.
Response Code 51.
T13CC / DCOff /
On Us
Failed - Expired Card: Credit / Cheque Card - The user Initiates the trans Via USSD β†’ The user is prompted to input the incorrect Expiry Date on the App β†’ Unsuccessful message appears on Website β†’ Unsuccessful message appears on App. Response 54.

Test Summary

Test SummaryTotal
Successful Tests
Failed Tests
Not Applicable Tests
TOTAL

Failed Test Summary

Test Case NumberReason for Failure
x
x
x

Scan to Pay Training Sign Off

IntegratorTraining Date
*
Topics Covered
*
*
*
Supporting Documentation
*
*
*

Attendees

NameDateSignature
*
*
*
TrainerDateSignature
*

Support Notification Registration

The Scan to Pay support team sends out notifications via email when system issues are experienced,
ie. Bank links down etc.

NamePositionContact NumberEmail Address
*
*
*