Tokenization > Failure outcome notification

Failure outcome notification

If contract creation or card substitution is not possible, the Gateway returns to Merchant, in synchronous (XML format) or asynchronous (NVP format) mode depending on the protocol, a standard notification with the following parameters more:

Errore code
A speaking error description

Example of failure outcome notification message

Where the payment request is in breach of the creation rules of a walletID or card substitution, the system will return the error code “182”, the failure detail is shown in errorcode and errormessage parameters.

NVP format asyncronous notification example

result=NOT APPROVED&paymentid=742792762584270189&walletid=WalletIsExample& merchantorderid=OrderId&rn=123456789123&responsecode=182&errorcode=WS00063& errormessage=Wallet Already Exists

                                        Example of synchronous notification in XML format                                    

                                    <?xml version="1.0" encoding="UTF-8"?>
<response>
 <result>NOT APPROVED</result>
 <paymentid>742792762584270189</paymentid>
 <walletid>WalletIsExample</walletid>
 <merchantorderid>OrderId</merchantorderid>
 <rrn>123456789123</rrn>
 <responsecode>182</responsecode>
 <errorcode>WS00063</errorcode>
 <errormessage>Wallet Already Exists</errormessage>
</response>
                                

The list of allowable error codes are listed in Tokenization Error codes table.