Skip to main content
Skip table of contents

Pay-me SDK error messages

Error Codes

Pay-me SDK handles different errors that interrupt the authorization flow, these errors are delivered to the merchant and can be identified by the error code found in the resultCode and resultMessage parameter of the PaymeResponse object.

Error Codes

Error Message

Description

00

AUTORIZACION_EXITOSA

The authorization was successfully completed.

01

AUTORIZACION_DENEGADA

The authorization was denied.

101

ERROR_INICIALIZAR_SDK

A problem occurred while initializing the SDK.

The merchant sent one or more invalid parameters when invoking the Payme SDK.

The merchant uses a currency that has not been configured.

102

ERROR_SERVICIO_CONFIGURADOR

A problem occurred in the communication with the Configuration service.

Connection error or timeout.

Error in the data provided by the service.

103

ERROR_SERVICIO_INTENTO_PAGO

A problem occurred in the communication with the attempted payment service.

Connection error or timeout

Error in the data provided by the service.

104

ERROR_SERVICIO_SCORING

A problem occurred in the pre-authentication process (routeEngine service).

Connection error or timeout.

Error in the data provided by the service.

105

ERROR_PROCESO_AUTENTICACION

A problem occurred in the authentication process (3DS SDK component).

106

ERROR_PROCESO_AUTORIZACION

A problem occurred in the authorization process (Charges service).

Connection error or timeout.

Error in the data provided by the service.

107

ERROR_GENERAL

A general error occurred.

108

VOLVER_AL_COMERCIO

The transaction was interrupted. The user decided to return to the store.

109

TRANSACCION_RIESGO_ALTO

The transaction was rejected. The transaction is high risk and failed to pass the pre-authentication rules.

110

AUTHENTICACION_NO_EXITOSA

The transaction was rejected. The user could not be authenticated in the 3DS authentication process.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.