Developer's Guide
Table Of Contents
- Content
- Preface
- Introducing the Gateway Checkout Solutions
- Secure Token
- Configuring Hosted Checkout Pages
- Payflow SDK
- Sending a Simple Transaction to the Server
- Submitting Credit Card Transactions
- Obtaining an Internet Merchant Account
- About Credit Card Processing
- Credit Card Features
- Planning Your Gateway Integration
- Core Credit Card Parameters
- Submitting Account Verifications
- Submitting Authorization/Delayed Capture Transactions
- Submitting Balance Inquiry Transactions
- Submitting Card Present (SWIPE) Transactions
- Submitting Credit (Refund) Transactions
- Submitting Inquiry Transactions
- When To Use an Inquiry Transaction
- Required Parameters When Using the PNREF
- Inquiry Transaction Parameter String Using the PNREF
- Required Parameters When Using the CUSTREF
- Inquiry Transaction Parameter String Using the CUSTREF
- Required Parameters When Using the Secure Token
- Inquiry Parameter String Using the Secure Token
- Submitting Partial Authorizations
- Submitting Purchasing Card Transactions
- Submitting Reference Transactions (Tokenization)
- Submitting Sale Transactions
- Submitting Soft Merchant Information
- Submitting Voice Authorization Transactions
- Submitting Void Transactions
- Using Address Verification Service
- Using Card Security Code
- Information for the PayPal Acquirer
- Testing Transactions
- Transaction Responses
- Processors Requiring Additional Transaction Parameters
- American Express Additional Credit Card Parameters
- Elavon Additional Credit Card Parameters
- First Data Merchant Services Nashville, Additional Credit Card Parameters
- First Data Merchant Services North, Additional Credit Card Parameters
- Heartland, Additional Credit Card Parameters
- Litle Additional Credit Card Parameters
- Cielo Payments, Additional Credit Card Parameters
- Paymentech Salem (New Hampshire) Additional Credit Card Parameters for American Express
- PayPal Credit Card Transaction Request Parameters
- SecureNet Additional Credit Card Parameters for American Express
- Vantiv Additional Credit Card Parameters
- WorldPay Additional Credit Card Parameters
- TeleCheck Electronic Check Processing
- Payflow Header Parameters
- Submitting Purchasing Card Level 2 and 3 Transactions
- About Purchasing Cards
- About Program Levels
- About American Express Purchasing Card Transactions
- American Express Purchasing Card Transaction Processing
- Elavon (Formerly Nova) Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) Nashville Purchasing Card Transaction Processing
- First Data Merchant Services (FDMS) North Purchasing Card Transaction Processing
- First Data Merchant Services South (FDMS) Purchasing Card Transaction Processing
- Global Payments - Central Purchasing Card Transaction Processing
- Global Payments - East Purchasing Card Transaction Processing
- Heartland Purchasing Card Transaction Processing
- Litle Purchasing Card Transaction Processing
- Cielo Payments Purchasing Card Transaction Processing
- Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
- Paymentech Tampa Level 2 Purchasing Card Transaction Processing
- SecureNet Purchasing Card Transaction Processing
- TSYS Acquiring Solutions Purchasing Card Transaction Processing
- Vantiv Purchasing Card Transaction Processing
- WorldPay Purchasing Cards Transaction Processing
- VERBOSITY: Processor-Specific Transaction Results
- Country Codes
- Codes Used by FDMS South Only
- Additional Processor Information
- Payflow Link Migration
- Payflow Gateway MagTek Parameters
- Payflow Gateway FAQs
Submitting Credit Card Transactions
Using Address Verification Service
6
84 07 January 2014 Gateway Developer Guide and Reference
Example Void Transaction Parameter String
The following is an example void transaction string:
TRXTYPE=V&TENDER=C&PARTNER=PayPal&VENDOR=SuperMerchant&USER=SuperMerchant&P
WD=x1y2z3&ORIGID=VPNE12564395&VERBOSITY=HIGH
Using Address Verification Service
To qualify for the lowest bank rate, pass address verification service information, including the
street address and zip (postal) code.
Address verification service compares the submitted billing street address and zip code with
the values on file at the cardholder’s bank. The response includes values for AVSADDR and
AVSZIP: Y, N, or X for the match status of the customer’s street address and zip code.
Y = match, N = no match, X = cardholder’s bank does not support address verification service.
The address verification service result is for advice only. Banks do not decline transactions
based on the address verification service result. The merchant decides to approve or decline a
transaction. Most US banks and some international banks support the address verification
service.
NOTE: Address verification service checks only for a street number match, not a street name
match, so
123 Main Street returns the same response as 123 Elm Street.
The international address verification service (IAVS) response indicates whether the address
verification service response is international (Y), USA (N), or cannot be determined (X).
NOTE: When you set VERBOSITY to HIGH, the Gateway returns the processor’s raw response
in the
PROCAVS field. To obtain details about the meaning of the response, contact
your merchant bank.
Example Address Verification Service Parameter String
This example request includes the address verification service parameters BILLTOSTREET
and BILLTOZIP:
TRXTYPE=A&TENDER=C&PWD=SuperUserPassword&PARTNER=PayPal&VENDOR=Vendor&USER=
SuperMerchant&&ACCT=5555555555554444&EXPDATE=1215&AMT=123.00&BILLTOSTREET=5
199
Maple&BILLTOZIP=98765
In this example response, the address value matches the value in the bank's records, but the
zip code does not. The AVSZIP response is N.
RESULT=0&PNREF=VXW412345678&RESPMSG=APPROVED&AUTHCODE=123456&AVSADDR=Y&AVSZ
IP=N&IAVS=X