Certification Testing

Document created by gjsissons on Aug 2, 2016Last modified by gjsissons on Aug 2, 2016
Version 4Show Document
  • View in full screen mode

The certification testing you need to perform depends upon the integration method you implement. This section provides information about the required tests for the eProtect integration method.

 

Testing Android Pay using eProtect

 

In this integration method, your application submits information to the Google test environment, receives a low-value token, and then submits the low value token to Vantiv in a normal payment

 

NOTE: At this time, we are unable to support end-to-end testing in our Pre-Live environment for Android Pay using eProtect option. Low-value tokens returned from Google are generated independently by their test environment. As a result, all transactions submitted using a low-value token returned by Google result in a response message containing the Reason Code 878 - Expired PayPage Registration Id. These test allow you to verify your submission of well formed XML conforming to the schema files.

 

1. Perform an implicit token registration by submitting a Sale or Authorization transaction using the data shown for the androidpay_1 (orderId) transaction in Table 1.

2. Verify the response message includes the key Response values shown.

3. Perform an explicit token registration by submitting a Register Token Request using the data shown for the androidpay_2 (orderId) transaction in Table 1.

4. Verify the response message includes the key Response values shown.

 

TABLE 1 Android Pay using eProtect Test Data

 

orderIdSupplied Data ElementSupplied Data Element ValueResponse ElementResponse Element Value
androidpay_1

<orderSource>

<paypageRegistrationId>

androidpay

Value returned from Google

<response>

<message>

878

Expired Paypage registration Id

androidpay_2<paypageRegistrationId>

alue returned from

Google

<response>

<message>

878

Expired Paypage registration Id

 

 

Example: Implicit Token Registration via Authorization Transaction

 

<litleOnlineRequest version="10.2" xmlns="http://www.litle.com/schema" merchantId="100">
     <authentication>
          <user>User Name</user>
          <password>Password</password>
     </authentication>
     <authorization id="834262" reportGroup="ABC Division" customerId="038945">
          <orderId>androidpay_1</orderId>
          <amount>40000</amount>
          <orderSource>androidpay</orderSource>
          <paypage>
               <paypageRegistrationId>Low-Value Token</paypageRegistrationId>
          </paypage>
     </authorization>
</litleOnlineRequest>

 

 

Example: Explicit Token Registration Transaction

 

<litleOnlineRequest version="10.2" xmlns="http://www.litle.com/schema" merchantId="100">
     <authentication>
          <user>User Name</user>
          <password>Password</password>
     </authentication>
     <registerTokenRequest id="99999" reportGroup="RG1">
          <orderId>androidpay_2</orderId>
          <paypageRegistrationId>Low-Value Token</paypageRegistrationId>
     </registerTokenRequest>
</litleOnlineRequest>

 

 


Previous: Merchant Decryption Method

Attachments

    Outcomes