1. Introduction

As soon as you start working with our platform, sooner or later it happens: You get stuck. You receive cryptic error messages and our platform rejects your transaction requests. 

But fear not: We have the tools that will help you. We have designed our platform to give you the greatest autonomy in your daily online transaction business, even when confronted with errors.    

Have a look at our best practices, our troubleshooting tools and explanations of the most common error messages. They will help you greatly to prevent and solve transaction trouble! 

2. Follow Best Practices

The best way to tackle down errors is – of course – to avoid them in the first place. Although this is not possible in all cases, we have created a list of best practices. Following them will help go live faster by dodging the most common obstacles: 

  • Always use our Test environment first before going live or adding a new feature to your live shop. Both our Test environment nav.aside.title.get-started.live-environment treat transaction request in the same way. As the expected behaviour and error messages are the same, it is an ideal way to test for any imponderables or stage scenarios 
  • Read the dedicated guide for the respective product carefully. Make sure to know the correct endpoint URL and all accepted parameters. Start sending requests with the absolute minimum of mandatory parameters to learn the basics of the respective product. This is especially helpful when dealing with alternative payment methods that require a lot of parameters.  
  • Check that the payment method you want to use is activated in your Back Office (Configuration > Payment Methods) and targeted in your request with parameters PM/BRAND 
  • Confirm that the option you want to use is activated in your Back Office (Configuration > Account > Your options) 
  • Distinguish failed requests from unsuccessful payments 
    • failed request is the result of an unsuccessful pre-payment check by our platformIn most cases, impacted transactions do not have any status at all. They often appear in our secure payment page with a generic error message. These are invalid requests containing technical errors that prevent our platform to process the transaction altogether. Our system adds them to our Back Office error logs with more detailed information. Have a look at the most typical ones and how to treat them.

The image shows a typical generic error message on our secure payment page.

An unsuccessful payment is a transaction with either status 0/1/2. This is the result of a technically valid request, albeit rejected by a third party (by the acquirer or issuer)To learn about the rejection reason, look up the transaction in the Back Office (Operations > View transactions). The acquirer ticket and the 8-digit error message in the transaction overview contains more information

The images shows the acquirer ticket and the 8-digit error message in the transaction overview 

However, failures like these can still be caused by an error on our platform in specific situations. Make sure to contact us if your transaction decline rate is above average. 

3. Use troubleshooting tools

Apart from our best practices, we offer you various diagnostic tools. In many cases, they will help you get to the root cause and amend the error completely on your own! 

  • Every error analysis requires you to understand during which step exactly the error occurs. Have a look at this decision tree to learn where you need to fix your transaction flow:

The flow chart shows the different scenarios of erroneous transactions and how to deal with them

If our platform rejects a transaction, we create a log entry in the Back Office of the PSPID the transaction was sent to. Go to Configuration > Error logs to check them. The table provides valuable information to understand what went wrong and what you can do to fix the error

Column Description

Date time 

Timestamp of the request 

Mode 

Integration mode trigram. Possible values 

STDHosted Payment Page 

DPRDirectLink 

AFU: Batch (advanced) 

THP: FlexCheckout 

 

Requestor’s IP address 

The IP the request was sent from 

PAYID 

Unique reference of the transaction in our system. Is only created if the mandatory parameters are sent correctly 

Description 

Detailed description of the error. Check our list for the most common error messages 

  • We offer pages in our Back Office you can use to simulate different integration modes. Go to Support > Integration and user manuals > Test pagesChoose one of the available modes by clicking on “.asp” in the respective line. In the subsequent screen, fill in the first set of parameters (which are the mandatory parameters for each integration). Click then on “Submit to send the request. 
     
  • We constantly monitor our platform to react quickly for any unforeseen events that may impact your online business – something you can do, too! Enrol with our status page to be always up to date for outages and planned maintenance. This will help you distinguish problems on our platform from errors on your end. 

The image shows the Ingenico status page displaying a notification about a service interruption for one our acquirers.  

4. Understand error messages

An important part of amending errors is to know exactly what they mean. We have collected the most common ones with some detailed explanation. All these error messages appear either in the 

  • Customers’ browser during the payment process 
  • Back Office (Configuration > Error logs) 
  • XML response you receive for DirectLink / FlexCheckout requests 

Find more errors and how to deal with them in our Transaction error codes overview 

All described errors prevent our platform from processing the request altogether.

5. Transaction error codes

You can find more information on transaction errors and statuses here.

If you log on to your Worldline account, you'll find all possible errors and statuses in the User guides section of the Support menu.

FAQs

There are different reasons why you can't refund a transaction. You need to consider the following (with the condition that the Refund option is enabled in your account):

  • The transaction is in an "incomplete" status, such as a pending or erroneous status (9192 etc.) that doesn't allow the refund operation.
  • If the transaction is authorised (status 5), at which point no payment has been made yet. In this case you have to cancel the authorisation instead of refund.
  • The used payment method doesn't support the refund functionality, which can be the case with certain debit cards, web banking methods and "offline" payment methods such as Bank transfer.

The message "An error has occurred; please try again later. If you are the owner or the integrator of this website, please log into the Worldline back office to see the details of the error." is a generic error message which is returned if a specific technical issue occurs at the moment the payment page is called. We don't display the actual error on the payment page, mainly because of security reasons, but also not to confuse your customers.

In your Worldline account, via "Configuration" > "Error logs", you can easily look up the errors that occurred when the generic error message was displayed. The actual meaning of these errors are described on the Possible errors page.

Sometimes it happens that an affiliation number has been put inactive on the side of the acquirer. We suggest you contact your acquirer for this.