MTN OPEN API Integration Test

TC# Test case

01. Registration

TC01-01 SignUp Create a New API Manager Account

TC01-02 Product Subscription Subscribeto a product

02. Authentication
Generate an API User
TC02-01 API User Provisioning POST
Generate an API User
TC02-02 API Key Use Provisioning POST
Generate Bearer Token using Invalid
Subscription key

TC02-03 OAUTH 2.0 POST

Generate Bearer Token using Invlaid
API Key

TC02-04 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.

TC02-05 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.
TC02-06 OAUTH 2.0 POST

TC02-07 Authentication POST Autheticate using Oauth

TC02-08 Authentication POST Autheticate using Oauth

TC02-09 Authentication POST Autheticate using Oauth

TC02-10 Certificate management POST Test transaction over https portal

TC02-11 Certificate management POST Test transaction over http portal

EN API Integration Test
Objective Expected Results

Follow https://momodeveloper.mtn.com link

and fill in the required Info SignUp Successful
Click on Product Tab and Subscribe to a User is assigned a
Package subscrition Key

To generate an API User using the

Porvisioning API on Sanbox
To Generate an API Key using the Provisioning
API
Invalid Subscription key
Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use Invalid
Subscription Key

Invalid API User Key

Generate OAUTH Token using Sanbox OAUTH
API using Invalid base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key

Valid Subscription Key & API Key

Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key
Generate Second Token
Test if generation of a second Token before
the First Token Expiry

Successful Authentication isung First Token

To test successful authentication using First
Oauth token

Successful Authentication using Second

Token
To test successful authentication using
Second Oauth token
Wrong Token
Use Wrong token to send a transaction
To test successful request sent over https on
the portal

To test request sent over http on the portal

Actual Results Notes
 MTN OPEN API Integration Test
TC# Test case
01. Authentication
Generate Bearer Token using Invalid
Subscription key

TC01-01 OAUTH 2.0 POST

Generate Bearer Token using Invlaid
API Key

TC01-02 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.

TC01-03 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.
TC01-04 OAUTH 2.0 POST
02. Transactions

TC02-01 RequestToPay POST No Exceptions- Subscriber Approves

TC02-02 RequestToPay POST No Exceptions- Subscriber Rejects

TC02-03 RequestToPay POST No Exceptions- Approval Timeout

TC02-04 RequestToPay POST Duplicate Reference ID

TC02-05 RequestToPay POST Incomplete Information

TC02-06 RequestToPay POST Insufficient Funds

TC02-07 RequestToPay POST Invalid B-Party

TC02-08 RequestToPay POST Exceed Daily Limit

TC02-09 RequestToPay POST Invalid Subscription Key

TC02-10 RequestToPay POST Invalid Target Environment

TC02-11 RequestToPay POST Invalid OAUTH Token

TC02-12 RequestToPay GET No Exception

TC02-13 RequestToPay GET Invalid Refernce ID
TC02-14 RequestToPay GET Invalid Subsciption key

TC02-15 RequestToPay GET Invalid Target Environment

TC02-16 RequestToPay GET Invalid OAUTH Token
EN API Integration Test
Objective Expected Results

Invalid Subscription key

Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use Invalid
Subscription Key

Invalid API User Key

Generate OAUTH Token using Sanbox OAUTH
API using Invalid base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key

Valid Subscription Key & API Key

Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key
Generate Second Token
Test if generation of a second Token before
the First Token Expiry

Send Request as per API specification

Send Request as per API specification

Send Request as per API specification

Send Request with Duplicate reference ID

Omit Currency or Amount from Request
Send a Debit Amount greater that Payer
Available balance
Send Request with Invalid B-Party
Send Request that exceeds Daily Limits on
Profile

Send Request with Invalid Subscription Key

Send Request with Invalid target Environment

Send Request with Invalid OAUTH Token

Fetch status of a valid Refernce ID

Fetch status of a Invalid Refernce ID
Send Request with Invalid Subscription Key

Send Request with Invalid target Environment

Send Request with Invalid OAUTH Token

SIGNATURE

SIGNATURE
Actual Results ReferenceID Notes
E

SIGNATURE
 MTN OPEN API Integration Test
TC# Test case
01. Authentication
Generate Bearer Token using Invalid
Subscription key

TC01-01 OAUTH 2.0 POST

Generate Bearer Token using Invlaid
API Key

TC01-02 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.

TC01-03 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.
TC01-04 OAUTH 2.0 POST
02. Transactions
TC02-01 Transfer POST No Exceptions

TC02-02 Transfer POST Duplicate Reference ID

TC02-03 Transfer POST Incomplete Information

TC02-04 Transfer POST Insufficient Funds

TC02-05 Transfer POST Invalid B-Party

TC02-06 Transfer POST Exceed Daily Limit

TC02-07 Transfer POST Invalid Subscription Key

TC02-08 Transfer POST Invalid Target Environment

TC02-09 Transfer POST Invalid OAUTH Token

TC02-10 Transfer GET No Exception

TC02-11 Transfer GET Invalid Refernce ID

TC02-12 Transfer GET Invalid Subsciption key

TC02-13 Transfer GET Invalid Target Environment

TC02-14 Transfer GET Invalid OAUTH Token
EN API Integration Test
Objective Expected Results

Invalid Subscription key

Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use Invalid
Subscription Key

Invalid API User Key

Generate OAUTH Token using Sanbox OAUTH
API using Invalid base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key

Valid Subscription Key & API Key

Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key
Generate Second Token
Test if generation of a second Token before
the First Token Expiry

Send Request as per API specification

Send Request with Duplicate reference ID

Omit Currency or Amount from Request
Send an Amount greater that Sender
Available balance
Send Request with Invalid B-Party
Send Request that exceeds Daily Limits on
Profile

Send Request with Invalid Subscription Key

Send Request with Invalid target Environment

Send Request with Invalid OAUTH Token

Send Request as per API specification

Fetch status of a Invalid Refernce ID

Send Request with Invalid Subscription Key

Send Request with Invalid target Environment

Send Request with Invalid OAUTH Token
Actual Results ReferenceID Notes
SIGNATURE
 MTN OPEN API Integration Test
TC# Test case
01. Authentication
Generate Bearer Token using Invalid
Subscription key

TC01-01 OAUTH 2.0 POST

Generate Bearer Token using Invlaid
API Key

TC01-02 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.

TC01-03 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.
TC01-04 OAUTH 2.0 POST
02. Transactions
TC02-01 ACTIVE GET No Exception
TC02-02 ACTIVE GET Invalid AccountHolderType
TC02-03 ACTIVE GET Invalid AccountHolderID
TC02-04 ACTIVE GET Invalid Subsciption key
TC02-05 ACTIVE GET Invalid Target Environment
TC02-06 ACTIVE GET Invalid OAUTH Token
EN API Integration Test
Objective Expected Results

Invalid Subscription key

Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use Invalid
Subscription Key

Invalid API User Key

Generate OAUTH Token using Sanbox OAUTH
API using Invalid base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key

Valid Subscription Key & API Key

Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key
Generate Second Token
Test if generation of a second Token before
the First Token Expiry

Send reqeust as per API specification

Use Invalid AccountType
Use Invalid AccountID
Use Incalid Subscription key
Set Invalid target Environment
Use Invalid Token
Actual Results Notes
 MTN OPEN API Integration Test
TC# Test case
01. Authentication
Generate Bearer Token using Invalid
Subscription key

TC01-01 OAUTH 2.0 POST

Generate Bearer Token using Invlaid
API Key

TC01-02 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.

TC01-03 OAUTH 2.0 POST

Generate Bearer Token with valid
API key and Subscription Key.
TC01-04 OAUTH 2.0 POST
02. Transactions
TC02-01 Balance GET No Exception
TC02-02 Balance GET Invalid AccountHolderType
TC02-03 Balance GET Invalid AccountHolderID
TC02-04 Balance GET Invalid Subsciption key
TC02-05 Balance GET Invalid Target Environment
TC02-06 Balance GET Invalid OAUTH Token
EN API Integration Test
Objective Expected Results

Invalid Subscription key

Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use Invalid
Subscription Key

Invalid API User Key

Generate OAUTH Token using Sanbox OAUTH
API using Invalid base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key

Valid Subscription Key & API Key

Generate OAUTH Token using Sanbox OAUTH
API using base64 Encoded
APIUserkey:APIsecret. Use a valid
Subscription Key
Generate Second Token
Test if generation of a second Token before
the First Token Expiry

Send reqeust as per API specification

Use Invalid AccountType
Use Invalid AccountID
Use Incalid Subscription key
Set Invalid target Environment
Use Invalid Token
Actual Results Notes