Bank and SecurePay Response Codes

Last updated: 19/07/2013

Bank Response Codes for Credit Card Transactions

Response Text

Code

Code

Response Text

APPROVED
00
11
77

Approved
Approved VIP (not used)
Approved (ANZ only)

08
16

01
02
03
04
05
06
07
09
10
12
13
14
15
17
18
19
20
21
22
23
24

Refer to Card Issuer

Refer to Issuers Special Conditions
Invalid Merchant
Pick Up Card
Do Not Honour
Error
Pick Up Card, Special Conditions
Request in Progress
Partial Amount Approved
Invalid Transaction
Invalid Amount
Invalid Card Number
No Such Issuer
Customer Cancellation
Customer Dispute
Re-enter Transaction
Invalid Response
No Action Taken
Suspected Malfunction
Unacceptable Transaction Fee
File Update not Supported by
Receiver
Unable to Locate Record on File
Duplicate File Update Record
File Update Field Edit Error
File Update File Locked Out
File Update not Successful
Format Error
Bank not Supported by Switch
Completed Partially
Expired CardPick Up
Suspected FraudPick Up
Contact AcquirerPick Up
Restricted CardPick Up
Call Acquirer SecurityPick Up
Allowable PIN Tries Exceeded
No CREDIT Account
Requested Function not Supported

Honour with ID
Approved, Update Track 3 (not used)

DECLINED

25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

SecurePay Pty Ltd

41
42
43
44
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

Lost CardPick Up
No Universal Amount
Stolen CardPick Up
No Investment Account
Insufficient Funds
No Cheque Account
No Savings Account
Expired Card
Incorrect PIN
No Card Record
Trans. not Permitted to Cardholder
Transaction not Permitted to Terminal
Suspected Fraud
Card Acceptor Contact Acquirer
Exceeds Withdrawal Amount Limits
Restricted Card
Security Violation
Original Amount Incorrect
Exceeds Withdrawal Frequency Limit
Card Acceptor Call Acquirer Security
Hard CapturePick Up Card at ATM

68
75
86
87
88
89
90
91
92
93
94
95
96
97
98
99

Response Received Too Late

Allowable PIN Tries Exceeded
ATM Malfunction
No Envelope Inserted
Unable to Dispense
Administration Error
Cut-off in Progress
Issuer or Switch is Inoperative
Financial Institution not Found
Trans Cannot be Completed
Duplicate Transmission
Reconcile Error
System Malfunction
Reconciliation Totals Reset
MAC Error
Reserved for National Use

Page 2 of 8

SecurePay Payment Server Response Codes

Response Text

Code

Description
DECLINED

100
101

Invalid Transaction Amount

Invalid Card Number

102

Invalid Expiry Date Format

103
104

Invalid Purchase Order

Invalid Merchant ID

106

Card type unsupported

109

Invalid credit card CVV number format

110

Unable To Connect To Server

111

Server Connection Aborted During

Transaction

112

Transaction timed out By Client

113

General Database Error

114

Error loading properties file

115

Fatal Unknown Server Error

116
117

Function unavailable through Bank

Message Format Error

118

Unable to Decrypt Message

119

Unable to Encrypt Message

123

Gateway Timeout

124

Gateway Connection Aborted During

Transaction

125

Unknown Error Code

126

Unable to Connect to Gateway

131

Invalid Number Format

132

Invalid Date Format

133

Transaction for refund not in database

134

Transaction already fully refunded / Only

$x.xx available for refund
Transaction for reversal not in database

135

SecurePay Pty Ltd

If payment transaction amount is non-integer, negative, or zero

If credit card number contains characters other digits, or bank
does not recognize this number as a valid credit card number
If expiry date does not follow the format MM/YY or contains an
invalid date
If purchase order is an empty string
If Merchant ID does not follow the format XXXDDDD, where X is
a letter and D is a digit, or Merchant ID is not found in
SecurePays database.
Merchant is not configured to accept payment from this
particular Credit Card type
CVV Number contains character other than digits or contains
more than 6 characters
Produced by SecurePay Client API when unable to establish
connection to SecurePay Payment Gateway
Produced by SecurePay Client API when connection to
SecurePay Payment Gateway is lost after the payment
transaction has been sent
Produced by SecurePay Client API when no response to
payment transaction has been received from SecurePay
Payment Gateway within predefined time period (default 80
seconds)
Payment Gateway was unable to read or write information to the
database while processing the transaction
Payment Gateway encountered an error while loading
configuration information for this transaction
Transaction could not be processed by the Payment Gateway
due to unknown reasons
The bank doesnt support the requested transaction type
SecurePay Payment Gateway couldnt correctly interpret the
transaction message sent
SecurePays security methods were unable to decrypt the
message
SecurePays security methods were unable to encrypt the
message
Produced by SecurePay Payment Gateway when no response
to the transaction has been received from bank gateway within
predefined time period
Produced by SecurePay Payment Gateway when connection to
bank gateway is lost after the payment transaction has been
sent
Produced by the bank gateway, textual description of the actual
problem is stored in the database
SecurePay Payment Gateway couldnt establish a connection to
Bank Gateway
A sting entered cannot be parsed as an integer. I.e. string must
contain only digits, or preceding - sign
Date entered does not follow the format DD/MM/YYYY, where
DD is the 2-digit day of the month, MM is the 2-digit month
number, and YYYY is the 4-digit year number; also if month is <
1 or > 12, or date is < 0 or > maximum days in that month
Refund operation requested, and the original approved
transaction is not found in the database
Refund operation is requested, and the given transaction has
already been fully or partially refunded
Reversal operation requested, and the original approved
transaction is not found in the database

Page 3 of 8

SecurePay Payment Server Response Codes

Response
Code

Response Text

Description
DECLINED

136

Transaction already reversed

137

Pre-auth transaction not found in database

138

Pre-auth already completed

139

No authorisation code supplied

140

Partially refunded, Do refund to complete

141

No transaction ID supplied

142

Pre-auth was done for smaller amount

143

Payment amount smaller than minimum

144

Payment amount greater than maximum

145

System maintenance in progress

146

Duplicate Payment Found

147

No Valid MCC Found

148
149

Invalid Track 2 Data

Track 2 Data Not Supplied

151

Invalid Currency Code

152

Multi-currency not supported by bank

153

External Database Error

157
158
159
160
175

Fraud Check Passed

Fraud Check Error
Suspected Fraud
Cardholder could not be authenticated
No Action Taken

176
179
190

Merchant Not Enrolled in 3D Secure

User Cancelled Payment
Merchant Gateway Not Configured

195
199

Merchant Gateway Disabled

Merchant Gateway Discontinued

SecurePay Pty Ltd

Reversal operation requested, and the given transaction has

already been reversed
Complete operation requested, and the matching approved preauth transaction is not found in the database
Complete operation requested, and the given pre-auth has
already been completed
Client performing Complete transaction did not provide Pre-auth
Code from original pre-auth transaction
Reversal operation is requested, and the given transaction has
already been partially refunded
Client performing Refund/Reversal transaction did not provide
original payments Bank Transaction ID
Complete operation was requested but the amount specified is
greater the pre-authorised amount
The payment amount was smaller than the minimum accepted
by the merchant
The payment amount was greater than the maximum accepted
by the merchant
The system maintenance is in progress and the system is
currently unable to process transactions
The system located a transaction that seems to be a duplicate
of the current attempt. Transaction is not passed to bank, and
customer should contact their merchant before making payment.
(Used in SecureBill / IVR only at present.)
The merchant does not have a valid MCC (Merchant Category
Code) set up to complete this transaction (Refers to Recurring
transactions only at present).
If track 2 data is invalid length.
Track 2 data was not supplied and the transaction cannot be
completed (Refers to Card Present transactions only at
present).
The currency code supplied does not match the format required
by SecurePay. Check the list of accepted currency codes.
The financial institution used for this payment only accepts
payments in Australian dollars (AUD).
A database error has occurred outside the SecurePay Payment
Server (e.g. DEFT, etc)
Fraud check successful. No suspected fraud.
Cannot evaluate transaction for fraud.
Transaction suspected to be fraudulent.
The payment was held in the processing queue too long and
was rejected without processing. Usually a symptom of slow
bank responses. Additional terminal IDs may help solve this
problem if it occurs frequently.

The gateway for the merchant has been reserved, but not yet
configured to be live by SecurePay staff.
SecurePay has disabled the merchant gateway.
SecurePay has discontinued the merchant gateway.

Page 4 of 8

SecurePay Payment Server Response Codes

Response
Code

Response Text

Description
APPROVED

000

Normal

Message processed correctly (check transaction

response for details).

DECLINED
504

Invalid Merchant ID

505

Invalid URL

510

Unable To Connect To Server

511

Server Connection Aborted During

Transaction

512

Transaction timed out By Client

513
514

General Database Error

Error loading properties file

515

Fatal Unknown Error

516

Request type unavailable

517

Message Format Error

524

Response Format Error

545

System maintenance in progress

550

Invalid password

575
577

Not implemented

580

Process method has not been called

594

Duplicate Transmission

595

Merchant Disabled

Too Many Records for Processing

SecurePay Pty Ltd

If Merchant ID does not follow the format XXXDDDD,

where X is a letter and D is a digit, or Merchant ID is
not found in SecurePays database.
The URL passed to either Echo, Query or Payment
object is invalid.
Produced by SecurePay Client API when unable to
establish connection to SecurePay Payment Gateway
Produced by SecurePay Client API when connection
to SecurePay Payment Gateway is lost after the
payment transaction has been sent
Produced by SecurePay Client API when no response
to payment transaction has been received from
SecurePay Payment Gateway within predefined time
period (default 80 seconds)
Unable to read information from the database.
Payment Gateway encountered an error while loading
configuration information for this transaction
Transaction could not be processed by the Payment
Gateway due to unknown reasons
SecurePay system doesnt support the requested
transaction type
SecurePay Payment Gateway couldnt correctly
interpret the transaction message sent
The client could not understand the response
message.
The system maintenance is in progress and the
system is currently unable to process transactions
The merchant has attempted to process a request with
an invalid password.
This functionality has not yet been implemented
The maximum number of allowed events in a single
message has been exceeded.
The process() method on either Echo, Payment or
Query object has not been called
A transaction with the same details has already been
processed.
SecurePay has disabled the merchant and the
requests from this merchant will not be processed.

Page 5 of 8

SecurePay Direct Entry Response Codes

Response
Code

Response Text

Description
APPROVED

00

Transaction Received

200
201
203
204

Invalid Transaction Amount

No DDA Found
Invalid Reference Number
Invalid Merchant ID

205
213

DDA Expired
General Database Error

217

Message Format Error

225
228
243

Transaction Rejected (Unknown

response)
No DDA With Merchant
Amount Lower Than Minimum

244

Amount Higher Than Maximum

246

Duplicate Payment Found

249

Invalid Payor ID

The transaction was received and will be sent off for

processing at the end of the day.

DECLINED

SecurePay Pty Ltd

If Merchant ID does not follow the format XXXDDDD,

where X is a letter and D is a digit; or if Merchant ID is
not found in the merchant database.
Direct Debit Server was unable to read or write
information to the database while processing the
transaction
Direct Debit Server received a message with invalid
data.

DDA is inactive.
The payment amount was lower than the minimum
accepted.
The payment amount was higher than the maximum
accepted.
The system located a transaction that seems to be a
duplicate of the current attempt. Transaction is not
passed to bank, and customer should contact their
merchant before making payment. (Used in SecureBill
/ IVR only at present.)

Page 6 of 8

SecurePay Periodic Server Response Codes

Response
Code

Response Text

Description
DECLINED

300

Invalid Amount

301

Invalid Credit Card Number

302

Invalid Expiry Date

303

Invalid Periodic Client ID

304

Invalid Merchant ID

305

Invalid BSB Number

306

Invalid Account Number

307

Invalid Account Name

308

No Matching DDA Found

309

Invalid CVV Number

313

General Database Error

314

Unable to Read Properties File

316

Invalid Action Type Requested

318

Unable to Decrypt Account Details

327

Invalid Periodic Payment Type

328

Invalid Periodic Frequency

329

Invalid Number of Payments

332

Invalid Date Format

333

Triggered Payment Not Found

346

Duplicate Client ID Found

SecurePay Pty Ltd

If payment transaction amount is non-integer, negative,

or zero. (May be zero (0) for trigger actions, when
default amount will be used.)
Credit card number is not supplied, wrong length, or
does not pass Luhn algorithm.
Expiry date does not follow format MM/YY, where MM is
the 2-digit month (01-12) and YY is the 2-digit year.
Client ID not provided, longer than 20 characters, or
contains spaces.
Merchant ID does not follow format XXXDDDD for credit
card payments, or XXXDD for direct entry, where X is a
letter and D is a digit; or merchant ID not in database.
BSB does not follow format DDDDDD, or DDD-DDD,
where D is a digit.
Account number not provided, greater than 9 digits, or
contains non-digit characters.
Account Name is mandatory for DE Credit payments,
and optional for DE Debits. Must be less than 32
characters if supplied.
A periodic DE Debit payment must match an existing
DDA stored in our database for the merchant. DDAs
can be added via the Merchant Login. DDA expiry date
must be after the final periodic payment date.
CVV is optional for credit card payments, but if provided,
must be either 3 or 4 digits.
A database error occurred while processing your
request. Retry, or contact SecurePay.
A properties file was not found or could not be read.
Retry, or contact SecurePay.
The server does not support the action type requested.
Check user manual for allowed values.
The card number or account details could not be
decrypted. Retry, or contact SecurePay.
The Periodic type requested is not supported. Check
user manual for allowed values.
The Periodic frequency requested is not valid. Check
user manual for allowed values.
Number of payments must be 1 or more for day-based
and calendar-based payments.
A supplied date does not follow format YYYYMMDD,
where values conform to standard calendar rules; or the
server could not correctly interpret a date.
Triggered payment Client ID requested does not match
a stored triggered payment for the merchant.
Client ID being added is not unique for the merchant.

Page 7 of 8

Bank Gateway Response Codes

Response
Code

Response
Code

Response Text

Response Text

DECLINED
900
901
902
903
904
905
906
907
908
909
910
913
914
915
916
917
918
919
922
923
924
925
926

Invalid Transaction Amount

Invalid Credit Card Number
Invalid Expiry Date Format
Invalid Transaction Number
Invalid Merchant/Terminal ID
Invalid E-Mail Address
Card Unsupported
Card Expired
Insufficient Funds
Credit Card Details Unknown
Unable to Connect to Bank
Unable to Update Database
Power Failure
Fatal Unknown Gateway Error
Invalid Transaction Type Requested
Invalid Message Format
Encryption Error
Decryption Error
Bank is Overloaded
Bank Timed Out
Transport Error
Unknown Bank Response Code
Gateway Busy

SecurePay Pty Ltd

928
932
933
936
937
938
939
941
946
951
958
960
961
962
970
971
972
973
974
975
976
977
978

Invalid Customer ID
Invalid Transaction Date
Transaction Not Found
Transaction Already Reversed
Transaction Cannot Be Authorised
Pre-auth Already Completed
Invalid Auth Code
Invalid Transaction ID Supplied
Reference Number Currently In Use
Transaction Not Permitted To Terminal
Fraud Check Error
Contact Card Issuer
Transaction Pending
Transaction Voided
File Access Error
Invalid Flag Set
Pin-pad/Gateway Offline
Invoice Unavailable
Gateway Configuration Error
No Action Taken
Unknown Currency Code
Too Many Records for Processing
Merchant Blocked

Page 8 of 8