Error Messages

Error Messages
Error Messages
Error ID
1
User Message
Password/Username Incorrect.
Please remember that usernames
and passwords are case-sensitive.
Technical
Sent by login screen when the username and/or the password are
incorrect.
2
Access to page denied.
3
Transaction type [type] not
supported. Please contact support.
Processing gateway currently
offline. Please try back in a few
moments.
The user has attempted to access a page they don't have permission
to access.
Is returned by /console/vterm.php when an unknown transaction type
(sale,credit,etc) is attempted.
Return by processing engine when the gateway cannot establish a
connection with the processing backend.
4
5
6
7
Error in verification module
[module]. Please contact support.
Merchant not found.
Merchant has been deactivated.
8
Unable to retrieve current batch.
9
Unable To Create Transaction.
Please Contact Support.
Unable To Allocate Transaction
Slot. Please contact support.
Invalid Card Number (1)
10
11
12
The given fraud module was did not load correctly. An upgrade may
be in progress.
The system was not able to locate the requested merchant.
Merchant account has been marked as deactivate. Contact
USAePay customer service.
Failed to get the id of the current batch. Typically this indicates that
the merchant account is not active or batches are out of sync. Verify
all merchant account info provided to usaepay.
Internal database error, system may be in the process of failing over
to backup database server. Retry transaction.
Internal database error, system may be in the process of failing over
to backup database server. Retry transaction.
The cardnumber contains illegal characters. A card number may only
include numbers.
Cardnumber was not between 13 and 16 digits
13
Card Number was not between 13
and 16 digits
Invalid Card Number (3)
14
Invalid Credit Card Number (1)
15
Invalid expiration date. Must be in
MMYY format. (1)
Invalid expiration date. Must be in
MMYY format. (2)
Credit card has expired.
Gateway temporarily offline.
Please try again shortly.
Gateway temporarily offline for
maintenance. Please try again in a
few minutes.
Expiration contains invalid characters (nothing but numbers allowed)
User not configured correctly,
please contact support.
Invalid username.
User not configured correctly. Remove the user and readd.
16
17
18
19
20
21
22
23
You do not have access to this
page.
Specified source key not found.
24
Transaction already voided.
Cardnumber failed Luhn Mod-10 Checkdigit Method (ISO 2894/ANSI
4.13)
Cardnumber passed length, format and checkdigit tests but didn't
match any of the cardnumber profiles enabled in the system. Contact
USAePay to verify support of cardtype.
Could not guess format of date. It wasn't MMYY or MMYYYY or
MMDDYYYY or even MMDDYY format.
The credit card expiration date has passed.
Unable to contact processor backend. Failed bank link maybe in the
process of coming back up. Retry transaction.
Processor backend is offline for maintenance. Retry transaction.
The merchant didn't type in a valid username when adding a new
user.
The user tried to access a page they don't have permission to access.
The source key provided did not match any of the currently active
keys.
The transaction was already marked as voided and wasn't going to
be settled anyway.
1 of 12
Error Messages
Error ID
25
User Message
Unable to find transaction in batch.
Technical
The batchid on the transaction references a batch that doesn't exist.
If there isn't a valid batch then trying to void a transaction isn't going
to do much
26
The batch has already been
closed. Please apply a credit
instead.
The specified transaction has already been settled. Once a
transaction has been sent in for settlement it can not be voided.
27
Gateway temporarily offline.
Please try again shortly. (2)
Unable to verify source
Unable to generate security key.
Error communicating with the processing backend. Retry transaction.
28
29
30
31
32
Source has been blocked from
processing transactions.
Duplicate transaction, wait atleast
[minutes] minutes before trying
again.
VerifySource couldn't find the source or the source was disabled
VerifySource wasn't able to create a source on the fly. Trouble
finding a key.
Merchant has disabled the specified source key.
The duplicate transaction fraud module detected a dupe.
The maximum order amount is
$[amount].
The minimum order amount is
$[amount].
Your billing information does not
match your credit card. Please
check with your bank.
Fraud module response
35
36
Unable to locate transaction
Gateway temporarily offline for
maintenance. Please try again in a
few minutes.
Was not able to find the requested transaction for voiding.
VeriCheck link has been brought down for maintenance. Retry
transaction.
37
38
39
40
Customer Name not submitted.
Invalid Routing Number.
Invalid Checking Account Number.
Merchant does not currently
support check transactions.
Check processing temporarily
offline. Please try again shortly.
Temporarily unable to process
transaction. Please try again
shortly.
Cardholder field was blank
Check Routing number did not meet requirement of 9 digits
Check Account number is not atleast 4 digits long
The merchant doesn't have a valid tax id or password entered for
check processing.
Internal system error encountered while communicating with check
processor. Please contact USAePay support.
A corrupted response (unparsable) was received from vericheck
Transaction Requires Voice
Authentication. Please Call-In.
Merchant not configured properly
(CardAuth)
Auth service unavailable.
Processor returned a referral.
33
34
41
42
43
44
45
46
50
70
71
80
Auth service unavailable (6).
Invalid SSN.
Transaction exceeds maximum
amount.
Transaction out of balance.
Transaction type not allowed from
this source.
Fraud module response.
AVS Response fraud module blocked this transaction.
The merchant has payment authentication enabled but does not
have a processorid/merchantid entered
Internal system error was encountered while connecting to
authentication platform. Contact USAePay support.
A corrupted response was received from the authentication platform.
Social Security number must be 9 digits.
Transaction exceeds the maximum allowable amount of $99,999.
Transaction does not add up correctly. subtotal + tip + tax + shipping
- discount must equal the amount.
The requested command (sale, authonly, etc) was blocked by the
merchant's source key. The command must be checked on source
key settings screen to be accepted by the gateway.
2 of 12
Error Messages
Error ID
81
User Message
Unable to apply changes, please
retry.
Check transactions can not be
voided.
Technical
Failed to commit changes to transaction. Possible locking or db
syncing problem. Contact support.
Check transactions cannot be voided (canceled) due to the process
flow of check transactions. Contact the check processing company
or issue a reversal.
83
84
Transaction not approved
Pin code required for credit/void
85
Invalid expiration date. Must be in
MMYY format. (3)
Only approved transactions may be voided
The credit/void command requires that the source key be configured
with a pin.
The month was not in the range of 1-12. This could be because the
expiration was sent as YYMM. Valid expiration date must be sent as
MMYY
101
The batch is in the process of
closing.
Transaction is not currently voided.
Transaction has already been
settled.
Transaction not a full sale in the
current batch
Your billing address does not
match your credit card. Please
check with your bank.
Changes cannot be made to batch if its in the process of closing.
Processing Error Please Try Again
Merchant does not accept this type
of card (1)
Merchant does not accept this type
of card (2)
Invalid Card Expiration Date
Error from FDMS Nashville: Invalid Transaction Code
Error from FDMS Nashville: Terminal ID not setup for settlement on
this Card Type.
Error from FDMS Nashville: Terminal ID not setup for authorization
on this Card Type
Error from FDMS Nashville: Terminal ID not setup for settlement on
this Card Type.
Error from FDMS Nashville: Invalid Process Code, Authorization
Type or Card Type.
Error from FDMS Nashville: Invalid Transaction or Other Dollar
Amount.
Error from FDMS Nashville: Invalid Entry Mode.
82
102
103
104
2034
10001
10003
10004
10005
10006
10007
10008
10009
10010
10011
10012
10013
10014
10015
10016
Merchant does not accept this type
of card (3)
Invalid amount
Processing Error Please Try Again
(08)
Processing Error Please Try Again
(09)
Processing Error Please Try Again
(10)
Processing Error Please Try Again
(11)
Processing Error Please Try Again
(12)
Processing Error Please Try Again
(13)
Processing Error Please Try Again
(14)
Processing Error Please Try Again
(15)
Processing Error Please Try Again
(16)
Transaction must be voided already to be unvoided.
Changes cannot be made to a batch once it has been settled.
Only full sales that are in the currently open batch can be queued.
The AVS result received from the platform was blocked by the
Merchants fraud preferences. Funds were not held for this
transaction.
Error from FDMS Nashville: Invalid Card Present Flag.
Error from FDMS Nashville: Invalid Customer Present Flag
Error from FDMS Nashville: Invalid Transaction Count Value.
Error from FDMS Nashville: Invalid Terminal Type.
Error from FDMS Nashville: Invalid Terminal Capability.
Error from FDMS Nashville: Invalid Source ID.
Error from FDMS Nashville: Invalid Summary ID.
Error from FDMS Nashville: Invalid Mag Strip Data.
3 of 12
Error Messages
Error ID
10017
10018
10019
10020
10026
10027
User Message
Invalid Invoice Number (17)
Invalid Transaction Date or Time
(18)
Processing Error Please Try Again
(19)
Processing Error Please Try Again
(20)
Merchant has been deactivated
(26)
Invalid Merchant Account (27)
10030
Processing Error Please Try Again
(30)
10031
Processing Error Please Retry
Transaction (31)
Processing Error Please Try Again
(33)
Sequence Error, Please Contact
Support (43)
Merchant has been deactivated
(51)
Merchant has not been setup
correctly (54)
Merchant does not support this
card type (57)
Processing Error Please Try Again
(59)
Invalid Account Number (60)
10033
10043
10051
10054
10057
10059
10060
10061
10062
10080
10098
10099
10100
10101
10102
10103
10104
10105
Processing Error Please Try Again
(61)
Processing Error Please Try Again
(62)
Processing Error Please Try Again
(80)
Processing Error Please Try Again
(98)
Session timed out. Please re-login.
Your username has been locked
for excessive login attempts.
Your username has been deactivated due to inactivity for 90
days. Please contact support to reactivate your account.
Unable to open certificate.
Unable to read certificate.
Error reading certificate.
Unable to find original transaciton.
Technical
Error from FDMS Nashville: Invalid Invoice Number.
Error from FDMS Nashville: Invalid Transaction Date or Time.
Error from FDMS Nashville: Invalid bankcard merchant number in
First Data database
Error from FDMS Nashville: File Access Error in First Data database.
Error from FDMS Nashville: Terminal flagged as Inactive in First Data
database.
Error from FDMS Nashville: Invalid Merchant/Terminal ID
combination, verify numbers are accurate.
Error from FDMS Nashville: Unrecoverable database error from an
authorization process (usually means the Merchant/Terminal ID was
already in use).
Error from FDMS Nashville: Database access lock encountered, retry
transaction.
Error from FDMS Nashville: Database error in summary process,
retry transaction.
Error from FDMS Nashville: Transaction ID invalid, incorrect or out of
sequence.
Error from FDMS Nashville: Terminal flagged as not useable
(violated) in First Data database, Call Customer Support.
Error from FDMS Nashville: Terminal ID not set up on First Data
database for leased line access.
Error from FDMS Nashville: Terminal is not programmed for this
service, Call Customer Support
Error from FDMS Nashville: Settle Trans for Summary ID where
earlier Summary ID still open
Error from FDMS Nashville: Invalid account number found by
authorization process
Error from FDMS Nashville: Invalid settlement data found in
summary process (trans level)
Error from FDMS Nashville: Invalid settlement data (i.e., 'future' date
found, erroneous Pserve data found) (summary level)
Error from FDMS Nashville: Invalid Payment Service data found in
summary process (trans level).
Error from FDMS Nashville: General System Error.
Session timed out, (checkout timeout setting).
The user failed login too many times. Their account has been locked
for 60 minutes.
VISA Cisp requires locking of accounts that have not been accessed
in the past 90 days.
Unable to load reqired certificate. Contact Support.
Unable to load reqired certificate. Contact Support.
Unable to load required certificate. Contact support.
A capture or void operation was not able to locate the original
transaction.
4 of 12
Error Messages
Error ID
10106
10107
10108
10109
User Message
You have tried too many card
numbers, please contact merchant.
Invalid billing zipcode.
10116
10117
Invalid shipping zipcode.
Billing state does not match billing
zipcode.
Billing city does not match billing
zipcode.
Billing area code does not match
billing zipcode.
Shipping state does not match
shipping zipcode.
Shipping city does not match
shipping zipcode.
Shipping area code does not
match shipping zipcode.
Merchant does not accept
transactions from [country].
Unable to verify card ID number.
Transaction authentication required.
10118
Transaction authentication failed
10119
10120
Unable to parse mag stripe data.
Unable to locate valid installation.
Please contact support.
Wireless key disabled. Please
contact support.
Wireless key mismatch.
10110
10111
10112
10113
10114
10115
10121
10122
10123
10124
Success
Unsupported transaction type. Only
authonly, sales and voids may be
captured.
10125
Original transaction not approved.
10126
Transactions has already been
settled.
Card Declined (F)
Processor Error ([response])
Invalid transaction data.
Libary Error: CURL support not
found
Libary Error: Unable to initialize
CURL
Error reading from card processing
gateway.
Amount exceeds original
transaction amount.
10127
10128
10129
10130
10131
10132
10133
Technical
The transaction was blocked by the MultipleCardTries module.
The ZipCodeVerification module was not able to locate the billing
zipcode.
The ZipCodeValidation fraud module was not able to find module.
ZipCodeVerification database came up with a conflict
ZipCodeVerification database came up with a conflict
ZipCodeVerification database came up with a conflict
ZipCodeVerification database came up with a conflict
ZipCodeVerification database came up with a conflict
ZipCodeVerification database came up with a conflict
IpCountry module blocked transaction
CVV2, CID, etc result was blocked by CVVresponse fraud module.
The merchant has set a pin for this transaction but the api did not
receive a UMmd5hash. They need to either upgrade their software
to send the hash or they need to remove the pin on the source.
The UMmd5hash did not match the hash that was calculated for the
transaction.
Could not determine the mag data format that was sent in.
A wireless transaction came in with an install id that wasn't found in
the system.
The install id submitted has been deleted/disabled.
The wireless key submitted does not correspond to the source id
created for this installation.
Operation was successful.
An attempt was made to settle a transaction that can not be
captured. This error will occur if you attempt to capture an echeck
transaction.
You are trying to capture (settle) a transaction that was declined or
resulted in an error. You can only capture approved transactions.
You are trying to capture a transaction that has already been settled.
Hard decline from First Data.
Unknown reponse code from First Data Nashville.
PHP Library detected missing or invalid fields.
PHP Library was not able to find curl support. You must compile php
with curl and openssl.
PHP Library was unable to initialize CURL. SSL support may be
missing or incorrectly configured.
PHP Library was received a bad response from the gateway.
Credits processed by refnum can not exceed the dollar amount of the
original transaction.
5 of 12
Error Messages
Error ID
10134
10135
10204
10205
10212
10215
10225
10251
10255
10257
10262
10265
10275
User Message
Original transaction not an
approved sale
Unable to locate merchant
10297
19000
19001
19002
Pickup Card (F04)
Do not Honor (F05)
Invalid Transaction (F12)
Invalid Issuer (F15)
Unable to locate Record (F25)
Insufficient funds (F51)
Invalid Pin (F55)
Transaction not permitted (F57)
Restricted Card (F62)
Excess withdrawal count (F65)
Allowable number of pin tries
exceeded (F75)
Previous messages data
inconsistent (F77)
No checking account (F78)
Already reversed by switch (F79)
Invalid date (F80)
Incorrect CVV (F82)
Invalid Authorization life cycle (F84)
Transaction can not be completed,
violation of law (F93)
Declined for CVV failure (F97)
Unable to save application.
The field '[field]' is required.
Requested application not found.
19003
Requested merchant not found.
19004
19006
Unable to save merchant. Contact
support.
Requested merchant was deleted
and is no longer active.
Invalid search criteria.
19010
19011
Invalid [date] date.
Start date not before end date
19012
Unable to perform currency
conversion: [reason]
Currency is not supported by
merchant
Specified transactions was not
found.
Invalid Security Token.
10277
10278
10279
10280
10282
10284
10293
19005
19013
20001
20002
20003
SSL Certificate Does Not Match
Source
Technical
Credits via refnum may only be applied against an approved sale. If
the sale has been voided, the credit cannot be applied
Unable to map to merchant's database. Unexpected error requiring
support attention
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
FDMS Hard Decline
Database fault saving application, try again or contact support.
A required field was left blank.
The requested application ID could not be found. (Or the application
ID does not match the reseller specified by the key)
The requested Merchant ID could not be found. (Or the Merchant is
not assigned with the reseller specified by the key)
A database fault occured. Try again or contact support.
Requested merchant has already been deleted.
Improperly constructed search criteria. Either a field was not allowed
or the type was not valid.
Date should be in YYYY-MM-DD format
Invalid start and end dates. The start date must occur before the end
date.
Contact customer service for more information on error.
Currency is not supported by merchant
RefNum didn't match any of the merchants transactions.
Unable to parse the security token. Check the documentation for
correct formating
The client SSL certificate must be a valid USAePay signed certificate
and it must match the source key for which it was originally
generated. Merchant should download the certificate again.
6 of 12
Error Messages
Error ID
20004
20005
20006
20007
20008
User Message
Invalid search parameter.
Host does not have authorization
to use this Source.
Specified Hash type not supported.
A pin is required to use this source
key.
Unable to validate request. Check
pin and try again.
Technical
Message requires a properly formatted search parameter. See
documentation.
The sourcekey has ip restrictions turned on. The host connecting to
system is not on the list of allowed ips.
An unknown hashing algorithm was specified in the PinHash portion
of the security token. Currently only "md5" and "sha1" are supported.
The source key specified requires a pin for use. You must submit the
PinHash component of the security token.
The HashValue does not match check against the pin on file. Make
sure the user entered the correct pin. If the correct pin is being used,
double check that you are concatinating the source key, the seed
and the pin with out any spaces or other characters inbetween.
20009
Unable to perform requested action
An internal database error occured. Contact support for more
information.
Functions dealing with sensitive information must be validated using
a pin. The source key used does not have a pin set. The merchant
must update the source key to include a pin before accessing this
function.
20010
Requested functionality requires
the use of PIN for security
purposes.
20011
20012
Invalid search field '[field]'
Batch Upload not found
20013
Batch Upload already completed
20014
20015
20016
20017
20018
20019
20020
20021
Unsupported file format.
Unsupported encoding method.
File data missing.
Unable to decode data
Missing field list
Unknown command
Unknown field '[field]'
Line [linenum] incorrecty formatted.
20022
Duplicate batch detected.
20023
Another batch is already running.
To prevent a batch from being double submitted, the system only
allows one batch to be queued up at a time. Please resubmit the
batch after the currently running batch has been completed.
20024
20025
20026
20027
Invalid command '[command]' on
line '[linenum]'
Unabled to save batch upload
Positive dollar amount required
Unknown comparison type [type]
30001
Merchant does not accept card type
40002
40003
40004
40006
Account configuration error
Error communicating with processor
Error communicating with processor
Processor temporarily unavailable
Invalid transaction command was specified in the upload file. Valid
commands are sale, authonly, credit and check.
Unable to save batch upload. Try again shortly.
A positive dollar amount required.
The supported comparison types are eq, dneq, gt,lt, gte,lte, contains
and dncontain. Make sure you are using one of these
CardType Fraud Module: The credit card number submitted was not
on the list of accepted types.
Request for non existant platform id.
Request for non existant command.
Backend was unable to load the requested command.
Connection called before it was initialized
The specified field is not in the list of fields that can be searched on.
The referenced batch upload was not found. Double check the value
submitted for BatchNum.
The batch has already completed. You can't change the status of a
batch that has complete
Supported file formats are csv,tab and xml.
Supported file encodings are 7bit, base64, uuencode.
No data was found in the data variable.
Unable to decode upload data using the specified encoding method.
No fields were listed.
Requested command was not a valid command
Listed field was not found a valid transaction field
Every row in the upload field must contain every field listed in the
fields argument. The field may be left blank if its not used.
Over 25% of the transactions are duplicates. The batch has been
blocked as a duplicate batch. This can be overriden using the
Override Duplicates option.
7 of 12
Error Messages
Error ID
40007
40008
40009
User Message
Processor temporarily unavailable
Processor temporarily unavailable
Unable to load transaction
40010
Transaction has already been
processed.
Transaction exceeds maximum
amount
Failed to validate merchant id.
Unable to load merchant.
Merchant not configured correctly.
Unable to load batch.
Unable to load transaction data.
Invalid transaction amount.
Error communicating with
processor.
Unable to pull transactions
Batch is empty
Error sending transaction detail
record
Batch has already been closed
Transaction has already been
settled
Transaction has not been
previously authorized
Batch is already in the process of
closing
40011
40012
40013
40014
40015
40016
40017
40018
40020
40021
40022
40023
40024
40025
40026
40027
40028
40029
Unable to find requested batch.
Error closing batch
Invalid field name.
40030
40031
Customer Not Found
Error saving customer
40032
Unable to parse date
40033
Username and/or Password
Incorrect
Invalid merchant
Only a master account can lookup
cardnumbers
Merchant Industry not supported.
40034
40035
40036
40400
40401
Invalid Billing Amount
Unable to parse customer update
data.
Technical
Connection to processor failed.
All connections to processor are flagged as down.
The backend was unable to pull transaction data. Its possible a
database failover is occuring. Please retry transaction.
The transaction has a status indicating that it has already been
processed.
Blank response from processor link subsystem
Batch is already locked for closing. Usually this means that the batch
is in the process of closing. If the batch stays locked for more than a
few minutes, there may have been a problem closing the batch.
Please check the batch status for more details or contact support.
No batches matched the requested batchnum
Backend returned error
An invalid field was passed in the search array. Check
documentation for list of valid field names
Requested customer number not found.
A database fault was encountered while saving customer record. Try
operation again or contact support.
Improperly formatted date. Date must be formated YYYY-MM-DD
HH:MM:SS.
The merchant is configured for an industry that is not supported on
the processing platform they are using. Contact customer service for
assistance
A recurring charge must be atleast 0.01 and no larger than 99,999.99
The customer object was not able to parse the update data. Make
sure you are passing an array where the array keys are the name of
a field and values are the new value being set.
8 of 12
Error Messages
Error ID
40402
User Message
Unknown field [field]
40403
40404
40405
Next billing date [date] is in the past
Unable to parse custom data
Invalid schedule
40406
Invalid customer data object
40407
Invalid payment method object
40451
Unable to load customer payment
method
Invalid expiration date
40452
40453
40454
40455
40456
48000
65000
65165
65200
65201
Unable to locate requested
payment method.
Unable to load payment method.
Error storing payment method
record.
Error storing payment method
record.
65211
VPAS auth failed
Unable to process transaction
Cardholder Authentication Missing
Card Declined (P)
Transaction Requires Voice
Authentication. Please Call-In. (P)
Card Declined - Hold Card, Call
Transaction Requires Voice
Authentication. Please Call-In. (P2)
Invalid Account/Card Number.
(P204)
Invalid Expiration Date. (P205)
Invalid International Control
Account number. (P206)
Invalid American Banking
Association number. (P207)
Invalid Personal ID Number [PIN]
Entered. (P208)
Invalid Bank MID (P209)
Invalid Term No. / merchant ID not
valid. (P210)
Invalid Dollar Amount (P211)
65213
Invalid Transaction Format. (P213)
65214
Please Re-Try or Call In. Unable to
Reach Auth. Center. (P214)
65202
65203
65204
65205
65206
65207
65208
65209
65210
Technical
The specified field was not a valid customer field. Check the
documentation for a list of valid customer fields.
The next billing date must not be in the past
Custom data must be sent as anarray, even if saving a single value.
Invalid schedule specified. Check documentation for a list of valid
schedule designations.
Check the soap documentation for the fields required to make a valid
customer object
Check the soap documentation for the fields required to make a valid
payment method object.
There was a problem parsing the credentials require to load a
customer payment method object. Contact customer service.
Credit Card expiration date was not valid. Error occurs when saving
a customer payment method.
The system was unable to load the requested payment method.
Most likely the method was deleted by another processes.
The system was unable to load the requested payment method.
Possible corruption issue. If possible, delete the method and
resave. Otherwise, contact customer service.
The system was unable to store the payment method. Could be a
temporary system issue. Try resaving payment method.
The system was unable to store the payment method. Most likely
cause is that the payment method no longer exists. Check that the
payment method has not been deleted by another process.
Paymentech returned an unmapped error.
UCAF Data was indicated but not supplied
Hard decline from Paymentech
Authorizer needs more information for approval.
Hold Card from Paymentech
Authorizer didn't respond within allotted time.
Paymentech Error: Account #/mag stripe is invalid.
Expiration date is either incorrect format or prior to today.
Paymentech Error: Invalid International Control Account number.
Paymentech Error: Invalid American Banking Association number.
Paymentech Error: The Personal ID Number for a debit transaction is
incorrect.
Paymentech Error: The Bank Merchant ID is incorrect.
Paymentech Error: The merchant ID is not valid or active.
Paymentech Error: Amount is either: equal to 0, has no decimal, has
decimal in wrong place, or has multiple decimals.
Paymentech Error: The transaction format isn't valid, typically invalid
SIC code.
Paymentech Error: Authorization center cannot be reached.
9 of 12
Error Messages
Error ID
65215
65216
65217
65218
65220
65240
65248
65308
65309
65310
65311
65312
65313
65314
65315
65317
65318
65319
65320
65321
65322
65323
User Message
Hold Card - Lost/Stolen Card.
(P215)
Invalid Personal ID (P214)
Amount Exceeds Card Limit (P217)
Authorizer Denies Transaction.
(P218)
Call Support. Fatal
communications error. (P220)
Do Not Honor. Card Not on File.
(P240)
CVC2/CID Rejected by Issuer.
(P248)
Invalid Card. MOD 10 Failed.
(P308)
Invalid Terminal ID. (P309)
Invalid Card Number Length.
(P310)
Invalid Terminal File. (P311)
Invalid Card Number BIN. (P312)
Merchant/Store # Not On File.
(P313)
Processor Couldn't Read Store File
(P314)
Invalid Trans Code for Card Type.
(P315)
Invalid Card. Discover Not Setup.
(P317)
Invalid Card Length. (P318)
Invalid Amount. (P319)
Invalid Format. Missing Field
Separator for ETX. (P320)
Invalid/Missing Auth. Code. (P321)
65327
Invalid Industry Date. (P322)
Invalid Transaction Class. Not F.
(P323)
Invalid Market Specific Data
Indicator. (P324)
Invalid Duration. (P325)
Invalid Perferred Customer
Indicator. (P326)
Invalid Card Type Reversal. (P327)
65328
Invalid Industry Incremental (P328)
65329
Invalid Industry Incremental. (P329)
65330
Invalid Incremental Reversal.
(P330)
65324
65325
65326
Technical
Paymentech Error: Card has been reported lost or stolen.
Paymentech Error: Personal ID code is incorrect.
Paymentech Error: Amount requested exceeds credit limit.
Paymentech Error: Transaction is not valid for this authorizer.
Paymentech Error: Fatal communications error.
Paymentech Error: Retail Issued account number does not exist.
Paymentech Error: CVC2 or CID data entered is not correct for the
card.
Paymentech Error: Account #/mag stripe does not pass MOD 10
check.
Paymentech Error: Terminal ID not found in terminal file.
Paymentech Error: Account #/mag stripe is incorrect length.
Paymentech Error: Host couldn't read terminal file within specified
time.
Paymentech Error: Account # can't be found in BIN table.
Paymentech Error: 12 digit merchant/store # not found in file.
Paymentech Error: Host couldn't read store file within specified time.
Paymentech Error: Tran Code not supported for that card type.
Paymentech Error: Discover not set up for draft capture or no
subscriber #.
Paymentech Error: Length does not match routing table specification.
Paymentech Error: Transaction amount all zeroes.
Paymentech Error: Missing field separator or ETX.
Paymentech Error: Authorization code is missing or incorrect on a
prior sale.
Paymentech Error: Industry specific data is incorrect.
Paymentech Error: Transaction class is not "F" financial.
Paymentech Error: Market specific data indicator is not H, A, F or P.
Paymentech Error: Duration is not 01-99
Paymentech Error: Preferred customer indicator is not Y or N.
Paymentech Error: A Partial Reversal was attempted for a non-Visa
card.
Paymentech Error: An incremental authorization was attempted for
an industry other than Lodging or Auto Rental.
Paymentech Error: An reversal authorization was attempted for an
industry other than Lodging, Auto Rental or MO/PO.
Paymentech Error: An Incremental or Reversal authorization was
attempted against a transaction that did not qualify for PSIRF.
10 of 12
Error Messages
Error ID
65331
65332
65333
User Message
Invalid Folio Number. (P331)
Invalid Charge Descriptor. (P332)
Invalid Industry/No Show. (P333)
65334
Invalid Card Type / Market. (P334)
65335
65336
65337
Invalid Vehicle Number. (P335)
Invalid Odometer Number. (P336)
Invalid Drivers Number. (P337)
65338
65340
Invalid or Missing Order Number
(P338)
Invalid Combination of SIC/MO/TO.
(P339)
Reversal Already Exists. (P340)
65341
Invalid Reversal Amount. (P341)
65342
65343
Invalid PIN Cabability. (P342)
Invalid Authorization Characters.
(P343)
Invalid Transaction ID. Non-digits.
(P344)
Transaction ID Doesn't Match
Original Auth. (P345)
Invalid BankNet Ref. Number.
(P346)
Invalid Duration Value (P347)
Market Specifier Doesn't Match
CPS Type. (P348)
Industry Code Doesn't Match CPS
Type. (P349)
Invalid Reversal Method (Manual)
(P350)
Invalid SIC for Premier
MasterCard. (P343)
Retail Issued Account Not Valid.
(P357)
American Express Not Supported
by Merchant. (P358)
Diners Capture Not Allowed by
Merchant. (P359)
Carte Blanche Not Allowed by
Merchant (P360)
JCB Not Allowed by Merchant.
(P361)
Invalid Electronic Commerce Data
(P362)
Card Code Data Error (P376)
Please Re-try or Call In. Auth
Center Not Reached. (P602)
65339
65344
65345
65346
65347
65348
65349
65350
65353
65357
65358
65359
65360
65361
65362
65376
65602
Technical
Paymentech Error: Folio number is not a 6 digit numeric field.
Paymentech Error: Charge descriptor field is not 2 digit numeric.
Paymentech Error: A No Show transaction was attempted for an
industry other than lodging or auto rental
Paymentech Error: Market specific data is present for other than Visa
card.
Paymentech Error: Vehicle number is not 5 digit numeric field.
Paymentech Error: Odometer field is not 6 digit numeric
Paymentech Error: Driver number is not 6 digit numeric or 4 digit with
2 leading spaces.
Paymentech Error: Order number is missing or contains invalid data.
Paymentech Error: Invalid iTransaction Typei indicator for a mail
order only SIC code under industry specific data.
Paymentech Error: A second reversal authorization was attempted,
only one is permitted.
Paymentech Error: Reversal amount is invalid or greater than original
authorization amount.
Paymentech Error: PIN capability field contains invalid data.
Paymentech Error: Auth Characteristics Indicator field contains
invalid data.
Paymentech Error: Transaction ID field contains non-numeric data.
Paymentech Error: Transaction ID does not match original
authorization.
Paymentech Error: BankNet reference number contains invalid data
or does not match original authorization.
Paymentech Error: Duration field greater than 99.
Paymentech Error: Market specific data indicator does not match
CPS type.
Paymentech Error: Industry code does not match custom payment
service type.
Paymentech Error: Incremental or reversal auths are not permitted
for manual entry.
Paymentech Error: Must use a special SIC code to accept Premier
MC cards.
Paymentech Error: Retail Issued account number not valid for that
Store number.
Paymentech Error: Amex capture not equal to C, A or P or SE#
missing.
Paymentech Error: Diners capture not equal to C or D.
Paymentech Error: Carte Blanche capture is not equal to C or D.
Paymentech Error: JCB capture is not equal to C or D.
Paymentech Error: Invalid Electronic Commerce Data.
Paymentech Error: CVD Data Error
Paymentech Error: Authorization center cannot be reached.
11 of 12
Error Messages
Error ID
65907
65999
70001
70002
70003
70004
70005
User Message
Batch not in balance
Client Not Setup Properly (P999)
Currency is required.
Error communicating with
processor.
Invalid currency code
Invalid source currency selected
70010
Invalid destination currency
selected
Unable to pull rate list: [reason]
Merchant account does not have
multi-currency support enabled.
Postal Code is required
Postal Code may not exceed 9
characters
Merchant not configured
70011
Merchant not configured
70012
Merchant not configured
70013
Unsupported Card Type
89000
Batch Rejected by Global
(Unmapped Response)
Batch not in balance (G0NB)
70006
70007
70008
70009
89001
900001 Internal Server Error
Technical
Paymentech Error: Client identifier field is not on system.
Currency is required to processing on the Planet Payment platyform
Error communicating with planet payment. Have support check
event log.
Verify that you are send a numeric currency code
The source currency specified was not valid. A 3 digit currency code
must be entered.
The destination currency specified was not valid. A 3 digit currency
code must be entered.
Error pulling rate from Planet Payment
Merchant account does not have multi-currency support enabled.
Contact customer service for details.
A postal code is required to process on Planet Payment
The maximum length of a postal code is 9 characters on Planet
Payment
Merchant account is not configured correctly. Contact customer
service. (Username missing)
Merchant account is not configured correctly. Contact customer
service. (Password missing)
Merchant account is not configured correctly. Contact customer
service. (Terminal ID missing)
Only Visa and Mastercard are supported by Planet Payment.
Transaction must be processed domestically.
Global reject batch with an unmapped response code/action code.
Global reject batch with INV BAL/SETL action code. Check
transaction amounts.
Unable to load an internal server component. This error is nonrecoverable and requires immediate support attention.
12 of 12
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising