Pay by QR Integration Acceptance Test

2016
PAY BY QR INTEGRATION ACCEPTANCE TEST
Pay by QR
Integration
Acceptance Test
SIGNED OFF INTEGRATION ACCEPTANCE TEST
PT DIMO PAY INDONESIA
0
October 19, 2016
SIGNED OFF ANDROID PLATFORM
1
October 19, 2016
ITC 001 / Reject Term and Condition

Scenario Description Mobile user rejecting Pay by QR term and condition
Test Environment / Apps Platform SANDBOX / ANDROID

1. Install mobile application
2. User login the application
Test Step
3. Click Pay by QR on menu
4. Disagree to term and condition
Status :
Expected Test Result 1. Mobile application return to home screen
OK / NOK
Conducted on PT DIMO Pay Indonesia <Issuer legal name>

<start date>
to
<end date>
At <Test location> Parman Suparman <name>
2
October 19, 2016
ITC 002 / Accept Term and Condition

User key will be requested to host server when mobile user/account access Pay
Scenario Description
by QR menu for the first time.
Test Step 3. Click Pay by QR on menu
4. Agree to term and condition
5. Do Pay by QR transaction
1. Successful transaction
Status :
Expected Test Result 2. Transaction is recorded on DPP with User API Key field isnt
OK / NOK
empty.

<start date>
to
<end date>
3
October 19, 2016
ITC 003 / Clear Applications Cache or Data

Scenario Description Mobile user clear applications cache or data

1. Open android setting
2. Choose Apps menu
3. Select installed mobile application
4. Clear applications data
Test Step
5. User open application and login
Status :
Expected Test Result 2. Transaction have the same user API key with ITC 003 on
OK / NOK
DPP

<start date>
to
<end date>
4
October 19, 2016
ITC 004 / Application Reinstallation

Scenario Description Mobile user reinstall issuers mobile application

1. User reinstall mobile application
1. Successful transaction Status :
Expected Test Result
2. Transaction have the same user API key with ITC 003 on DPP OK / NOK

<start date>
to
<end date>
5
October 19, 2016
ITC 005 / Double Device Single User Account

Scenario Description One user account use Pay by QR on different device

1. User login with two different devices
Test Step 2. User click Pay by QR menu
3. Do Pay by QR transaction in both devices one after another
1. Mobile application open scanning QR screen
Status :
Expected Test Result 2. Successful transaction
OK / NOK
3. Both transaction should have the same user API key on DPP.

<start date>
to
<end date>
6
October 19, 2016
ITC 006 / Single Device Multiple User Account
Scenario Description One device is used for more than one logged in accounts

1. One device is used by two account/user
2. Each account do Pay by QR transaction in the same device one after
Test Step another
3. Four times transaction (or more) with switching the account each
transaction
Status :
Expected Test Result 2. Produced transaction should have different user API key that is
OK / NOK
displayed on DPP

<start date>
to
<end date>
7
October 19, 2016
ITC 007 / Cancel Transaction by Close Scanning Screen

User cancel to do Pay by QR transaction by pressing crosscheck in scanning
screen
1. User select Pay by QR menu
Test Step
2. Press close (crosscheck button) in scanning QR screen
Status :
Expected Test Result 1. Closed SDK and opened home application screen
OK

<start date>
to
<end date>
8
October 19, 2016
ITC 008 / Insufficient Payment Fund

Scenario Description User do a transaction with bigger transaction amount than balance

1. User open issuers mobile application
2. Select Pay by QR menu
Test Step
3. Scan QR
Pay an invoice that have amount greater than balance
1. Show failed transaction Status :
2. Close SDK and return to home screen OK

<start date>
to
<end date>
9
October 19, 2016
ITC 009 / Invalid QR

Scenario Description User scanning QR do not related to Pay by QR

Test Step 2. Select Pay by QR menu
3. Scan QR non entity system
1. Show invalid QR notification Status:
2. Close SDK and return to scanning screen OK

<start date>
to
<end date>
10
October 19, 2016
ITC 010 / Invalid QR Expired


1. Show invalid QR notification Status:
2. Close SDK and return to scanning screen OK

<start date>
to
<end date>
11
October 19, 2016
ITC 011 / Invalid PIN Input

Scenario Description User do Pay by QR transaction and input incorrect PIN

Test Step
3. Scan QR
4. Input incorrect PIN
1. Failed transaction Status :
2. Close SDK and return to home screen OK

<start date>
to
<end date>
12
October 19, 2016
ITC 012 / Input PIN Cancellation

User do Pay by QR transaction and do cancellation when input PIN screen is
pop-up
Test Step
3. Scan QR
4. Select cancel on input PIN pop-up
Status :
Expected Test Result 1. Close SDK and return to home screen
OK

<start date>
to
<end date>
13
October 19, 2016
ITC 013 / Invalid OTP Input

Scenario Description User do Pay by QR transaction and input incorrect OTP

Test Step
3. Scan QR
4. Input incorrect OTP
2. Close SDK and return to home screen OK / NOK

<start date>
to
<end date>
14
October 19, 2016
ITC 014 / Input OTP Cancellation

pop-up
Test Step
3. Scan QR
4. Select cancel on input OTP pop-up
Status :
OK / NOK

<start date>
to
<end date>
15
October 19, 2016
ITC 015 / Portrait Screen Orientation

Scenario Description User change screen orientation while opening Pay by QR

Test Step
3. Scan QR
4. Rotate the phone / change screen orientation
Status :
Expected Test Result 1. Portrait screen orientation
OK

<start date>
to
<end date>
16
October 19, 2016
ITC 016 / Decimal Rounding on Percentage Discount

Round up for paid amount while greater than or equals 0.5 and round up for
discount amount while greater than 0.5
Test Step
3. Scan QR
4. Pay invoice with discount
1. DPP display rounded transaction amount at Total Amount
field Status :
2. DPP display rounded discount amount at Loyalty Amount OK
field

<start date>
to
<end date>
17
October 19, 2016
ITC 017 / In-App Purchase
Scenario Description Mobile user decide a purchase while he/she is browse in mobile web browser

1. User open URL that contain trigger to issuers mobile application
2. User clicking trigger button to issuers mobile application
3. Opened issuers mobile application and directly show payment
Test Step
confirmation screen
4. Finished payment process will return to callback URL provided by e-
commerce
1. Successful payment notification
Status :
Expected Test Result 2. Return to stated application or web URL provided by e-
OK / NOK
commerce

<start date>
to
<end date>
18
October 19, 2016
ITC 018 / QR Store Transaction

Scenario Description Mobile user do Pay by QR transaction from Pay by QR catalog

1. User is scanning catalog Pay by QR
2. Every scanned QR is added to shopping chart
Test Step
3. User click pay in payment confirmation screen
4. Finish transaction
1. Successful payment notification Status :
2. Return to issuers mobile application home screen OK / NOK

<start date>
to
<end date>
19
October 19, 2016
ITC 019 / Loyalty Inquiry

Scenario Description Mobile user queries existed loyalty program

1. User open menu Promo Pay by QR
Test Step
2. Queries loyalty program
Status :
Expected Test Result 1. Successful loyalty program inquiry
OK

<start date>
to
<end date>
20
October 19, 2016
ITC 020 / Payment with Tipping

Scenario Description Mobile user pay a normal transaction with tip amount

Test Step
3. Scan QR
4. Add tips amount
2. Balance deduction history should be consist of paid amount Status :
and tip amount OK
3. DPP display the value at Tip Amount field

<start date>
to
<end date>
21
October 19, 2016
ITC 021 / Tipping Amount Not Greater Than Paid Amount


Test Step
3. Scan QR
4. Add tips amount so that tip amount exceed or equals transaction amount
Status :
Expected Test Result 1. Failed payment notification
OK

<start date>
to
<end date>
22
October 19, 2016
ITC 022 / Maximum Redeem Discount Amount

Scenario Description Mobile user pay a normal transaction

Test Step 3. Scan QR
4. Pay a transaction which is have discount amount greater than allowed
discount amount
1. Payment confirmation show maximum discount amount
instead of discount amount Status :
2. Successful transaction OK
3. Recorded transaction on DPP

<start date>
to
<end date>
23
October 19, 2016
ITC 023 / Minimum Transaction Amount Gain Discount


Test Step
3. Scan QR
4. Transaction amount greater than or equals minimum required qualification
1. Payment confirmation show discount amount
Status :
OK

<start date>
to
<end date>
24
October 19, 2016
ITC 024 / Minimum Transaction Amount Do Not Gain Discount


Test Step
3. Scan QR
4. Transaction amount less than minimum required qualification
1. Payment confirmation show normal transaction
Status :
OK

<start date>
to
<end date>
25
October 19, 2016
ITC 025 / QR Offline Transaction


Test Step 3. Scan QR offline
4. Input transaction amount
5. Pay the invoice on payment confirmation
2. Recorded transaction on DPP OK

<start date>
to
<end date>
SIGNED OFF iOS PLATFORM
26
October 19, 2016
ITC 001 / Reject Term and Condition

Scenario Description Mobile user rejecting Pay by QR term and condition
Test Environment / Apps Platform SANDBOX / iOS

Test Step
4. Disagree to term and condition
Status :
Expected Test Result 1. Mobile application return to home screen
OK / NOK

<start date>
to
<end date>
27
October 19, 2016
ITC 002 / Accept Term and Condition

User key will be requested to host server when mobile user/account access Pay
by QR menu for the first time.
Status :
Expected Test Result 2. Transaction is recorded on DPP with User API Key field isnt
OK / NOK
empty.

<start date>
to
<end date>
28
October 19, 2016
ITC 003 / Application Reinstallation

Scenario Description Mobile user reinstall issuers mobile application

1. User reinstall mobile application
1. Mobile application open scanning QR screen Status :
2. Transaction have the same user API key with ITC 002 on DPP OK / NOK

<start date>
to
<end date>
29
October 19, 2016
ITC 004 / Double Device Single User Account

Scenario Description One user account use Pay by QR on different device
Test Environment / Apps
SANDBOX / iOS
Platform
1. User login with two different devices
Test Step 2. User click Pay by QR menu
3. Do Pay by QR transaction in both devices one after another
1. Mobile application open scanning QR screen
3. Both transaction should have the same user API key on OK / NOK
DPP

<start date>
to
<end date>
30
October 19, 2016
ITC 005 / Single Device Multiple User Account

Scenario Description One device is used for more than one logged in accounts

1. One device is used by two account/user
2. Each account do Pay by QR transaction in the same device one after
Test Step another
3. Four times transaction (or more) with switching the account each
transaction
Status :
Expected Test Result 2. Produced transaction should have different user API key
OK / NOK
that is displayed on DPP

<start date>
to
<end date>
31
October 19, 2016
ITC 006 / Cancel Transaction by Close Scanning Screen

User cancel to do Pay by QR transaction by pressing crosscheck in scanning
screen
1. User select Pay by QR menu
Test Step
2. Press close (crosscheck button) in scanning QR screen
Status :
Expected Test Result 1. Closed SDK and opened home application screen
OK / NOK

<start date>
to
<end date>
32
October 19, 2016
ITC 007 / Insufficient Payment Fund

Scenario Description User do a transaction with bigger transaction amount than balance

Test Step
3. Scan QR
4. Pay an invoice that have amount greater than balance
1. Show failed transaction Status :

<start date>
to
<end date>
33
October 19, 2016
ITC 008 / Invalid QR


1. Show invalid QR notification Status :

<start date>
to
<end date>
34
October 19, 2016
ITC 009 / Invalid Input PIN

Scenario Description User do Pay by QR transaction and input incorrect PIN

Test Step
3. Scan QR

<start date>
to
<end date>
35
October 19, 2016
ITC 010 / Input PIN Cancellation

Test Number / Test Name
pop-up
Test Step
3. Scan QR
Status :
OK / NOK

<start date>
to
<end date>
36
October 19, 2016
ITC 011 / Invalid OTP Input

Scenario Description User do Pay by QR transaction and input incorrect OTP

Test Step
3. Scan QR

<start date>
to
<end date>
37
October 19, 2016
ITC 012 / Input OTP Cancellation

pop-up
Test Step
3. Scan QR
Status :
OK / NOK

<start date>
to
<end date>
38
October 19, 2016
ITC 013 / Portrait Screen Orientation

Scenario Description User change screen orientation while opening Pay by QR

Test Step
3. Scan QR
4. Rotate the phone / change screen orientation
Status :
Expected Test Result 1. Portrait screen orientation
OK / NOK

<start date>
to
<end date>
39
October 19, 2016
ITC 014 / Decimal Rounding on Percentage Discount

Round up for paid amount while greater than or equals 0.5 and round up for
discount amount while greater than 0.5
Test Step
3. Scan QR
4. Pay invoice with discount
1. DPP display rounded transaction amount at Total Amount
field Status :
2. DPP display rounded discount amount at Loyalty Amount OK / NOK
field

<start date>
to
<end date>
40
October 19, 2016
ITC 015 / In-App Purchase

Scenario Description Mobile user decide a purchase while he/she is browse in mobile web browser

1. User open URL that contain trigger to issuers mobile application
2. User clicking trigger button to issuers mobile application
3. Opened issuers mobile application and directly show payment
Test Step
confirmation screen
4. Finished payment process will return to callback URL provided by e-
commerce
Status :
Expected Test Result 2. Return to stated application or web URL provided by e-
OK / NOK
commerce

<start date>
to
<end date>
41
October 19, 2016
ITC 016 / QR Store Transaction

Scenario Description Mobile user do Pay by QR transaction from Pay by QR catalog

1. User is scanning catalog Pay by QR
2. Every scanned QR is added to shopping chart
Test Step
3. User click pay in payment confirmation screen
4. Finish transaction
1. Successful payment notification Status :
2. Return to issuers mobile application home screen OK / NOK

<start date>
to
<end date>
42
October 19, 2016
ITC 017 / Loyalty Inquiry

Scenario Description Mobile user queries existed loyalty program

1. User open menu Promo Pay by QR
Test Step
2. Queries loyalty program
Status :
Expected Test Result 1. Successful loyalty program inquiry
OK / NOK

<start date>
to
<end date>
43
October 19, 2016
ITC 018 / Payment with Tipping


Test Step
3. Scan QR
4. Add tips amount
2. Balance deduction history should be consist of paid amount Status :
and tip amount OK / NOK
3. DPP display the value at Tip Amount field

<start date>
to
<end date>
SIGNED OFF BACKEND MESSAGE
44
October 19, 2016
ITC 001 / Correct User API Key Request Message

Scenario Description User do Pay by QR transaction normally
Test Environment SANDBOX

1. Login with user/account that will do Pay By QR for the first time
Test Step
3. Accept Term and Condition
4. Scanning QR screen is opened
1. MTI request should be 0800
2. Data element 3 should 000010
3. Data element 7 should numeric 10 with format
MMDDhhmmss
Status :
Expected Test Result 4. Data element 11 should numeric 6 right alignment padded
OK / NOK
with zero
5. Data element 32 should numeric LLVAR max 11
7. Database mapping between user API key and account

<start date>
to
<end date>
45
October 19, 2016
ITC 002 / Correct Payment Inquiry Message

Test Environment / Apps Platform SANDBOX

Test Step
3. Scan QR
4. Pay invoice normally
1. MTI request should 0100
3. Data element 4 should numeric 18 right alignment zero
padded with two decimal point
DDMMhhmmss
5. Data element 11 should numeric 6 right alignment padded
with zero
6. Data element 12 should numeric 6 with format hhmmss
7. Data element 13 should numeric 4 with format MMDD
9. Data element 39 at MTI 0110 should 00 as successful
10. Data element 41 should alfa numeric 8 left alignment space
padded
11. Data element 43 should alfa numeric 40 left alignment Status :
space padded OK / NOK
12. Data element 48 should alfa numeric 40 left alignment
space padded
15. Data element 61 should alfa numeric LLLVAR max 999
16. Data element 62 consist of 40 char space padded, numeric
12 right alignment zero padded without decimal point,
numeric 3 right alignment zero padded, alfa numeric 20 left
alignment space padded, alfa numeric 40 left alignment
space padded, numeric 12 right alignment zero padded and
numeric 12 right alignment zero padded.
space padded

<start date>
to
<end date>
46
October 19, 2016
ITC 003 / Correct Payment Acknowledgment Message


Test Step
3. Scan QR
DDMMhhmmss
with zero
padded
space padded
Status :
Expected Test Result 13. Data element 41 should alfa numeric 8 left alignment space
OK / NOK
padded
space padded
space padded
numeric 12 right alignment zero padded
space padded

<start date>
to
<end date>
47
October 19, 2016
ITC 004 / Correct Payment Advice Message


Test Step
3. Scan QR
DDMMhhmmss
with zero
padded
space padded
Status :
Expected Test Result 13. Data element 41 should alfa numeric 8 left alignment space
OK / NOK
padded
space padded
space padded
numeric 12 right alignment zero padded
space padded

<start date>
to
<end date>
48
October 19, 2016
ITC 005 / Pending Transaction Due to Do Not Reply

Scenario Description Payment with timeout respond for acknowledgement

Test Step 3. Scan QR with 123456 as transaction amount
5. Timeout at payment acknowledgement
1. No response found in interval between payment
Status :
Expected Test Result acknowledgement and other message are more than 25
OK / NOK
second

<start date>
to
<end date>
49
October 19, 2016
ITC 006 / Pending Transaction Due to Reply 68

Scenario Description Payment with timeout respond for acknowledgement

Test Step 3. Scan QR with 1234567 as transaction time
5. Payment acknowledgement receive 68 at DE39 MTI230
1. Data element 39 at MTI 0230 is 68
Status :
Expected Test Result 2. Payment advice messages (data element 3 is 510000) are
OK / NOK
received.

<start date>
to
<end date>
50
October 19, 2016

Pay by QR Integration Acceptance Test

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pay by QR Integration Acceptance Test

Uploaded by

Copyright:

Available Formats

2016

PAY BY QR INTEGRATION ACCEPTANCE TEST

SIGNED OFF ANDROID PLATFORM

ITC 001 / Reject Term and Condition

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 002 / Accept Term and Condition

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 003 / Clear Applications Cache or Data

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 004 / Application Reinstallation

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 005 / Double Device Single User Account

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 006 / Single Device Multiple User Account

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 007 / Cancel Transaction by Close Scanning Screen

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 008 / Insufficient Payment Fund

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 009 / Invalid QR

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 010 / Invalid QR Expired

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 011 / Invalid PIN Input

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 012 / Input PIN Cancellation

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 013 / Invalid OTP Input

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 014 / Input OTP Cancellation

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 015 / Portrait Screen Orientation

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 016 / Decimal Rounding on Percentage Discount

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 017 / In-App Purchase

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 018 / QR Store Transaction

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 019 / Loyalty Inquiry

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 020 / Payment with Tipping

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 021 / Tipping Amount Not Greater Than Paid Amount

Test Environment / Apps Platform SANDBOX / ANDROID

Conducted on PT DIMO Pay Indonesia <Issuer legal name>

ITC 022 / Maximum Redeem Discount Amount

Test Environment / Apps Platform SANDBOX / ANDROID