Asoft IPG: Merchant Integration Compliance Verification Document

Asoft IPG
Merchant Integration Compliance

Verification Document
Version <1.2>
This is the official document of ArsBlue d.o.o company, with ArsBlue copyright (in written and electronic form). Unauthorized using, copying,
trading or publishing in original or modified is strictly forbidden.
AsoftIPG - Merchant Integration Compliance Verification Document
_____________________________________________________________________________
Contents
1. Introduction..................................................................................................................................3
2. Compliance verification...............................................................................................................3
3. Test case scenarios.......................................................................................................................3
3.1. Test case n°1 – Successful e-commerce purchase................................................................4
3.2. Test case n°2 – Non-authorized e-commerce purchase........................................................5
3.3. Test case n°3 – Issuer is not available..................................................................................6
3.4. Test case n°4 – Purchase request contains invalid card number...........................................7
3.5. Test case n°5 – Purchase canceled by buyer.........................................................................8
Appendix A – Testing Results Form...............................................................................................9
Appendix B - Screenshot Samples.................................................................................................10
Test case n°1 – Successful e-commerce purchase.....................................................................10
Test case n°2 – Non-authorized e-commerce purchase.............................................................12
Test case n°3 – Issuer is not available.......................................................................................14
Test case n°4 – Purchase request contains invalid card number................................................16
Test case n°5 – Purchase canceled by buyer..............................................................................18
______________________________________________________________________________
Confidential 2
_____________________________________________________________________________
1. Introduction
This document outlines the policies, procedures and processes for merchant integration
compliance verification.
2. Compliance verification
Successful completion of compliance testing specified in this document indicates that merchant
is successfully integrated and that it is interoperable with the AsoftIPG (Asoft Internet Payment
Gateway).
After the completion of compliance testing, the merchant has to provide to ArsBlue filled Test
Result Form (see Appendix A) and also include screen captures for verification (see Appendix
B).
3. Test case scenarios
The test cases presented in this document should be performed by merchant in order to verify the
integration with AsoftIPG.
Each Test Case contains the steps that need to be performed, as well as data to be used (card
numbers, Expiration date, CVV values, etc.) in order to receive positive test case results.
______________________________________________________________________________
Confidential 3
_____________________________________________________________________________
3.1. Test case n°1 – Successful e-commerce purchase

Purpose
Demonstrate successful processing of an e-commerce purchase request.
Expected Processing and Results
Step
No. Description
1 Create valid e-commerce purchase order on merchant site.
2 AsoftIPG validates purchase order request and displays:
- Payment Method Selection Page (SPP), if the merchant supports various payment methods, or
- Hosted Payment Page (HPP), if the merchant supports Credit Card payment method only.
3 (only if SPP Page is displayed) Select Credit Card payment method. AsoftIPG displays HPP page.
4 Create payment request on HPP.
The content of the request has to be as follows:
- Card Number: 4012001037141112;
- Cardholder’s Name: <arbitrary value>;
- Expiration Date: 12/2017;
- CVV2/CVC2: 002.
5 AsoftIPG validates payment request and performs 3D Secure Authentication procedure using
VISA PIT test environment. As result 3D Secure PARes message is displayed.
6 Press Submit button to confirm PARes message.
7 AsoftIPG sends authorization request to the Host.
8 AsoftIPG receives authorization response from the Host.
9 AsoftIPG sends Notification message to the merchant.
10 Merchant receives Notification message. Expected content of the message has to be as follow:
- Message Date: <message date and time>;
- Result Code: CAPTURED;
- Reference ID: <value generated by AsoftIPG>
- Authorization Code: <value generated by authorization center>
- Order ID: <value generated by AsoftIPG>
- Transaction ID: <value generated by AsoftIPG>
- Currency: <equal to currency submitted in purchase request>;
- Amount: <equal to amount submitted in purchase request>;
- Card Type: VISA;
- Payment Instrument: VPAS;
- Card Last 4 Digits: 1112;
- Card Expiration Date: 201712;
- Liability: Y;
- Host Response Code: 78.
11 Appropriate result page is displayed on merchant site.
______________________________________________________________________________
Confidential 4
_____________________________________________________________________________
3.2. Test case n°2 – Non-authorized e-commerce purchase

Purpose
Demonstrate successful processing of a non-authorized e-commerce purchase request.
Ste
p Description
No.
The content of the request has to be as follow:
- Card Number: 4539990000000020;
- CVV2/CVC2: 112.
5 AsoftIPG validates payment request and sends authorization request to the Host.
6 AsoftIPG receives authorization response from the Host.
- Result Code: NOT CAPTURED;
- Authorization Code: <value generated by Host>
- Card Type: VISA;
- Payment Instrument: CC;
- Liability: N;
- Host Response Code: 51.
______________________________________________________________________________
Confidential 5
_____________________________________________________________________________
3.3. Test case n°3 – Issuer is not available
Purpose
Demonstrate successful processing of an e-commerce purchase request when issuer is not

available for request authorization.
Step
No. Description
Payment Method Selection Page (SPP), if the merchant supports various payment methods, or
Hosted Payment Page (HPP), if the merchant supports Credit Card payment method only.
- Card Number: 4539990000005557;
- CVV2/CVC2: 333.
5 AsoftIPG validates payment request and sends authorization request to the Host.
6 No response is received from the Host.
- Result Code: ISSUER UNAVAILABLE;
- Authorization Code:
- Card Type: VISA;
- Payment Instrument: CC;
- Liability: N;
- Host Response Code:
______________________________________________________________________________
Confidential 6
_____________________________________________________________________________
3.4. Test case n°4 – Purchase request contains invalid card number
Purpose
Demonstrate processing of an e-commerce purchase request which contains invalid card number.
Ste
p Description
No.
1 Create e-commerce purchase order on merchant site.
- Card Number: 4999000055550000;
- CVV2/CVC2: 222.
5 AsoftIPG validates payment request and performs 3D Secure Authentication procedure using VISA
PIT test environment. As result 3D Secure PARes message with Transaction Status set to 'N' is
displayed.
6 Press Submit button to confirm PARes message.
- Order ID: <value generated by AsoftIPG>;
- Error Code: GW00853;
- Error Description: Invalid Card Number.
9 Appropriate message is displayed on merchant site.
______________________________________________________________________________
Confidential 7
_____________________________________________________________________________
3.5. Test case n°5 – Purchase canceled by buyer

Purpose
Demonstrate processing of an e-commerce purchase request when customer opts-out of buying.
Ste
p Description
No.
3
Press Cancel button to opt-out of buying.
4
AsoftIPG sends Notification message to the merchant.
- Order ID: <value generated by AsoftIPG>;
- Error Code: PY20090;
- Error Description: Customer canceled transaction.
6 Appropriate message is displayed on merchant site.
______________________________________________________________________________
Confidential 8
_____________________________________________________________________________
Appendix A – Testing Results Form
Integration Testing Results Form for Merchant
Contact Information
Company Name:
Contact Name:
Email:
Phone Number:
Merchant Application Name/Version:
Test Case Results

Test Cases Completion Status
Case n°1 Successful e-commerce purchase Successful Failed
Case n°2 Non-authorized e-commerce purchase Successful Failed
Case n°3 Issuer is not available Successful Failed
Case n°4 Purchase request contains invalid card number Successful Failed
Case n°5 Purchase canceled by buyer Successful Failed
Please provide the reason for any failed test scripts
Test Case Screenshots

Test Cases Completion Status
Case n°1 Successful e-commerce purchase Included Not Included

Case n°2 Non-authorized e-commerce purchase Included Not Included
Case n°3 Issuer is not available Included Not Included
Case n°4 Purchase request contains invalid card number Included Not Included
Case n°5 Purchase canceled by buyer Included Not Included
Please provide the reason for any missed screenshots

Authorized Company Representative Signature Date

______________________________________________________________________________
Confidential 9
_____________________________________________________________________________
Appendix B - Screenshot Samples
Screen shot samples for required test cases are presented.
Test case n°1 – Successful e-commerce purchase
Step 1.
Screen shot of purchase request created on merchant’s site:
Step 4. Screen Shot of AsoftIPG HPP page:
______________________________________________________________________________
Confidential 10
_____________________________________________________________________________
Step 11. Screen shot of result page on merchant’s site:
Note: Data source for above screenshot is PaymentNotificationRequest message as following:
Date Time: <msgDateTime>

Order Number: <trackid>
Total Price: <currencycode> + <amt>
Payment ID: <paymentid>
Transaction ID: <tranid>
Authorization Code: <auth>
Reference ID: <ref>
Response Code: <responsecode>
______________________________________________________________________________
Confidential 11
_____________________________________________________________________________
Test case n°2 – Non-authorized e-commerce purchase
Step 1. Screen shot of purchase request created on merchant’s site:
______________________________________________________________________________
Confidential 12
_____________________________________________________________________________
Rejection reason is derived from Response Code value.

Authorization Code: <auth>
Reference ID: <ref>
Response Code: <responsecode>
______________________________________________________________________________
Confidential 13
_____________________________________________________________________________
Test case n°3 – Issuer is not available
______________________________________________________________________________
Confidential 14
_____________________________________________________________________________
Rejection reason is derived from Error Description value.

Reference ID: <ref>
______________________________________________________________________________
Confidential 15
_____________________________________________________________________________
Test case n°4 – Purchase request contains invalid card number
______________________________________________________________________________
Confidential 16
_____________________________________________________________________________

Error Code: <errorCode>
Error Description: <errorDesc>
______________________________________________________________________________
Confidential 17
_____________________________________________________________________________
Test case n°5 – Purchase canceled by buyer
______________________________________________________________________________
Confidential 18
_____________________________________________________________________________

Error Code: <errorCode>
Error Description: <errorDesc>
______________________________________________________________________________
Confidential 19

Asoft IPG: Merchant Integration Compliance Verification Document

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Asoft IPG: Merchant Integration Compliance Verification Document

Încărcat de

Drepturi de autor:

Formate disponibile

Asoft IPG

Merchant Integration Compliance

3. Test case scenarios

3.1. Test case n°1 – Successful e-commerce purchase

Demonstrate successful processing of an e-commerce purchase request.

Expected Processing and Results

3.2. Test case n°2 – Non-authorized e-commerce purchase

Demonstrate successful processing of a non-authorized e-commerce purchase request.

Expected Processing and Results

Demonstrate successful processing of an e-commerce purchase request when issuer is not

Expected Processing and Results

Expected Processing and Results

9 Appropriate message is displayed on merchant site.

3.5. Test case n°5 – Purchase canceled by buyer

Demonstrate processing of an e-commerce purchase request when customer opts-out of buying.

Expected Processing and Results

6 Appropriate message is displayed on merchant site.

Integration Testing Results Form for Merchant

Company Name:

Contact Name:

Phone Number:

Merchant Application Name/Version:

Test Case Results

Case n°1 Successful e-commerce purchase Successful Failed

Case n°2 Non-authorized e-commerce purchase Successful Failed

Case n°3 Issuer is not available Successful Failed

Case n°5 Purchase canceled by buyer Successful Failed

Please provide the reason for any failed test scripts

Test Case Screenshots

Case n°1 Successful e-commerce purchase Included Not Included

Authorized Company Representative Signature Date

Appendix B - Screenshot Samples

Screen shot samples for required test cases are presented.

Test case n°1 – Successful e-commerce purchase

Step 4. Screen Shot of AsoftIPG HPP page:

Step 11. Screen shot of result page on merchant’s site:

Note: Data source for above screenshot is PaymentNotificationRequest message as following:

Date Time: <msgDateTime>

Test case n°2 – Non-authorized e-commerce purchase

Step 1. Screen shot of purchase request created on merchant’s site:

Step 4. Screen Shot of AsoftIPG HPP page:

Step 9. Screen shot of result page on merchant’s site:

Note: Data source for above screenshot is PaymentNotificationRequest message as following:

Rejection reason is derived from Response Code value.

Test case n°3 – Issuer is not available

Step 1. Screen shot of purchase request created on merchant’s site:

Step 4. Screen Shot of AsoftIPG HPP page:

Step 9. Screen shot of result page on merchant’s site:

Note: Data source for above screenshot is PaymentNotificationRequest message as following:

Rejection reason is derived from Error Description value.

Test case n°4 – Purchase request contains invalid card number

Step 1. Screen shot of purchase request created on merchant’s site:

Step 4. Screen Shot of AsoftIPG HPP page:

Step 9. Screen shot of result page on merchant’s site:

Note: Data source for above screenshot is PaymentNotificationRequest message as following:

Rejection reason is derived from Error Description value.

Test case n°5 – Purchase canceled by buyer

Step 1. Screen shot of purchase request created on merchant’s site:

Step 3. Screen Shot of AsoftIPG HPP page:

Step 6. Screen shot of result page on merchant’s site:

Note: Data source for above screenshot is PaymentNotificationRequest message as following:

Rejection reason is derived from Error Description value.

S-ar putea să vă placă și