close ad
Databridge V2 with MySQLi support IS Now Available!
open ad
View Menu

Web development tutorial

Debug eCart transaction failures

Tutorial created by Team WebAssist

Categories: eCart


When trying to figure out why your test transactions are failing, eCart has a few built-in functions to help you out. Applying the eCart Payment Gateway Response bindings to your failure pages will help you better understand why a transaction is failing.

arrow downWhat you need to start

  1. Dreamweaver CS3 or later
  2. eCart 5
  3. Site containing eCart checkout pages

arrow downCreating Response bindings

The first step is to add the Payment Response option to your list of bindings.

  1. Open the failure page you wish to apply this to.
  2. Most commonly, this would be checkout_failure or shipping_failure.
  3. From the Bindings panel, choose Add.
  4. Select eCart > Checkout > Local Checkout Response.
  5. From the Gateway menu, choose your payment gateway.

PayPal Express users will need to do this twice for the %u2018PayPal Authorize Express Checkout%u2019 and %u2018PayPal Process Express Checkout%u2019.

arrow downAdding the desired bindings

You will now have a new group listed in the Bindings panel for Local Checkout Response. The responses available vary depending on the payment gateway.

  1. Click and drag any of the options listed to a location within your page.
    Each option you add to your page will display specific information regarding the error that is being returned. Choose whichever options you feel will be most helpful with diagnosing the issue.

  2. Besides each binding on your page, you may want to add some descriptive text.
  3. Press Ctrl (Cmd) S to save your page.
  4. Upload your new pages to your live server.
  5. Make sure to upload the WA_eCart folder as well since it will contain new helper files for these bindings.
  6. Perform another test transaction on your site and review the error you receive.

Step 1: Using the Full Response option

There is an option under the Local Checkout Response for Full Response. This option includes all the details regarding your error, and may be easier to use than adding individual bindings. However, when using this option, you will need to View Source in your browser to view the error details cleanly.

  1. When you reach the failure page, you will see a block of text containing your error response.
  2. Select the View option in your browser.
  3. Choose Page Source or Source.
  4. Scroll to the location in your code that contains the error.
    The error information will be presented in an organized XML format.
  5. Review the XML code to view the Full Response details of your error.

arrow downHow do I resolve the error?

The most appropriate method for resolving your error message is to check with your payment gateway for more details on why that particular error may be occurring. Once you have an understanding of what is causing the error, you can make any change necessary to the pages of your site.

Once you have resolved the error, you should remove the bindings from the page. As they may display information that you (or your customers) do not want displayed on the page.

arrow downReviews and comments

Comments will be sent to the author of this tutorial and may not be answered immediately. For general help from WebAssist, please visit technical support.

Sign in to add comments

Build websites with a little help from your friends

Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.

Build websites from already-built web applications

These out-of-the-box solutions provide you proven, tested applications that can be up and running now.  Build a store, a gallery, or a web-based email solution.

Want your website pre-built and hosted?

Close Windowclose

Rate your experience or provide feedback on this page

Account or customer service questions?
Please user our contact form.

Need technical support?
Please visit support to ask a question





Ease of use


security code refresh image

We do not respond to comments submitted from this page directly, but we do read and analyze any feedback and will use it to help make your experience better in the future.