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 137
TeleCheck Electronic Check Processing
Response Code Values
B
Response Code Values
For your service, below is a complete list of possible Response Codes. Depending upon the
merchants risk parameters and service type, some of these may not apply. Please confirm
applicable codes with TeleCheck’s Merchant Boarding and Certification group.
NOTE: Merchants should establish policies and procedures for each applicable response code.
For example, if a clerk enters a transaction and receives Response Code 27, they
should retry the transaction. If, after entering the item a second time they receive a
Response Code 27 again, the merchant may choose to cancel or terminate the
transaction and a) retry the transaction b) call TeleCheck Live Operator Authorization
Center, or c) request another form of payment from the check writer.
Sale Response Code Values
Sale Approval Responses
Sale Decline Responses
HOSTCODE TeleCheck’s response code representing the results of the transaction
authorization attempt.
Character length and limitations: 6 numeric characters
RESPMSG A descriptive message associated with decline or error result values.
Character length and limitations: alphanumeric, variable number of characters
Code Description Merchant Action
07 Approved No action needed.
Code Description Merchant Action
08 Rejected (Negative Data) Ask for other form of payment or decline sale
to customer.
73 Lost or Stolen check Ask for other form of payment or decline sale
to customer.
88 Rejected Code 3 (Risk) Ask for other form of payment or decline sale
to customer.
25 Ineligible – ACH Not Offered
NOTE: Do NOT use the verbiage
“decline” this is not a true decline.
Ask for other form of payment.
Field Description