Page Comparison

Setup 2 cases for Pronto,

1. Pronto with Loyalty: return Loyalty ID "7147616368
2. Pronto with no Loyalty : SW 9001

because we get "9001" or "9102" from Pronto CX(which provided from customer), and we validated the result:

...

so I got SW 9102 becasue I do not setup a credit card in my Androidpay.

test with Terminal App and Merchant App

1. To setup the information which provide from Pronto to Terminal app
   1. Download Pronto.json to Android phone
   2. open Terminal app
      Image Removed
   3. click the setting symbol in the uppper right corner
   Image RemovedImage Removed
   1. click LOAD
   2. Image Removed
   3. get the Pronto.json file 
      Image Removed
   4. go back to Terminal App
      Image Removed
2. To setup the information which provide from Pronto to Merchant app
   1. Download test-cases-Pronto.json to Android phone
   2. click Merchant App
      Image Removed
   3. click setting symbol in the upper left corner
      Image Removed
   4. click LOAD TEST SUITE and load test-cases-Pronto.json
   5. create
      Image RemovedImage Removed
   6. long press to AVTIVATE test case
      Image Removed
3. tapping Merchant App to Terminal App, 2 app would show log.
   1. Pronto with Loyalty, SW = 9000
      Image RemovedImage Removed
   2. Pronto with nothing. SW = 9001
      Image RemovedImage Removed
4. Pronto may need to setup some information for their pass, for example, I setup the Loyalty ID in Merchant App and I could read it back(SW 9000).
   Image Removed

Task 1 Create Google Private Key

Download drive-download-20180207T222536Z-001.zip and extract to drive C:\CS-1630\20180208

and it should look like this

Image Removed

and there are 2 PEM file in drive-download-20180207T222536Z-001\

Image Removed

...

C:\Users\Richard Cheng>cd c:\

c:\>cd "Program Files (x86)"

c:\Program Files (x86)>cd GnuWin32

c:\Program Files (x86)\GnuWin32>cd bin

c:\Program Files (x86)\GnuWin32\bin>openssl.exe ec -noout -text -in "c:\CS-1630\20180208\drive-download-20180207T222536Z-001\PRIVATE.key.pem"

Image Removed

There are 2 part in this private key, and we need to load priv part to reader, 

RSA Private Key:

...

RSA Public Key:

...

RSA Exp:

...

Long term private key

...

Padding “00” + Version(ex. 00 00 00 01) + Long term private key to 256 bytes data

...

Calculate SHA-256 for data

...

Append encrypt data and sha-256 data

...

IDG Command

...

Task 2 Create Pronto Private Key

Download pronto.key.zip and extract to drive C:\CS-1630\20180208

and it should look like this

Image Removed

and there are 2 PEM file in pronto.key\

Image Removed

open command line tool, and change path

C:\Users\Richard Cheng>cd c:\

c:\>cd "Program Files (x86)"

c:\Program Files (x86)>cd GnuWin32

c:\Program Files (x86)\GnuWin32>cd bin

c:\Program Files (x86)\GnuWin32\bin>openssl.exe ec -noout -text -in "c:\CS-1630\20180208\pronto.key\pronto-PRIVATE.key.pem"

Image Removed

There are 2 part in this private key, and we need to load priv part to reader, 

RSA Private Key:

...

RSA Public Key:

...

RSA Exp:

...

Long term private key

...

Calculate SHA-256 for data

...

...

Append encrypt data and sha-256 data

...

IDG Command

...

Test test-cases2074294809.json with Terminal App case 0.3

1. Download Terminal configuration file terminal_configs.7z to Android phone, which used to as Terminal.

2. Click Terminal App → Setting → Click "LOAD" → go to direction where store Terminal configuration file → serch for 0.3.json → clikc OK

   → scroll down, change Merchant ID to 50248994(if need) and check Long term private key, which should be same as the priv we use openssl to read PEM file(Google's or Pronto's) → return to Terminal App → tapping new pass
   → SW 9102.

   Image RemovedImage RemovedImage RemovedImage RemovedImage RemovedImage RemovedImage Removed

   Image RemovedImage Removed

3. Change LTPK to Pronto's, Terminal APP → Setting → scroll down to LTPK → click LTPK → "LOAD KEY FROM FILE" → select Pronto' s PEM file → SAVE → tapping new pass → SW 9102.

Image RemovedImage RemovedImage RemovedImage RemovedImage RemovedImage RemovedImage RemovedImage Removed

Suggenstion

To validate customer' s pass via Terminal App is a best way. If Terminal App could read data and get SW 9000, that means VP3300 should get same data.

One more thing should be notice is, test case 0.3 need to do negotiate with pass, so we could read log from Terminal App, and knwo SW of Negotiate is 9500(Authorization failed).

I think customer and Google may use Terminal App and pass to read something back successfully first, then set the same configuratioin to VP3300 and read pass.

If Terminal App success but VP3300 fail, then we fix it.