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 35
Credit Card Transactions
Submitting Void Transactions
Submitting Void Transactions
The Void transaction (TRXTYPE=V) prevents a transaction from being settled.
As part of its internal process, PayPal makes reasonable effort to process authorization
reversals for void transactions for debit and credit cards. Because the honoring of
authorization reversals is ultimately decided by the bank or issuer, there is no accurate way to
determine if an individual bank or issuer has honored an authorization reversal request.
N OTE: For more information on authorization reversals, see
http://en.wikipedia.org/wiki/Authorization_hold.
For information on authorization reversals related to the Paymentech New Hampshire and
FDMS North processors, see “Processors Requiring Additional Transaction Parameters” on
page 65.
When To Use a Void Transaction
Follow these guidelines:
z You can void Delayed Capture, Sale, Credit, Authorization, and Voice Authorization
transactions. You cannot void a Void transaction.
z You can only use a Void transaction on a transaction that has not yet settled. To refund a
customer’s money for a settled transaction, you must submit a Credit transaction.
Required Void Transaction Parameters
To submit a Void transaction, you must pass the following parameter:
ORIGID
Set ORIGID to the PNREF (Transaction ID in PayPal Manager reports) value returned for the
original transaction.
Fields Copied From the Original Transaction into the Void Transaction
The following fields are copied from the original transaction into the Void transaction (if they
exist in the original transaction). If you provide a new value for any of these parameters when
submitting the Void transaction, then the new value is used. (Exceptions are ACCT, EXPDATE,
and SWIPE. These parameters retain their original values).
TABLE 4.7 Void required parameter
Parameter Description
ORIGID (Required by some transaction types) ID of the original transaction that is being
referenced. This ID is returned by the PNREF parameter and appears as the
Transaction ID in PayPal Manager reports.
Limitations: 12 case-sensitive alphanumeric characters.