The vital identification numbers are incorrect

If the original transaction was approved, and a value was passed in the duplicate window field, the payment gateway response will also include the authorization code for the original transaction. All duplicate transactions submitted after the duplicate window, whether specified in the transaction request or after the payment gateway’s default 2 minute duplicate window, are processed normally.

Response Code Details

The following tables describe the response codes and response reason texts that are returned for each transaction.

Response Code indicates the overall status of the transaction with possible values of approved, declined, errored, or held for review.

Response Reason Code is a numeric representation of a more specific reason for the transaction status.

Response Reason Text details the specific reason for the transaction status. This information can be returned to the merchant and/or customer to provide more information about the status of the transaction.

Response Codes

RESPONSE CODE	DESCRIPTION
1	This transaction has been approved.
2	This transaction has been declined.
3	There has been an error processing this transaction.
4	This transaction is being held for review.

Response Reason Codes and Response Reason Text

RESPONSE	RESPONSE	RESPONSE REASON TEXT	NOTES
CODE	REASON
	CODE
1	1	This transaction has been approved.
2	2	This transaction has been declined.
2	3	This transaction has been declined.
2	4	This transaction has been declined.	The code returned from the processor
			indicating that the card used needs to
			be picked up.
3	5	A valid amount is required.	The value submitted in the amount
			field did not pass validation for a
			number.
3	6	The credit card number is invalid.
3	7	The credit card expiration date is invalid.	The format of the date submitted was
			incorrect.
3	8	The credit card has expired.
3	9	The ABA code is invalid.	The value submitted in the
			x_bank_aba_code field did not pass
			validation or was not for a valid

 

Last revised: 8/12/2008
Copyright © 1998 – 2008 Authorize.Net, a Cyber Source solution	33

AIM Developer Guide
RESPONSE	RESPONSE	RESPONSE REASON TEXT	NOTES
CODE	REASON
	CODE
			financial institution.
3	10	The account number is invalid.	The value submitted in the
			x_bank_acct_num field did not pass
			validation.
3	11	A duplicate transaction has been	A transaction with identical amount
		submitted.	and credit card information was
			submitted two minutes prior.
3	12	An authorization code is required but not	A transaction that required
		present.	x_auth_code to be present was
			submitted without a value.
3	13	The merchant API Login ID is invalid or
		the account is inactive.
3	14	The Referrer or Relay Response URL is	The Relay Response or Referrer URL
		invalid.	does not match the merchant’s
			configured value(s) or is absent.
			Applicable only to SIM and WebLink
			APIs.
3	15	The transaction ID is invalid.	The transaction ID value is non-
			numeric or was not present for a
			transaction that requires it (i.e., VOID,
			PRIOR_AUTH_CAPTURE, and
			CREDIT).
3	16	The transaction was not found.	The transaction ID sent in was properly
			formatted but the gateway had no
			record of the transaction.
3	17	The merchant does not accept this type	The merchant was not configured to
		of credit card.	accept the credit card submitted in the
			transaction.
3	18	ACH transactions are not accepted by	The merchant does not accept
		this merchant.	electronic checks.
3	19 – 23	An error occurred during processing.
		Please try again in 5 minutes.
3	24	The Nova Bank Number or Terminal ID
		is incorrect. Call Merchant Service
		Provider.
3	25 – 26	An error occurred during processing.
		Please try again in 5 minutes.
2	27	The transaction resulted in an AVS
		mismatch. The address provided does
		not match billing address of cardholder.
3	28	The merchant does not accept this type	The Merchant ID at the processor was
		of credit card.	not configured to accept this card type.
3	29	The Paymentech identification numbers
		are incorrect. Call Merchant Service
		Provider.
3	30	The configuration with the processor is
		invalid. Call Merchant Service Provider.
3	31	The FDC Merchant ID or Terminal ID is	The merchant was incorrectly set up at
		incorrect. Call Merchant Service	the processor.
		Provider.
3	32	This reason code is reserved or not
		applicable to this API.
3	33	FIELD cannot be left blank.	The word FIELD will be replaced by an
			actual field name. This error indicates
			that a field the merchant specified as
Last revised: 8/12/2008
Copyright © 1998 – 2008 Authorize.Net, a CyberSource solution			34

 

			Section 4 Transaction Response
RESPONSE	RESPONSE	RESPONSE REASON TEXT	NOTES
CODE	REASON
	CODE
			required was not filled in.
3	34	The VITAL identification numbers are	The merchant was incorrectly set up at
		incorrect. Call Merchant Service	the processor.
		Provider.
3	35	An error occurred during processing.	The merchant was incorrectly set up at
		Call Merchant Service Provider.	the processor.
3	36	The authorization was approved, but
		settlement failed.
3	37	The credit card number is invalid.
3	38	The Global Payment System	The merchant was incorrectly set up at
		identification numbers are incorrect. Call	the processor.
		Merchant Service Provider.
3	40	This transaction must be encrypted.
2	41	This transaction has been declined.	Only merchants set up for the
			FraudScreen.Net service would
			receive this decline. This code will be
			returned if a given transaction’s fraud
			score is higher than the threshold set
			by the merchant.
3	43	The merchant was incorrectly set up at	The merchant was incorrectly set up at
		the processor. Call your Merchant	the processor.
		Service Provider.
2	44	This transaction has been declined.	The card code submitted with the
			transaction did not match the card
			code on file at the card issuing bank
			and the transaction was declined.
2	45	This transaction has been declined.	This error would be returned if the
			transaction received a code from the
			processor that matched the rejection
			criteria set by the merchant for both
			the AVS and Card Code filters.
3	46	Your session has expired or does not
		exist. You must log in to continue
		working.
3	47	The amount requested for settlement	This occurs if the merchant tries to
		may not be greater than the original	capture funds greater than the amount
		amount authorized.	of the original authorization-only
			transaction.
3	48	This processor does not accept partial	The merchant attempted to settle for
		reversals.	less than the originally authorized
			amount.
3	49	A transaction amount greater than	The transaction amount submitted was
		$[amount] will not be accepted.	greater than the maximum amount
			allowed.
3	50	This transaction is awaiting settlement	Credits or refunds may only be
		and cannot be refunded.	performed against settled transactions.
			The transaction against which the
			credit/refund was submitted has not
			been settled, so a credit cannot be
			issued.
3	51	The sum of all credits against this
		transaction is greater than the original
		transaction amount.
3	52	The transaction was authorized, but the
		client could not be notified; the
Last revised: 8/12/2008
Copyright © 1998 – 2008 Authorize.Net, a CyberSource solution			35

 

AIM Developer Guide
RESPONSE	RESPONSE	RESPONSE REASON TEXT	NOTES
CODE	REASON
	CODE
		transaction will not be settled.
3	53	The transaction type was invalid for	If x_method = ECHECK, x_type cannot
		ACH transactions.	be set to CAPTURE_ONLY.
3	54	The referenced transaction does not
		meet the criteria for issuing a credit.
3	55	The sum of credits against the	The transaction is rejected if the sum
		referenced transaction would exceed the	of this credit and prior credits exceeds
		original debit amount.	the original debit amount
3	56	This merchant accepts ACH	The merchant processes eCheck.Net
		transactions only; no credit card	transactions only and does not accept
		transactions are accepted.	credit cards.
3	57 – 63	An error occurred in processing. Please
		try again in 5 minutes.
2	65	This transaction has been declined.	The transaction was declined because
			the merchant configured their account
			through the Merchant Interface to
			reject transactions with certain values
			for a Card Code mismatch.
3	66	This transaction cannot be accepted for	The transaction did not meet gateway
		processing.	security guidelines.
3	68	The version parameter is invalid.	The value submitted in x_version was
			invalid.
3	69	The transaction type is invalid.	The value submitted in x_type was
			invalid.
3	70	The transaction method is invalid.	The value submitted in x_method was
			invalid.
3	71	The bank account type is invalid.	The value submitted in
			x_bank_acct_type was invalid.
3	72	The authorization code is invalid.	The value submitted in x_auth_code
			was more than six characters in length.
3	73	The driver’s license date of birth is	The format of the value submitted in
		invalid.	x_drivers_license_dob was invalid.
3	74	The duty amount is invalid.	The value submitted in x_duty failed
			format validation.
3	75	The freight amount is invalid.	The value submitted in x_freight failed
			format validation.
3	76	The tax amount is invalid.	The value submitted in x_tax failed
			format validation.
3	77	The SSN or tax ID is invalid.	The value submitted in
			x_customer_tax_id failed validation.
3	78	The Card Code (CVV2/CVC2/CID) is	The value submitted in x_card_code
		invalid.	failed format validation.
3	79	The driver’s license number is invalid.	The value submitted in
			x_drivers_license_num failed format
			validation.
3	80	The driver’s license state is invalid.	The value submitted in
			x_drivers_license_state failed format
			validation.
3	81	The requested form type is invalid.	The merchant requested an integration
			method not compatible with the AIM
			API.
3	82	Scripts are only supported in version	The system no longer supports version
		2.5.	2.5; requests cannot be posted to
			scripts.
Last revised: 8/12/2008
Copyright © 1998 – 2008 Authorize.Net, a CyberSource solution			36

 

			Section 4 Transaction Response
RESPONSE	RESPONSE	RESPONSE REASON TEXT	NOTES
CODE	REASON
	CODE
3	83	The requested script is either invalid or	The system no longer supports version
		no longer supported.	2.5; requests cannot be posted to
			scripts.
3	84	This reason code is reserved or not
		applicable to this API.
3	85	This reason code is reserved or not
		applicable to this API.
3	86	This reason code is reserved or not
		applicable to this API.
3	87	This reason code is reserved or not
		applicable to this API.
3	88	This reason code is reserved or not
		applicable to this API.
3	89	This reason code is reserved or not
		applicable to this API.
3	90	This reason code is reserved or not
		applicable to this API.
3	91	Version 2.5 is no longer supported.
3	92	The gateway no longer supports the
		requested method of integration.
3	97	This transaction cannot be accepted.	Applicable only to SIM API.
			Fingerprints are only valid for a short
			period of time. This code indicates that
			the transaction fingerprint has expired.
3	98	This transaction cannot be accepted.	Applicable only to SIM API. The
			transaction fingerprint has already
			been used.
3	99	This transaction cannot be accepted.	Applicable only to SIM API. The
			server-generated fingerprint does not
	Was this answer helpful? Top of Form Bottom of Form

 Print this Article

Also Read

AVS Codes

Address Verification Service (AVS) codes Type of CodesCodesDescription Domestic (U.S.)…

Authorize error codes 83

A table of common decline reasons, with the associated Response Reason Code, is listed below:…

  Support

Source: We are check the Quickbooks support Error or Intuit Help line number. @ 1800-865-4183.

My Support Tickets   Announcements   Knowledgebase   Downloads   Network Status   Open Ticket