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
Gateway Developer Guide and Reference 07 January 2014 101
Transaction Responses
Address Verification Service Responses From PayPal
8
Address Verification Service Responses From PayPal
The following table compares the detailed response the PayPal processor returns for address
verification to the normalized response value (Y, N, or X) that AVSADDR and AVSZIP return. To
obtain the PayPal processor value, set the VERBOSITY parameter to HIGH. The processor
value is returned in the PROCAVS response parameter.
PAYMENTADVICECODE A processor response code typically returned on declined recurring transactions. Its
purpose is to provide merchants with information and specific instructions on how to
handle the decline. It is the merchant’s responsibility to follow the instructions
provided in order to avoid chargebacks.
For details on the meanings of these codes, see:
https://merchant.paypal.com/us/cgi-bin/?&cmd=_render-
content&content_ID=merchant/cc_compliance_error_codes
NOTE: If a recurring transaction is declined with a returned PAYMENTADVICECODE
value of
03 or 21, it is the merchant's responsibility to stop this recurring
transaction. These two codes indicate that either the account was closed,
fraud was involved, or the cardholder has asked the bank to stop this payment
for another reason. Even if a reattempted transaction is successful, it will
likely result in a chargeback.
TRANSSTATE State of the transaction sent in an Inquiry response. The values are:
0 = Account Verification (no settlement involved)
1 = General error state
3 = Authorization approved
4 = Partial capture
6 = Settlement pending (transaction is scheduled to be settled)
7 =Settlement in progress (transaction involved in a currently ongoing settlement)
8 = Settled successfully
9 = Authorization captured (once an authorization type transaction is captured, its
TRANSSSTATE becomes 9)
10 = Capture failed (an error occurred while trying to capture an authorization
because the transaction was already captured)
11 = Failed to settle (transactions fail settlement usually because of problems with
the merchant’s processor or because the card type is not set up with the merchant’s
processor)
12 = Unsettled transaction because of incorrect account information
14 = For various reasons, the batch containing this transaction failed settlement
15 = Settlement incomplete due to a charge back
16 = Merchant ACH settlement failed; (need to manually collect it)
106 = Unknown Status Transaction - Transactions not settled
206 = Transactions on hold pending customer intervention
Character length and limitations: 10 integer characters
Field Description