Amex Virtual Payment Client Example

Dialect
Payments

PHP VPC 2-Party Auth & Capture Transaction

Simply input those required fields to change the functionality.

Virtual Payment Client URL: 
 
 

 Basic 2-Party Transaction Fields

VPC Version:
Command Type:
Merchant AccessCode:
Merchant Transaction Reference:
MerchantID:
Transaction OrderInfo:
Purchase Amount:
Card Number:
Card Expiry Date (YYMM):
 
 
 
 

 Optional Card Security Code Field

Card Security Code:
 
 

 Optional Transaction Source and Transaction Source Sub Type Fields

If no Transaction Source or Transaction Source Sub Type is selected,
the default values on the Merchant Profile will be used by the Payment Server.
Transaction Source:
Transaction Source Sub Type:
 
 

 Optional Ticket Number Field

TicketNo:
 
 

 Optional Extended Address Verfication Service Fields

Billing Title:
Billing Firstname:
Billing Middlename:
Billing Lastname:
Billing Phone Number:
Billing Street/PO Box Address: (Compulsory field if using AVS)
Billing City/Town:
Billing State/Province:
Billing Zip/Post Code: (Compulsory field if using AVS)
Billing Country of Issue:
Ship-To Fullname:
Ship-to Title:
Ship-to Firstname:
Ship-to Middlename:
Ship-to Lastname:
Ship-to Phone Number:
Ship-to Street/PO Box Address:
Ship-to City/Town:
Ship-to State/Province:
Ship-to Zip/Post Code:
Ship-to Country of Issue:
 
 

 Optional Airline Passenger Data Fields

You cannot send both (APD and ITD) together for a single transaction. One or the other, but not both.
An error will be thrown it you try and send both.
Departure Date:
Passenger Title:
Passenger Firstname:
Passenger Middlename:
Passenger Lastname:
Cardmember Title:
Cardmember Firstname:
Cardmember Middlename:
Cardmember Lastname:
Origin:
Destination:
Routing Cities:
Airline Carriers:
Fare Basis:
Number of Passengers:
E-Ticket Indicator:
Reservation Code:
IATA (Travel Agent Code):
 
 

 Optional Internet Source Data Fields

You cannot send both (APD and ITD) together for a single transaction. One or the other, but not both.
An error will be thrown it you try and send both.
Customer Email:
Customer Hostname:
Http Browser Type:
Shipping Method Code:
Ship To Country Code:
Merchant Product SKU (Stock Keeping Unit):
Customer IP Address:
Customer ANI (Automatic Number Identiciation):
Customer II Digitits (caller type code):
 
 

 Optional Card Present Fields

Transaction Source must be set to CARDPRESENT if providing Card Track data.
Card Track 1:

May also include LRC character.

Card Track 2:

May also include LRC character.

 
 

Note:
Any information passed through the customer's browser can potentially be modified by the customer, or even by third parties to fraudulently alter the transaction data. Therefore all transactional information should not be passed through the browser in a way that could potentially be modified (e.g. hidden form fields). Transaction data should only be accepted once from a browser at the point of input, and then kept in a way that does not allow others to modify it (e.g. database, server session, etc.). Any transaction information displayed to a customer, such as amount, should be passed only as display information and the actual transactional data should be retrieved from the secure source last thing at the point of processing the transaction.

Fields like return links back to the order page (AgainLink), titles, (sockets' data when applicable), and any other non-transactional information are only included here in the example for information purposes. They do not apply to the transaction and should not be included in production code orders.