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 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
- 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
- Merchant e-Solutions, 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
- Submitting Purchasing Card Level 2 and Level 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
- Merchant e-Solutions 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: Viewing Processor- Specific Transaction Results
- ISO Country Codes
- Codes Used by FDMS South Only
- PayPal Acquirer
- Additional Processor Information
- Payflow Link Migration
Gateway Developer Guide and Reference 31 July 2012 59
Submitting Credit Card Transactions
Submitting Credit Transactions
6
NOTE: Do not include the ACCT or EXPDATE parameters in card-present transactions. The
SWIPE value includes this data.
TRXTYPE=S&TENDER=C&PARTNER=PayPal&USER=SuperMerchant&PWD=SuperMerchant&SWIP
E[40]=;4912000033330026=15121011000012345678?&AMT=21.00
Submitting Credit Transactions
The credit transaction (TRXTYPE=C) refunds the specified amount back to the cardholder. A
credit transaction can contain a reference to the original transaction (referenced) or not (non-
referenced) depending on how your account is setup. To issue a credit, the original transaction
can only be one of the following: a Sale (TRXTYPE=S), Delayed Capture (TRXTYPE=D) or
Voice Authorization (TRXTYPE=F). It is recommended that the merchant issue a credit only if
the original transaction has already settled. Even though it is possible to issue a credit to a
transaction that has not settled, it is recommended that you void such transactions.
Both the credit transaction and the original transaction will appear on the customer’s
statement.
Required Credit Transaction Parameters
The required parameter data for a credit transaction depends on the Allow non-referenced
credits security setting for your Payflow account. A non-referenced credit is a credit
transaction that does not use the credit card information from an existing transaction. You
provide the credit card information. As an example, Sally Smith calls you on the phone to
cancel an order from your business. To refund her money, you credit her credit card by
submitting a non-referenced credit transaction.
Guidelines and parameter requirements for credit transactions differ depending on whether
non-referenced credits are allowed.
Non-Referenced Credits Not Allowed
When non-referenced credits are not allowed (the setting recommended by PayPal), credit
transactions are permitted only against existing sale, delayed capture, and voice authorization
transactions. To submit a credit transaction when non-referenced credits are not allowed, pass
the following parameter:
Parameter Description
ORIGID (Required by some transaction types) ID of the original transaction referenced.
The PNREF parameter returns this ID, and it appears as the Transaction ID in
PayPal Manager reports.
Limitations: 12 case-sensitive alphanumeric characters.