mPAY24 provides within each operation response the
status element specifies if the operation itself was successful or not. It does not specify if the transaction was successful or not.
The operation was ok (no error occurred).
The operation was not ok (see
The following list contains a short description of the currently returned values of
returnCode. Additionally some codes are described in detailed afterwards. The list can
be extended by mPAY24 at any time.
|0||The transaction was ok (no error occurred).|
|1||The transaction was declined by the external payment interface.|
|2||The transaction was blocked.|
|3||The merchant’s IP address is not white listed.|
|4||The merchant id is locked.|
|5||The desired payment system is not active.|
|6||A mandatory parameter is missing.|
|7||The parameter supplied is not valid.|
|8||The operation is not supported.|
|9||The payment method mismatches.|
|10||The transaction was not found.|
|11||The transaction has been processed and can not be processed again.|
|12||The temporary cache data are invalid due to expiration.|
|13||The MDXI XML stream could not be validated.|
|14||The parameter |
|15||The credit card number is not plausible.|
|16||The Maestro card number is not plausible.|
|17||The provided IBAN is not plausible.|
|20||mPAY24 payment profile could not be found.|
|21||mPAY24 Profile is not activated.|
|22||mPAY24 Profile FLEX is not activated.|
|23||The maximum number of payment profiles of a customer is reached.|
|30||The token has not been found or has already been used.|
|31||The token is invalid due to missing or incorrect data.|
|32||The token has not been used and is expired.|
|33||The token data could not be encrypted.|
|34||The token data could not be decrypted.|
|40||Withdraw operation is not allowed for the merchant.|
|50||The transaction has already been cleared.|
|60||The total amount of all credits exceeds the clearing amount.|
|61||The total amount of all clearing exceeds the reservation amount.|
|99||An error during the communication occurred.|
|100||The external payment interface returned an error.|
OK indicates that a operation was processed. It does not specifies the
transactions state. If the
OK was returned, the transaction state is either
additionally specified or can be received via the Confirmation Interface.
If a profile is created or updated during a payment process, following ReturnCodes are possible:
|The transaction was ok and the profile created|
|The transaction was ok and the profile updated|
|The transaction was ok but the profile was not stored/updated|
The transaction was declined by the specific external payment interface and can not be
processed any more. No technical problem occurred during the transaction.
The merchant should advise the customer to refer to his issuer about the reason of the
An error during the communication occurred. The operation was not successful and in most
cases the transaction has not been processed. For further questions about a transaction
INTERNAL_ERROR contact the mPAY24 support.
This error is also returned if the external payment interface returns an
incorrect or unknown error code.
An error occurred while processing through the external payment interface and a correct
error code was returned by this interface. The operation was not successful and the
transaction has not been processed.
The return value
errText may contain additional information supplied by the external
payment interface if a public error code (or message) was defined by the interface. If
possible, the error message is returned in the language defined upon request (default:
In case of a non public error code as defined by the external payment interface, a general
message will be provided, since the merchant or respectively the customer is not allowed
to be notified about the reason of the error.
Updated over 1 year ago