Hi all,

I've been sitting here for over 1 month now with a fully working integration with ECHO, but it is only one-way i.e Signup form to ECHO processor.

I want to make this two-way so that account-creation/payment notification is supported. To do this, I need to know if ECHO supports some form of callback or passback url? An example of this is PayPals IPN or 2Checkouts Callback URL.

I've been in contact with ECHO several times over the past month about this and not a single person on their support team can answer this simple question!!! Everytime I email them, the person just forwards the email to another support technician, asking them if they can answer it :rolleyes: The result? An answer that has nothing to do with the original question!!!

All I need to know is do ECHO support this callback? If so, how do I set the destination URL? And also, what variables are passed back to the script on my server?

Hopefully the educated WHT users can answer this simple question so that I won't have to wait another bloody month for an answer :angry:

Regards,

Locutus

P.S I apologise for the tone of this message, but a lot of ppl have requested ECHO integration which was started on over 1 month ago and I've still not completed it yet due to ECHO's incompetence.

Generally I use a straight form post method to send data to mechants (such as echo). By using this form post method over NET::SSL on a secure page you're about as safe as you can get without being on the merchant's site.

The benefit of this type of submusion is that you get instant resutls and dont ever leave your site. This way you can do whatever form of validation, database addition, etc.... you need. If you go to the echo forums you'll see a few posts on this subject.

Mike, I emailed robb (lead developer for Echo) about this post and this is what he sent to chicken and myself:

His problem is that he is using a little known feature that is not described in our documentation.

If you can put this in the thread, I would appreciate it:

Michael,

No, I didn't understand your question. I think part of your
frustration is that we are just starting to implement URL redirection and we don't have it publicly documented. Here is the information you need. If you run into any problems, please let us know. We will address them promptly.

Jim

This is ECHO's "URL Forwarding URL":

https://wwws.echo-inc.com/ECHOnline.asp

There are 7 variables that can be passed to this URL gateway (along with
all the other ECHO required variables):

success_url failure_url user1 user2 user3 user4 user5

success_url and failure_url can be the same

If the transaction was a success then the url is redirected to
success_url and all of the user defined variable are passed along. If
the transaction was a failure then everything is redirected to the
failure_url.


Hello

This is Robb in Developer Support

Another thing is that you also provide all of the variables that we always use for transactions in our standard interface.


These variables are described in our host specs:

https://wwws.echo-inc.com

Select the option for DEVELOPER TOOLS.

In SECTION I you will find samples of the POST and GET method that you can
use. Just include the extra variables for the URL forwarding script.


Please let me know what other issues you have and I will help you resolve
them.

Thanks,


Robb Hanisee
ECHO Developer Support
800 233 0406 Ext 3109
rhanisee@echo-inc.com

was anything on the site

http://openecho.com/index.php

of any help ?

They still don't seem to understand :(

No, I didn't understand your question.

How else can I put it? Have they never heard of PayPal IPN or 2Checkout/Revecom Callback?

I'm not asking for a URL redirection, I'm simply enquiring whether a passback confirmation is sent to my server once a user has paid via ECHO.

If it is, how do I set the url this confirmation is sent to, and what variables are sent along with it.

I need this passback before I can integrate auto-account setup.

Edit: Just noticed this just now. How does one set the success_url and failure_url?

Any other questions will have to be emailed to open-echo and resolved privately.

Because I happen to see this thread I figured I would post what could be done at this time.


I need this passback before I can integrate auto-account setup.


Use what they said as the success_url to set the clients account
up after signup. If their payment was successful then they will
be sent to the success_url if it was not then it will be sent to the
failure_url.

To set those up you would use a hidden for field for each:

<input type="hidden" name="success_url" value="http://yourdomain.com/successful.html">

Same applies for the failure.

Also the reason no one gets exactly what your talking about it
because your wording it a bit wrong if I am not mistaken.

What you want is the following:

User signs up, you send this information to ECHO
ECHO in turn not only redirects the user to the success_url but
sends you a STATUS CODE as well or a URL that is PGP SIGNED.

The above helps you establish that the user actually did signup
and they are not just calling the finish signup url witout going through the process.

When referring to PayPal it would be best to explain what they do not everyone uses them.

PayPal sends back a confirmation code to the success_url which
can be sent back to PayPal using either PHP, Perl, ASP ect.. to verify
the order is an actual order. Whether the order is good or bad PayPal
sends back a responce to let you know so you can do what you need to do with that order.

Hope this helps to clear things up a bit.

Regards,
Ray

I just wanted to preface by saying that we are an ECHO merchant, and we've been with them for about 4 months now. I can say nothing but good things about them.

We needed an interface to our billing software (custom built) that was going to be easy to use, yet flexible. ECHO's way of passing variables over https (using a standard GET or POST) makes transacting a breeze.

I recommend anyone planning on using ECHO get intimately familiar with their gateway documentation and protocol specification, located at https://wwws.echo-inc.com/ISPGuide-Menu.asp -- it's VERY thorough (and the nicest I've seen to date -- it's simple enough to use from just about any language, yet flexible enough to handle response codes from address verification, credit card security codes, authorizations, merchant advice codes, etc.).

The real sellings points for us were the PHP and Perl source examples (which we have since customized), the use of simple https requests, and the fact that the response can be returned as XML! If you're going to be doing any kind of serious software development with a merchant account, these types of features are required.

Don't plan on using any type of cheesy 'pass-through' page. ECHO (in my humble opinion) is not really meant for this. If you need a top notch gateway at an INCREDIBLY reasonable price, I highly recommend them.

My $.02 (and then some)
Dan