Response Codes & Text

CODE
TEXT & RESPONSE EXPlANATION
0000
SUCCESSFUL TRANSACTION: See ‘0000 Response Text Variations Table’ below for text variations and explanations.
0001- 1299
Decline messages from various financial institutions. Text may not be constant for a particular return code. Hard-coding actions based on any of these values is not recommended. See Appendix A for details.

1000

MALFORMED TRANS: Some data in the transaction was missing or invalid, or the reference number was too long.

1001

ACCESS DENIED or TOTL DENIED: TERMID is not activated or not use of TERMID not permissible from IP address.

1003

DECLINED (CV): Card has been used more than the preset limit for the TERMID allows.

1011

ILLEGAL/MISSING AMOUNT: A blank or zero amount was sent as a financial transaction. Check the amount.

1016

COMPLETION NO MATCH: There is no matching Pre-Authorization for the Completion attempted.

1017

NO MATCH: There is no matching Sale, Completion, or Force Post for the Void attempted.

1018

CARD TYPE INVALID: Merchant not setup to accept card type, or the card is not a valid type.

1019

TRAN TYPE INVALID: Merchant not setup to accept transaction type, or transaction type does not exist.

1020

CARD NUMBER INVALID: Card number did not pass check-digit tests for that card type.

1024

NETWORK FAILURE: Communications failure in the authorization network. The transaction was neither approved nor declined.

1028

OPERATOR INVALID: OPERID submitted contained something other than letters and numbers. Refer to specifications.

1029

AUTH NUMBER MISSING/INVALID: Force Post transaction is missing an authorization number.

1030

CARD LENGTH ERR: Card number submitted did not contain the correct number of digits for that card type.

1031

INVALID/MISSING REF: Reference number is missing or invalid. Refer to specifications.

1032

CARD DATA ERROR: Card data is invalid or incomplete.

1033

NOTHING TO SETTLE: Settlement was requested for an empty batch.

1035

DUPLICATE REF: Reference number transaction is not unique in the batch

1036

INVALID INV: Invoice number is invalid

1037

USERFEE NOT ALLOWED: Terminal ID is not setup for USERFEE. Contact SportsPay Support. OR,
USERFEE TOO SMALL: The amount is lower than the cost of the transaction using the merchant's billing profile. Utilize the AMT field in GetAPIKey or StartSession to receive an accurate amount in the returned value.

1097

HOST COMMS ERROR: Communication with the bank host failed during the transaction. Retry the transaction.

1098

INVALID HOST RESPONSE: Bank host provided an invalid response. Retry the transaction.

1099

NETWORK FAILURE: Network failure has occurred while communicating with the card issuer.
9100
GATEWAY SYSTEM ERROR: Gateway has generated an internal error. Switch to the backup gateway URL and try again.
9101
GATEWAY SYSTEM ERROR: Gateway has generated an internal error. Switch to the backup gateway URL and try again.
9102
GATEWAY CONFIG ERROR: There is an error in the configuration of the TERMID on the gateway. Please contact support.
9128
INVALID PASSWORD: Incorrect password provided for the TERMID.

0000 Response Text Variations

Depending on the request sent, the TEXT of a ‘0000’ return code will vary.

CODE
REQUEST TYPE
TEXT & RESPONSE EXPLANATION
0000 = SUCCESS
SALE

TEXT field contains the authorization number followed by the dollar value of the transaction. Example: R02564 $8.99

FORCE POST

TEXT field contains the authorization number followed by the dollar value of the transaction. Example: R02564 $8.99

PRE-AUTHORIZATION

TEXT field contains the authorization number followed by the dollar value of the transaction. Example: R02564 $8.99

COMPLETION

TEXT field contains the authorization number (the authorization number obtained during the corresponding pre-authorization) followed by the dollar value of the transaction. Example: R02564 $8.99

AUTHORIZE ONLY

TEXT field contains the authorization number followed by the dollar value of the transaction. Example: R02564 $8.99

RETURN

TEXT field contains the word 'RETURN' followed by the dollar value of the transaction. Example: RETURN $8.99"

VOID

TEXT field contains the text VOID OK

MERCHANDISE RETURN VOID

TEXT field contains the text MRVOID OK

BALANCE REQUESTS

TEXT field contains the total batch dollar amount, individual card total amounts, and total number of depositable transactions for each card type (meaning Pre-Authorization and Auth Only transactions are not included in the totals).

The amounts shown are the amounts that would be settled for deposit if you were to perform a Settlement transaction at that instant on that OPERID.

Please note that the card types are listed in alphabetical order.

The message format looks like this:

TOTL , <$amount>, <$amount>…

Example: TOTL $4.20 , AMEX 0 $0.00 , MCRD 1 $2.00 , VISA 1 $2.20

SETTLEMENTS

TEXT field contains the text SETTLED followed by the dollar value of the Settlement.

Example: SETTLED $1643.21

Note: If you receive a different answer in response to a Settlement (possibly due to a communications error), a Balance Request will allow you to check if the Settlement went through.