Developer's Guide
Table Of Contents
- 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 Account Verifications With TRXTYPE=A
- 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
- 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
- Additional Processor Information
- Index
Payflow Pro Developer’s Guide 93
Performing TeleCheck Electronic Check Transactions
Testing TeleCheck Transactions
B
Testing TeleCheck Transactions
PayPal provides a test server to support testing and configuration. For information on the test
server URL, see “Host Addresses” on page 13.
Example Test Transaction
“TRXTYPE=S&TENDER=K&CHKTYPE=P&PARTNER=<your Partner Name (typically
PayPal>&VENDOR=<your Merchant Login Name>&USER=<your Merchant Login
PARTNER The authorized PayPal Reseller that registered you for the
Payflow service provided you with a Partner ID. If you
registered yourself, use PayPal.
This parameter is case-sensitive.
Yes Alpha-
numeric
64
PHONENUM Account holder’s telephone number No Numeric 20
PWD Case-sensitive 6- to 32-character password that you
created while registering for the account.
Yes Alpha-
numeric
32
SS Account holder’s social security number.
If CHKTYPE=P, a value for either DL or SS must be
passed as an identifier.
If CHKTYPE=C, the Federal Tax ID must be passed as the
SS value.
No Alpha-
numeric
35
STATE Account holder’s state Yes Alpha 2
STREET Account holder’s street address Yes Alpha-
numeric
30
TENDER Tender type (method of payment). Use only the value K
(electronic check).
Yes Alpha 1
TRXTYPE Type of transaction that should be processed. Allowed
transaction types: Sale (S), Void (V), Inquiry (I).
Yes Alpha 1
USER Case-sensitive login ID for the Payflow Pro account that
you created while registering for the account.
In the future, each account will allow multiple users. This
parameter will specify the user.
Yes Alpha-
numeric
64
VENDOR Case-sensitive Vendor ID that you created while
registering for the account.
Yes Alpha-
numeric
64
ZIP Account holder’s 5- to 9-digit postal code (called ZIP code
in the USA). Do not use spaces, dashes, or non-numeric
characters.
Yes Alpha 9
T
ABLE B.1 TeleCheck Parameters (Continued)
Parameter Description Required Type Length