TransactionStatus
|
Description
|
Notes
|
0
|
OK
|
|
1
|
Technical error
|
|
2
|
Input error
|
One or more of the input parameters is missing or has the wrong format or value.
Comment: This is an implementation error.
|
3
|
Wrong AgreementID
|
AgreementID not found
Comment: This is a configuration error or implementation error (e.g. sending request to the wrong system)
|
5
|
Unauthorized action
|
The merchant/aggregator is not permitted to perform the requested operation.
Comment: This is a implementation error. The provided AgreementID is not allowed to execute this action.
|
5
|
Unauthorized action
|
The merchant/aggregator is not permitted to perform the requested operation.
|
6
|
Client account not found
|
Comment: The end user has no account in this system.
|
7
|
Client account blocked
|
|
8
|
Insufficient funds
|
The end user has not enough money on the selected account to perform the purchase.
|
11
|
Client account is expired
|
Comment: This will rarely occur. Must be treated the same way as status 7.
|
53
|
Connection limit exceeded
|
The number of allowed concurrent active requests has been exceeded.
This is implemented to prevent a single acquirer to use 100% of the API capacity. The request may be retried later. Avoid this problem by reducing traffic and/or implement flow control in your application.
Comment: Try again.
|
60
|
Acknowledge
|
Valid request received and queued for processing. Final response will be sent to the PostbackURL.
Comment: Only used for asynchronous payments.
|
61
|
Deprecated
|
Replaced with status code 63 (Generic decline).
|
62
|
Deprecated
|
Replaced with status code 63 (Generic decline).
|
63
|
Generic decline
|
This status code is returned when a payment transaction is rejected and the system either cannot or will not specify the exact reason.
Examples of conditions that causes this status code to be returned include:
- A purchase amount limit has been exceeded
- Accumulated transaction amount has been exceeded
- Suspected fraud
- Generic errors returned by external (3rd party) payment instruments
|
99
|
Rejected by business rule
|
Payment is currently not available to the requested payee/client/subscriber/ on the current payment channel.
Comment: This is a general error, and should be treated as status 6.
The customer is not allowed to use this payment instrument.
|
105
|
Deprecated
|
Replaced with status code 6
|
107
|
Deprecated
|
Replaced with status code 1
|
110
|
Order not found
|
The order search for with the CheckOrder function could not be found
|
114
|
Third party error.
|
Third party error for external account.
Comment: This should be treated as “host down”, meaning that the account provider is not responding for the time. This is not a permanent error and retries are possible.
|
116
|
No suitable payment instrument found
|
The user does not have a payment instrument / account that is permitted in this scenario.
Comment: Should be treated as status 6.The customer may have an account, but cannot use the account in this scenario.
|
117
|
Max number of purchases for Easy Registration exceeded
|
The user needs to register on the portal to continue using the system
Comment: This is a customer error response. Due to anti fraud restrictions, the payment will not be approved. Should be treated as status 6.
|
118
|
Max purchase amount for Easy registration exceeded
|
The purchase amount is higher than permitted amount for users that are not fully registered.
Comment: This is a customer error response. Due to anti fraud restrictions, the payment will not be approved. Should be treated as status 6.
|
119
|
Deprecated
|
Replaced with status code 6
|
120
|
User not identified by mobile operator, MNO billing disabled
|
Cannot charge to phone bill because the mobile operator could not identify the user of the given MSISDN
Comment: This is a customer error response. Should be treated as status 6.
|
121
|
MSISDN does not belong to a WyWallet operator
|
The MSISDN / phone number does not belong to a 4T telecom operator (Telia, Telenor,Tele2 or 3.)
Comment: This is a customer error response. Should be treated as status 6.
|
