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
Submitting Credit Card Transactions
Submitting Credit Transactions
6
60 31 July 2012 Gateway Developer Guide and Reference
Set the value of ORIGID to the PNREF value returned for the original transaction. (PayPal
Manager reports display the PNREF as the Transaction ID.) If you do not specify an amount,
the amount of the original transaction is credited to the cardholder.
Non-Referenced Credits Allowed
When non-referenced credits are allowed, credit transactions are permitted in any amount up
to the transaction limit for the credit card account that you specify. To submit a credit
transaction when non-referenced credits are allowed, you must pass values for the following
parameters:
ACCT
EXPDATE
AMT
NOTE: The default security setting for Gateway accounts is Allow non-referenced credits =
No. Sending the ORIGID is the preferred method for performing credit transactions.
Using the ACCT, EXPDATE, or AMT parameters for such accounts leads to the return of
RESULT value 117 (failed the security check). To help reduce fraud, PayPal
recommends that you not activate non-referenced credits unless you have a business
reason. For information on setting the security settings, see PayPal Manager online
help.
Set the value of ORIGID to the PNREF value returned for the original transaction. (PayPal
Manager reports display the PNREF as the Transaction ID.) If you do not specify an amount,
then the amount of the original transaction is credited to the cardholder.
Fields Copied From the Original Transaction Into the Credit Transaction
The following fields are copied from the original transaction into the credit transaction (if they
exist in the original transaction). If you provide a new value for any of these parameters when
submitting the credit transaction, the new value is used. (Exceptions are ACCT, EXPDATE, and
SWIPE. These parameters retain their original values.)
NOTE: These fields are not copied for referenced credits: TAXAMT, TAXEXEMPT, DUTYAMT,
FREIGHTAMT, and (for American Express only) DESC4.
NOTE: For processors that use the RECURRING parameter: If you set the RECURRING
parameter to Y in the original transaction, this setting is ignored when forming the
credit transaction.
Parameter Description
ORIGID (Required by some transaction types) ID of the original transaction that is being
referenced. The PNREF parameter returns this ID, and it appears as the
Transaction ID in PayPal Manager reports.
Limitations: 12 case-sensitive alphanumeric characters