Managing application errors

Managing application errors

Standardized application error messages can be sent in the SOAP response message associated with a call.

They consist of an error code and a problem description.

The table below lists the error codes that can be returned in the responseCode attribute:

Error code responseCodeDetail Description
0 Action successfully completed The format of the query is valid. However, it does not mean that the payment has been accepted.
1 Unauthorized request Action not authorized.
2 Bad Parameter Invalid attribute.
3 Bad Request The request could not be processed.
10 Transaction was not found Transaction not found.
11 Bad transaction status Incorrect transaction status.
12 Transaction already exists Transaction already exists.
13 Date is too far from current UTC date Incorrect date (the value of the 'submissionDate' attribute if too far from the current date).
14 Nothing has changed No changes have been made.
15 Too much results Too many results.
16 Duplicate forbidden The initial transaction has been refused due to forbidden duplication. Ask the holder to use another payment method.
20 Bad amount Invalid amount in the 'amount' attribute.
21 Unknown currency Invalid currency in the 'currency' attribute.
22 Unknown card type Unknown card type.
23 Invalid Expiration Date Invalid date in the 'expiryMonth' and/or 'expiryYear' attributes.
24 CVV Mandatory The 'cvv' is mandatory.
25 Contract not found Unknown contract number.
26 Invalid card number Invalid card number.
30 Payment token not found Token not found.
31 Invalid payment token (cancelled, …) Invalid token (canceled, empty, etc.)
32 SubscriptionID was not found The 'subscriptionId' attribute not found.
33 Invalid Subscription Invalid 'rrule' attribute.

or

Subscription already canceled

34 Payment token already exists Token already exists.
35 Payment token creation declined Creation of a rejected token.
36 Payment token purged Purged 'paymentToken' attribute.
40 Amount not authorized The 'amount' attribute is not authorized.
41 Card range not found Card range not found.
42 Not enough credit Insufficient balance of the payment method.
43 No credit Refund is not authorized for this contract.
50 Brand not found No brand found.
51 Merchant not enrolled Merchant not enrolled.
52 Invalid ACS Signature Invalid ACS signature.
53 Technical error 3DS 3DS technical error.
54 Wrong Parameter 3DS Incorrect 3DS parameter.
55 3DS Disabled 3DS deactivated.
56 PAN not found PAN not found.
57 Acquirer transient data not valid The specific data that must be transmitted to the acquirer is invalid.
75 Cancel operation not available anymore, try a refund Cancellation impossible, please try a refund.
76 Refund operation not yet available, try a cancel Refund impossible, please try a cancellation.
77 In order to refund this transaction, please contact RBM at the following address: solicitudes@rbm.com.co The Redeban acquirer does not authorize refunds for a MAESTRO card. Please contact RBM at: solicitudes@rbm.com.co
78 In order to refund this transaction, please contact Credibanco at the following address: atrecom@credibanco.com The Credibanco acquirer does not authorize refunds for a AMEX cards. Please contact Credibanco at: atrecom@credibanco.com
79 In order to refund this transaction, please contact Davivienda at the following adress: cempresarial@davivienda.com The Redeban acquirer does not authorize refunds for a Diners cards. Please contact Davivienda at: cempresarial@davivienda.com
80 Transaction(s) not sent yet in CNAB/Remessa file Refunds not authorized as the transaction is not recorded in a CNAB/Remessa file (Boleto payment).
81 Manual capture not allowed for this type of contract Manual capture not supported within this scheme.
82 Refund not allowed on this transaction type Credit operations are not authorized for this type of transactions (VERIFICATION, CREDIT).
83 Refund not allowed on unpaid transaction Refund impossible for an unpaid transaction.
97 OneyWsError OneyWs error.
98 Bad request Id Invalid RequestId attribute.
99 Undefined Error Unknown error.

Explanation of the error codes

  • 0 - Action successfully completed

    Indicates that the format of the request is valid.

    WARNING: Even if the responseCode is set to 0, you must analyze the following fields in order to determine if the payment was successful:

    1. commonResponse.transactionStatusLabel to know the transaction status,
    2. authorizationResponse.result to know the reason why the authorization request was refused,
    3. paymentResponse.paymentError to know the other reasons for refusal.

  • 1- Action not authorized

    Indicates that your shop is not allowed to create transactions in PRODUCTION mode.

  • 2 - Invalid parameter

    This error code is returned when an attribute is invalid. It is returned with an error of the param type that provides additional information about the attribute with an error.

    Error code Description Explanation
    33 The 'paymentSource' parameter invalid in case of a subscription Source of the transaction invalid for a subscription.

    The possible values are “EC”, “MOTO”, “CC” or “OTHER”.

    34 The 'scheme' parameter invalid in case of a token creation. Card type invalid when creating a token.
    35 The phoneNumber' parameter is invalid. Invalid buyer’s phone number.
    36 The 'email' parameter is invalid. The buyer’s e-mail is invalid.
    37 The 'zipCode' parameter is invalid. The buyer’s postal code is invalid.
    38 The 'cellPhoneNumber' parameter is invalid. The buyer’s cell phone number is invalid.
    50 The 'shopId' parameter is invalid. The shop ID is incorrect.
    51 The 'submissionDate' parameter is invalid. The date and UTC time of the transaction are missing.
    66 The 'contractNumber' parameter is invalid. The number of the merchant acceptance agreement is invalid.
    82 The 'initialAmount' parameter is invalid. The initial amount of the subscription is invalid (less than 0).
    83 The 'initialAmountNumber' parameter is invalid.

    The number of installments that is applied to the amount initialAmount.

    This attribute is mandatory if the attribute value of initialAmount is set.

    84 The effectDate' parameter is invalid. The effective date of the subscription is invalid. The date cannot be in the past.
    85 The commission' parameter is invalid. Parameter missing, mandatory for Boleto in Brazil.
    90 The 'enrolled' parameter is invalid. The enrollment status of the cardholder us invalid.
    92 The 'eci' parameter is invalid. The e-commerce indicator is invalid.
    93 The 'xid' parameter is invalid. The 3DS transaction number is invalid.
    94 The 'cavv' parameter is invalid. The ACS signature is invalid.
    95 The 'cavvAlgorithm' parameter is invalid. The algorithm for Cardholder Authentication Verification Value (CAVV) is invalid.
    96 The 'brand' parameter is invalid. The card scheme is invalid.
    101 The 'paymentOptionCode' parameter is invalid. The option code is invalid.
    102 The 'paymentOptionCode (invalid date)' parameter is invalid. The date of validity of the payment option code is invalid.
    103 The 'amount/optionCode (inconsistency)' parameter is invalid. The payment option code is incoherent regarding the amount.
    104 The 'optionCode (not found) ' parameter is invalid. Unknown payment option code.
E.g.: The e-mail address is missing for an operation.
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">   
	<env:Header xmlns:env="http://www.w3.org/2003/05/soap-envelope">
		<shopId xmlns="http://v5.ws.vads.lyra.com/Header/">12345678</shopId>
		<requestId xmlns="http://v5.ws.vads.lyra.com/Header/">222e970d-9c8b-466f-b672-7d830af18a8c</requestId>
		<timestamp xmlns="http://v5.ws.vads.lyra.com/Header/">2015-04-01T09:41:11Z</timestamp>
		<mode xmlns="http://v5.ws.vads.lyra.com/Header/">TEST</mode>
		<authToken xmlns="http://v5.ws.vads.lyra.com/Header/">HW4+kJDlErT3g2z5KnUEjFxBPsg9NTjR6QOsXjfsKvk=</authToken>
	</env:Header>
	<soap:Body>
		<ns2:createTokenResponse xmlns:ns2="http://v5.ws.vads.lyra.com/">
			<createTokenResult>
				<requestId>222e970d-9c8b-466f-b672-7d830af18a8c</requestId>
				<commonResponse>
					<responseCode>2</responseCode>
					<responseCodeDetail>Error param 36: email</responseCodeDetail>
				</commonResponse>
				<authorizationResponse/>
			</createTokenResult>
		</ns2:createTokenResponse>
	</soap:Body>
</soap:Envelope>

  • 3 - Request not processed

    Indicates the request could not be processed.

    Additional information is returned in the response.

    Example:

    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    	<env:Header xmlns:env="http://www.w3.org/2003/05/soap-envelope"/>
    	<soap:Body>
    		<ns2:updatePaymentDetailsResponse xmlns:ns2="http://v5.ws.vads.lyra.com/">
    			<updatePaymentDetailsResult>
    				<requestId>024a5593-8537-46cf-afc3-fabb7c76bc97</requestId>
    				<commonResponse>
    					<responseCode>3</responseCode>
    						<responseCodeDetail>Bad request[Details]</responseCodeDetail>
    				</commonResponse>
    				<paymentResponse/>
    				<orderResponse/>
    				<cardResponse/>
    				<authorizationResponse/>
    				<captureResponse/>
    				<customerResponse/>
    				<markResponse/>
    				<threeDSResponse/>
    				<extraResponse/>
    				<fraudManagementResponse/>
    				<shoppingCartResponse/>
    			</updatePaymentDetailsResult>
    		</ns2:updatePaymentDetailsResponse>
    	</soap:Body>
    </soap:Envelope>

  • 25 - Unknown contract number

    Indicates an error in the merchant acceptance agreement.

    Several cases are possible:

    • The value transmitted in the query does not match with any merchant acceptance agreement registered for the shop (shopId),
    • There is no merchant acceptance agreement associated with the shop,
    • This merchant acceptance agreement has been terminated,
    • No merchant acceptance agreements match with the type of agreement required for the payment. This is the case if you do not have an agreement for accepting manual payments and if paymentSource if set to MOTO, CC or OTHER in your query.

  • 35 - Token not created

    Indicates that the token has not been created.

    The motive for refusal is given in the result attribute of the authorizationResponse object.

    See chapter Managing authorization request return codes for more information.

    Example:
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    	<env:Header xmlns:env="http://www.w3.org/2003/05/soap-envelope">
    		<shopId xmlns="http://v5.ws.vads.lyra.com/Header/">12345678</shopId>
    		<requestId xmlns="http://v5.ws.vads.lyra.com/Header/">8fbf0b7a-c5bd-419d-b14d-23bf557c6139</requestId>
    		<timestamp xmlns="http://v5.ws.vads.lyra.com/Header/">2015-04-01T09:47:58Z</timestamp>
    		<mode xmlns="http://v5.ws.vads.lyra.com/Header/">TEST</mode>
    		<authToken xmlns="http://v5.ws.vads.lyra.com/Header/">DjY7Jr+a+7jzqD4FtYj7MflmVc8o/8QDPZkJdFSNk/k=</authToken>
    	</env:Header>
    	<soap:Body>
    		<ns2:createTokenResponse xmlns:ns2="http://v5.ws.vads.lyra.com/">
    			<createTokenResult>
    				<requestId>8fbf0b7a-c5bd-419d-b14d-23bf557c6139</requestId>
    				<commonResponse>
    					<responseCode>35</responseCode>
    					<responseCodeDetail>PaymentToken creation declined</responseCodeDetail>
    				</commonResponse>
    				<authorizationResponse>
    					<result>51</result>
    				</authorizationResponse>
    			</createTokenResult>
    		</ns2:createTokenResponse>
    	</soap:Body>
    </soap:Envelope>

  • 36 - 'paymentToken' attribute purged

    After 15 consecutive months of non-use of a token, payment method holder data are purged (PCI DSS security benchmark - security and protection of banking data).

  • 40 - Amount not authorized

    Indicates that the amount of the request for creating or refunding a payment does not respect the minimum / maximum amounts defined in the merchant acceptance agreement.

    Please contact the customer service to know the details of your acceptance agreement.

  • 99 - Technical error

    This error code is returned in case of an internal technical error.

    For more information, address the technical contact.

Example: The e-mail address is missing for an operation.
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
	<env:Header xmlns:env="http://www.w3.org/2003/05/soap-envelope">
		<shopId xmlns="http://v5.ws.vads.lyra.com/Header/">12345678</shopId>
		<requestId xmlns="http://v5.ws.vads.lyra.com/Header/">ca3d38d5-0344-461c-9f52-192482e09bda</requestId>
		<timestamp xmlns="http://v5.ws.vads.lyra.com/Header/">2015-04-01T09:47:58Z</timestamp>
		<mode xmlns="http://v5.ws.vads.lyra.com/Header/">TEST</mode>
		<authToken xmlns="http://v5.ws.vads.lyra.com/Header/">d3W/6dtIebGUpReqzrS40KHEImEway6ixrpn05pSGLY=</authToken>
	</env:Header>
	<soap:Body>
		<ns2:createTokenResponse xmlns:ns2="http://v5.ws.vads.lyra.com/">
			<createTokenResult>
				<requestId>ca3d38d5-0344-461c-9f52-192482e09bda</requestId>
				<commonResponse>
					<responseCode>99</responseCode>
				</commonResponse>
				<authorizationResponse>
					<result>96</result>
				</authorizationResponse>
			</createTokenResult>
		</ns2:createTokenResponse>
	</soap:Body>
</soap:Envelope>