ezosC v2.1 is a turnkey e-commerce online store business solution based in osCommerce 2.2 RC 2a with a full supported IT and tech support staff.  ezosC v2.1  can be customized for any business’ needs with its open source. We have added additional functionality to this store by adding modules for every business to profit from. You need to have the edge over your competition with modules that will set you apart from the rest.

After years of experience developing and repairing shopping carts, we have developed the functionality of the carts that we have made for the various clients, in one great e-commerce solution. From turnkey apparel e-commerce stores and automotive online stores, to reservation systems e-commerce and book online stores, we have developed the ultimate online shopping experience for your customers. Read more

Click here for more information

 
Call Now 1.800.961.7427

 

Complete eCommerce Solution
Based in osCommerce

Help - Search - Members - Calendar
Full Version: Integration - MD5 signature problem - WorldPay Select Junior v1.0
osCommerce Community Support Forums > osCommerce Online Merchant v2.x > Contributions / Add-Ons > Payment Modules > WorldPay
cujimmy
Jings! this is a quiet corner of the osC forum.

I'm getting "the MD5 signature could not be verified" on running a test transaction - been over everything a dozen times and suspect the problem lies with WorldPay (can't even submit a support request at the moment - getting an internal server error on submitting) but I still have a horrible feeling I've missed something obvious.

(In the admin, we do have the same password under "MD5 Password" as under "MD5 secret for transactions" on Worldpay's Test Integration Setup page).

In worldpay_junior.php, everything is unchanged (I've only removed some fields for this post) :

CODE
$process_button_string = tep_draw_hidden_field('instId', MODULE_PAYMENT_WORLDPAY_JUNIOR_INSTALLATION_ID) .
tep_draw_hidden_field('amount', $this->format_raw($order->info['total'])) .
tep_draw_hidden_field('currency', $currency) .
tep_draw_hidden_field('hideCurrency', 'true') .
tep_draw_hidden_field('cartId', $order_id) .
tep_draw_hidden_field('signatureFields', 'amount:currency:cartId') .
tep_draw_hidden_field('signature', md5(MODULE_PAYMENT_WORLDPAY_JUNIOR_MD5_PASSWORD . ':' . $this->format_raw($order->info['total']) . ':' . $currency . ':' . $order_id)) .
tep_draw_hidden_field('MC_callback', substr(tep_href_link('ext/modules/payment/worldpay/junior_callback.php', '', 'NONSSL', false, false), strpos(tep_href_link('ext/modules/payment/worldpay/junior_callback.php', '', 'NONSSL', false, false), '://')+3));


At this point, I think the sensible thing is to take the dog for a walk.
lomaxa
QUOTE (cujimmy @ Apr 18 2008, 02:03 PM) *
Jings! this is a quiet corner of the osC forum.

I'm getting "the MD5 signature could not be verified" on running a test transaction - been over everything a dozen times and suspect the problem lies with WorldPay (can't even submit a support request at the moment - getting an internal server error on submitting) but I still have a horrible feeling I've missed something obvious.

(In the admin, we do have the same password under "MD5 Password" as under "MD5 secret for transactions" on Worldpay's Test Integration Setup page).

In worldpay_junior.php, everything is unchanged (I've only removed some fields for this post) :

CODE
$process_button_string = tep_draw_hidden_field('instId', MODULE_PAYMENT_WORLDPAY_JUNIOR_INSTALLATION_ID) .
tep_draw_hidden_field('amount', $this->format_raw($order->info['total'])) .
tep_draw_hidden_field('currency', $currency) .
tep_draw_hidden_field('hideCurrency', 'true') .
tep_draw_hidden_field('cartId', $order_id) .
tep_draw_hidden_field('signatureFields', 'amount:currency:cartId') .
tep_draw_hidden_field('signature', md5(MODULE_PAYMENT_WORLDPAY_JUNIOR_MD5_PASSWORD . ':' . $this->format_raw($order->info['total']) . ':' . $currency . ':' . $order_id)) .
tep_draw_hidden_field('MC_callback', substr(tep_href_link('ext/modules/payment/worldpay/junior_callback.php', '', 'NONSSL', false, false), strpos(tep_href_link('ext/modules/payment/worldpay/junior_callback.php', '', 'NONSSL', false, false), '://')+3));


At this point, I think the sensible thing is to take the dog for a walk.


I've just integrated with WP Junior, and I didn't touch the worldpay_junior.php file.

In Worldpay admin, login to the production area and click on SYSTEM Settings, select the Integration Setup 'Test' and add the Payment Response URL eg http://www.your-url.co.uk/catalog/ext/modu...or_callback.php (don't forget the include the http://), check the Payment Response enabled? and check the Enable the Shopper Response. Enter a Payment Response password (This is the Callback Password you entered in the OSC Admin WP Junior setup) and enter the MD5 secret for transactions (This is the MD5 Password you entered in the OSC Admin WP Junior setup).

I also copied it to the Production setup.

PS You can only enter these changes when you login to the PRODUCTION live environment if you try it in the TEST environment you will get a database error. A good contact at WP is Gary Cook 08703661290.

Enjoy...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.
Powered by osCommerce.com | Oscommerce Forum