Overview

The Virtual Pin Pad (VPP) can be used for testing the Customer-Present Cloud API without a device. To do so, use our virtual registration codes which can be submitted to any test gateway account or gateway account that is in test mode. Keep in mind that if an account is in test mode, no actual credit card processing will take place. The VPP will simulate a Visa EMV transaction for the purposes of transaction processing and reporting visibility.

Transaction Testing Credentials

The Payment Gateway demo account can also be used for testing at any time. Please use the following api-key for testing with this account:

api-key = 2F822Rw39fx762MaV7Yy86jXGTC7sCDy

Registration

VPP Registration requests are submitted with the same API calls as a registration request for a physical device, but using the following special registration codes:

Successful Registration	Failed Registration
T00001	T00002

All GUIDs returned associated with the VPP (including POI Device IDs and Asynchronous Transaction GUIDs) will always end in 12 zeroes. This will be an indicator that the transaction is a ‘test’ transaction since this will never occur in a live environment.

For example: 3915af04-29fa-49df-88d0-000000000000

Registration requests using T00001 will return a virtual (fake) POI Device ID which can be used to process test payments and will appear in estate management polling requests. This POI Device ID can also be used to simulate deregistration of an EMV terminal.

Processing

The POI Device IDs returned via VPP registration can be used in both synchronous or asynchronous processing requests.

Process an approved transaction	Process a declined transaction
Send an amount greater than or equal to 1.00	Send an amount less than 1.00

When using Synchronous processing, you can expect to wait a few seconds before receiving a response. The VPP does not simulate the full five (5) minute wait time, but you will want to plan ahead to expect longer wait times for customer interaction.

VPP AsyncStatus GUIDs will only simulate an immediate ‘interactionComplete’ response versus remaining ‘inFlight’ for customer interaction.

If you would like to test Customer Vault interaction with VPP, simply send the standard Customer Vault action variables along with your transaction request.

Transaction Contents for VPP Transactions

Card Brand: Visa
Card Number: 4111111111111111
Expiration Date: 0229
Full Name: JOHN SMITH
- Cardholder Verification Method: Pin Entered
- Application ID: A0000000031010
- Application Label: VISA CREDIT
- Application Preferred Name: CREDITO DE VISA
- Transaction Status Info: E800
- PAN Sequence Number: 01
- Masked MID: XXXXXXXXXX1234
- Auth Code: 123456

Deregistering VPP devices

The POI Device ID can be used to deregister the VPP device - exactly like a real POI Device ID.

Triggering Errors in Test Mode

To cause a declined response, pass an amount less than 1.00.
To trigger a fatal error message in processing, pass an invalid POI Device ID.
To cause an unknown AsyncStatus GUID, pass an invalid GUID.
To cause an empty Estate Management response, pass an invalid GUID.

See Registration and Deregistration, Estate Management, Transaction Processing, and AsyncStatus API documentation for more information on these concepts.

VPP does not support handling POI device prompts at this time, though sending the variables in your request will not cause errors. These prompts require interaction with a physical device though have very little effect on the final responses or API calls.