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
Testing Transactions
Processors Other Than PayPal
7
92 07 January 2014 Gateway Developer Guide and Reference
Testing Card Security Code
If you submit a value for the card security code, the cardholder’s bank returns a Yes / No / Not
Supported (Y / N / X) response on whether the value matches the number on file at the bank.
Card security code is described in “Card Security Code Validation”.
NOTE: Some processors will decline (RESULT value 12) a transaction if the card
security code does not match without returning a CVV2MATCH value. Test the
results and check with your processor to determine whether they support card
security code checking.
For the testing server, the first three characters of the CVV2 value determine the CVV2MATCH
result, as shown here.
Testing CVV2MATCH
Testing the Litle Automatic Account Updater Feature
The Litle Automatic Account Updater feature identifies outdated card information, “repairs”
it, and substitutes new card information before submitting the transaction to the network. See
the “Litle Automatic Account Updater” on page 113 section for more information.
Merchants utilizing this feature should check for the presence of the CCUPDATED=Y response
parameter, and if it is returned, should also check for the presence of the ACCT and EXPDATE
response parameters to determine what card information has been updated.
Merchants can test their integration for the Litle Automatic Account Updater feature in the
Payflow pilot test environment by doing the following.
1. In the ACCT request parameter, pass one of the following testing card numbers:
NOTE: Only the last 4-digits of the updated credit card number will be returned.
CVV2 Value CVV2MATCH Value
000 Y
001-300 Y
301-600 N
601 or higher X
Card number passed in ACCT request parameter
Updated card number returnedin ACCT
response parameter
4111111111111111 4321432143214321
4012888888881881 4012000033330026
5105105105105100 5454545454545454
5560136761278244 5105105105105100