Developer's Guide
Table Of Contents
- Payflow Pro Developer’s Guide
- Contents
- Introduction
- Downloading, Installing, and Activating
- Simple Payflow Transaction
- Credit Card Transactions
- Credit Card Features
- About Credit Card Processing
- Parameters Used in Credit Card Transactions
- Submitting Sale Transactions
- Submitting Authorization/Delayed Capture Transactions
- When To Use Authorization/Delayed Capture Transactions
- Required Authorization Transaction Parameters
- Typical Authorization Transaction Parameter String
- Required Delayed Capture Transaction Parameters
- Delayed Capture Transaction: Capturing Transactions for Lower Amounts
- Delayed Capture Transaction: Capturing Transactions for Higher Amounts
- Delayed Capture Transaction: Error Handling and Retransmittal
- Submitting Voice Authorization Transactions
- Submitting Credit Transactions
- Submitting Void Transactions
- Submitting Inquiry Transactions
- Recharging to the Same Credit Card (Reference Transactions)
- Submitting Card-Present (SWIPE) Transactions
- Submitting Purchasing Card Transactions
- Using Address Verification Service
- Processing Platforms Supporting Address Verification Service
- Example Address Verification Service Request Parameter List
- Example Address Verification Service Response
- Card Security Code Validation
- Credit Card Testing
- Responses to Transaction Requests
- Processors Requiring Additional Transaction Parameters
- American Express
- First Data Merchant Services (FDMS) Nashville
- First Data Merchant Services (FDMS) South
- First Data Merchant Services (FDMS) North
- Merchant e-Solutions
- Elavon (Formerly Nova)
- Paymentech
- TSYS Acquiring Solutions
- Performing TeleCheck Electronic Check Transactions
- Submitting Purchasing Card Level 2 and Level 3 Transactions
- About Purchasing Cards
- About Program Levels
- About American Express Purchasing Card Transactions - Phoenix Processor
- American Express Phoenix 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
- Merchant e-Solutions Purchasing Card Transaction Processing
- Elavon (Formerly Nova) Purchasing Card Transaction Processing
- Paymentech Salem (New Hampshire) Purchasing Card Transaction Processing
- Paymentech Tampa Level 2 Purchasing Card Transaction Processing
- TSYS Acquiring Solutions Purchasing Card Transaction Processing
- VERBOSITY: Viewing Processor- Specific Transaction Results
- Additional Reporting Parameters
- ISO Country Codes
- Codes Used by FDMS South Only
- XMLPay
- Index
Payflow Pro Developer’s Guide 61
Responses to Transaction Requests
RESULT Values and RESPMSG Text
6
1014 Buyer Authentication Service — Merchant is not enrolled for Buyer
Authentication Service (3-D Secure).
1016 Buyer Authentication Service — 3-D Secure error response received. Instead of
receiving a PARes response to a Validate Authentication transaction, an error response
was received.
1017 Buyer Authentication Service — 3-D Secure error response is invalid. An error
response is received and the response is not well formed for a Validate Authentication
transaction.
1021 Buyer Authentication Service — Invalid card type
1022 Buyer Authentication Service — Invalid or missing currency code
1023 Buyer Authentication Service — merchant status for 3D secure is invalid
1041 Buyer Authentication Service — Validate Authentication failed: missing or
invalid PARES
1042 Buyer Authentication Service — Validate Authentication failed: PARES format is
invalid
1043 Buyer Authentication Service — Validate Authentication failed: Cannot find
successful Verify Enrollment
1044 Buyer Authentication Service — Validate Authentication failed: Signature
validation failed for PARES
1045 Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid amount in PARES
1046 Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid acquirer in PARES
1047 Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid Merchant ID in PARES
1048 Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid card number in PARES
1049 Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid currency code in PARES
1050 Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid XID in PARES
1051 Buyer Authentication Service — Validate Authentication failed: Mismatched or
invalid order date in PARES
1052 Buyer Authentication Service — Validate Authentication failed: This PARES was
already validated for a previous Validate Authentication transaction
T
ABLE 6.2 Payflow transaction RESULT values and RESPMSG text (Continued)
RESULT RESPMSG and Explanation