comment on

That is not my experience: I have analysed the WorldPay callback process carefully, and have been able to satisfy myself that it can be made secure, which isn't always the case.

Maybe our needs are different, but I had no problems coding to it, and our clients have reported no problems getting support or getting their money.

They are not the cheapest payment processing service out there, but the cheaper one that I investigated at a client's request turned out to be entirely insecure (ie there was no way to write the client code so that the callback could be confident the ordered goods had been paid for); when I pointed this out to them they agreed, but affirmed that they had no plans to change it.

Hugo

In reply to Re^3: Business::WorldPay::Junior and last release date by hv
in thread Business::WorldPay::Junior and last release date by ghenry

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl-Sensitive Sunglasses
	PerlMonks