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 39
Credit Card Transactions
Submitting Inquiry Transactions
Required Parameters When Using the CUSTREF
To submit an Inquiry transaction when using the CUSTREF, you must pass the following
parameter:
CUSTREF
Optionally, specify the STARTTIME and ENDTIME parameters. The Inquiry transaction request
parameters are described below.
IMPORTANT:If there are multiple transactions with a particular CUSTREF value, then the
Inquiry transaction returns only the last transaction with the specified
CUSTREF. So, to ensure that you can always access the correct transaction,
you must use a unique CUSTREF when submitting any transaction, including
retries.
Inquiry Transaction Parameter String Using the CUSTREF
This is an example Inquiry transaction parameter string using the CUSTREF:
TABLE 4.10 Inquiry transaction request parameters when using the CUSTREF
Parameter Description
CUSTREF (Required) Merchant-defined identifier for reporting and auditing purposes. For
example, you can set CUSTREF to the invoice number.
You can use CUSTREF when performing Inquiry transactions. To ensure that you
can always access the correct transaction when performing an Inquiry, you must
provide a unique CUSTREF when submitting any transaction, including retries.
Limitations: 12 alphanumeric characters.
STARTTIME (Optional) For Inquiry transactions when using CUSTREF to specify the
transaction.
ENDTIME specifies the end of the time period during which the transaction
specified by the CUSTREF occurred. See STARTTIME.
ENDTIME must be less than 30 days after STARTTIME. An inquiry cannot be
performed across a date range greater than 30 days.
If you set ENDTIME, and not STARTTIME, then STARTTIME is defaulted to 30 days
before ENDTIME.
If neither STARTTIME nor ENDTIME is specified, then the system searches the last
30 days.
Limitations: 14 numeric characters in the format yyyymmddhhmmss.
ENDTIME (Optional) For Inquiry transactions when using CUSTREF to specify the
transaction.
ENDTIME specifies the end of the time period during which the transaction
specified by the CUSTREF occurred. See STARTTIME.
Limitations: 14 numeric characters.