- #REASONS FOR SOCKER ERROR 1 HOW TO#
- #REASONS FOR SOCKER ERROR 1 FREE#
Is only created if the mandatory parameters are sent correctlyĭetailed description of the error. Unique reference of the transaction in our system. The table provides valuable information to understand what went wrong and what you can do to fix the error Column Go to Configuration > Error logs to check them.
If our platform rejects a transaction, we create a log entry in the Back Office of the PSPID the transaction was sent to.
#REASONS FOR SOCKER ERROR 1 HOW TO#
The flow chart shows the different scenarios of erroneous transaction s and how to deal with them Have a look at this decision tree to learn where you need to fix your transaction flow :
Every error analysis requires you to understand during which step exactly the error occurs. In many cases, they will help you get to the root cause and amend the error completely on your own! #REASONS FOR SOCKER ERROR 1 FREE#
Allow free traffic between your server and our platform by following our Firewall documentation.Īpart from our best practices, we offer you various diagnostic tools. Make sure to contact us if your transaction decline rate is above average. However, failures like these can still be caused by an error on our platform in specific situations. The images show s the acquirer ticket and the 8-digit error message in the transaction overview T he acquirer ticket and the 8-digit error message in the transaction overview contains more information. 
To learn about the rejection reason, look up the transaction in the Back Office ( Operations > View transactions ). T his is the result of a technically valid request, albeit rejected by a third party (by the acquirer or issuer). The image show s a typical generic error message on our secure payment page.Īn unsuccessful payment is a transaction with either status 0/1/2. Have a look at the most typical ones and how to treat them. Our system adds them to our Back Office error logs with more detailed information. These are invalid requests containing technical errors that prevent our platform to process the transaction altogether. They often appear in our secure payment page with a generic error message. In most cases, impacted transaction s do not have a ny status at all.
A failed request is the result of an unsuccessful pre-payment check by our platform. Distinguish failed requests from unsuccessful payments. They help you find the cause of failed requests. Understand the meaning of transaction status codes and the transaction error codes. As they come from certified providers, they have been thoroughly tested to create requests correctly Use the shopping cart p lugins we natively support. All of them require an individual approach Be aware that we offer different ways to integrate with our platform. Confirm that the option you want to use is activated in your Back Office ( Configuration > Account > Your options ). 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. This is especially helpful when dealing with alternative payment methods that require a lot of parameters. Start sending requests with the absolute minimum of mandatory parameters to lear n the basics of the respective product. Make sure to know the correct endpoint URL and all accepted parameters. Read the dedicated guide for the respective product carefully. As the expected behaviour and error messages are the same, it is an ideal way to test for any imponderables or stage scenarios Both our Test environment / -started.live-environment treat transaction request in the same way. Always u se our Test environment first before going live or adding a new feature to your live shop. Following them will help go live faster by d odg ing the most common obstacles : Although this is not possible in all cases, we have created a list of best practices. The best way to tackle down errors is – of course – to avoid them in the first place. They will help you greatly to prevent and solve transaction trouble! 2. Have a look at our b est p ractices, our troubleshooting tools and explanations of the most common error messages. We have designed our platform to give you the greatest autonomy in your daily online transaction business, even when confronted with errors. You receive cryptic error messages and our platform rejects your transaction requests.īut fear not: We have the tools that will help you. 
As soon as you start working with our platform, sooner or later it happens: You get stuck.
0 kommentar(er)
