Home  ›  Aes Is Currently Down for Maintenance. Please Try Again Later.

Aes Is Currently Down for Maintenance. Please Try Again Later.

Written By quarta-feira, 16 de março de 2022 Add Comment Edit
  1. Abode
  2. Help
  3. Troubleshooting

ane. Introduction

As soon equally you starting time working with our platform, sooner or subsequently information technology happens: You go stuck. You receive cryptic error messages and our platform rejects your transaction requests.

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

Have a wait at our b est p ractices , our troubleshooting tools and explanations  of the virtually mutual error messages. They will assistance you greatly to prevent and solve transaction trouble!

2. Follow Best Practices

The best way to tackle downward errors is – of form – to avoid them in the first place. Although this is not  possible in all cases, we have created a list of best practices. Post-obit them will assistance go live faster by d odg ing  the near common obstacles :

  • Always u se our Examination surroundings  starting time before going live or calculation a new feature to your live shop. Both our Test environment / nav.aside.title.go-started.live-surround treat transaction request in the same way. Equally the expected behaviour and fault messages are the same, information technology is an platonic way to examination for any imponderables or stage scenarios
  • Read the dedicated guide for the corresponding product carefully. Make sure to know the correct endpoint URL and all accepted parameters. Showtime sending requests with the absolute minimum of mandatory parameters to lear n the basics of the respective product . This is especially helpful when dealing with alternative payment methods that crave a lot of parameters.
  • Cheque that the payment method you want to utilise is activated  in your Back Office  ( Configuration > Payment Methods )  and targeted in your request with parameters PM/Make
  • Ostend that the pick  you want to use is activated in your Dorsum Office  ( Configuration >  Account > Your options )
  • Be enlightened that we offer different ways to integrate with our platform . All of them require an private approach
  • Use the shopping cart p lugins we natively back up . As they come up from certified providers, they have been thoroughly tested to create requests correctly
  • Understand the meaning of transaction status codes  and the transaction mistake codes . They help you detect the cause of failed requests .
  • Distinguish failed requests  from unsuccessful payments
    • A failed request is the result  of an unsuccessful pre-payment check by  our platform . In most cases, impacted transaction south do not  have a ny  condition 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 arrangement adds them to our Back Office  mistake logs  with more detailed information. Have a look at the most typical ones  and how to treat them.

The image show s a typical generic error bulletin on our secure payment page.

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

The images show due south  the acquirer ticket and the 8-digit error bulletin in the transaction overview

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

  • Permit complimentary traffic between your server and our platform by following our Firewall documentation.

Apart from our all-time practices, nosotros offer  you  various diagnostic tools . In many cases, they will help you lot get to the root cause and better the error completely on your own!

  • Every mistake analysis requires you to understand during which step exactly the fault occurs. Have a look at this decision tree to learn where you need to prepare your transaction  menstruum :

shows the different scenarios of erroneous  transaction s and how to deal with them

If our platform rejects a transaction , we create a log entry in the Dorsum Role  of the PSPID the transaction was sent to. Go to Configuration > Error logs to cheque them. The table provides  valuable information to understand what went incorrect and  what you can do to prepare the error

Cavalcade Description

Date time

Timestamp of the request

Mode

Integration mode  trigram . Possible values :

STD : Hosted Payment Page

DPR : DirectLink

AFU: Batch (advanced)

THP: FlexCheckout

Requestor'due south IP accost

The IP the request was sent from

PAYID

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

Description

Detailed clarification of the fault. Bank check our listing for the most common mistake messages

The prototype shows the table displaying the logs of a failed transaction try

  • Nosotros offering pages  in our Back Office  you can use to simulate dissimilar integration modes . Get to Support > Integration and user manuals > Examination pages . Choose one of the available modes by clicking on ". asp " in the respective line. In the subsequent screen, make full in the get-go set of parameters  (which are the mandatory parameters for each integration). C lick  then  on " Submit "  to send the request .
  • We constantly monitor our platform to react rapidly for any unforeseen events that may touch your online business concern – something you tin can practise, too! Enrol with our s tatus page  to be always up to date for outages and planned maintenance. This will assist y'all distinguish problems  on our platform from errors on your end.

The image show s the Ingenico status folio displaying a notification well-nigh  a service break for one our acquirers.

iv. Empathise error messages

An  important part of alteration errors is to know exactly what they hateful. Nosotros have collected the most common ones  with some detailed explanation.  All these error message s  appear either in the

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

Discover more than 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 fault codes

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

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

FAQs

Why can't I refund my payment?

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

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

What does the bulletin "An error has occurred; please effort over again later. If you are the owner..." mean?

The bulletin "An mistake has occurred; please endeavor again afterwards. If you are the owner or the integrator of this website, please log into the Worldline back function to run into the details of the error." is a generic error message which is returned if a specific technical outcome occurs at the moment the payment page is called. We don't display the actual error on the payment folio, mainly considering of security reasons, but likewise not to confuse your customers.

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

What should I practice if affiliation number is not working anymore?

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

paoluccicopievere.blogspot.com

Source: https://epayments-support.ingenico.com/help/troubleshooting

0 Response to "Aes Is Currently Down for Maintenance. Please Try Again Later."

Postar um comentário

Assinar: Postar comentários (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel