7 replies to this topic

[j_vovus]

Hi,


I almost finished payment module and want to clarify following question:
Payment gateway needs tree urls - callback, success and cancel.
callback - is for background callback
success - is to redirect customer after payment
cancel   - is to redirect customer on canceling of transaction


What is the best way to process this callbacks? Is there some interface to direct such requests to my module through router or I need separate public files to catch it?

Best regards,
Vladimir

[web-project]

Quote

What is the best way to process this callbacks? Is there some interface to direct such requests to my module through router or I need separate public files to catch it?

normally some payment gateways like PayPal send information back to store via IPN/API about the payment back to store.

Quote

What is the best way to process this callbacks?

verify information and enter the info as order comments (PayPal and other modules do the same way)

Quote

I need separate public files to catch it?

no you don't need as it's normally in the same public folder.

[j_vovus]

Hi web-project,
Thanks for reply!

I mean something different.
E.g.:
I have module file /Core/Site/Shop/Module/Payment/MyPaymentModule.php
It has method "processCallback()"
How to send callback to this method form remote gateway with construction nearly like this: "http://example.com/index.php?MyPaymentModule&processCallback"?

P.S.: Some details: My payment provider use redirect of customer to its gateway, like 2checkout, Sage, PayPal Standard (seems to be). Then it redirects customer back to shop's success page and make background callback to shop.

[toyicebear]

You do know that 3.02 is "incomplete" and just a developers release...

For a live shop you should be using 2.3.1

[j_vovus]

Hi toyicebear,

Thank you, but I'm not using it in production.
I'm developing a payment module for 3.0.2.
I already have module for 2.3.1 version and now need to complete the same task for 3.0.2.
I can't find a contacts osCommerce developers for non-commercial support (developers of other CMS consult module developers when documentation is incomplete).

[j_vovus]

I found how to process this data:
on success you need to redirect customer to http://yoursite.com/index.php?Checkout&Process and handle it with function process() in the module file.
For cancel you can do hack with switch:
success url: http://yoursite.com/index.php?Checkout&Process&myaction=1
cancel url: http://yoursite.com/index.php?Checkout&Process&myaction=2

function process() {
	switch($_GET['myaction']) {
		 case 1:
			 //success processing
		 break;
		 case 2:
		   //cancel processing
		  OSCOM::redirect(OSCOM::getLink(null,'Cart')); // we are redirecting customer to cart before Process action redirects customer to Success action page
		  exit();
	}
}

BUT! callback() handler - is total fail! It goes through same checks and verifications as customer on success and server of payment gateway fails to pass them.
It's deadlock.

[modminds]

Hi
COuld you let me know the steps to write a custom payment module for oscommerce 3.0.2

Thanks

[DunWeb]

@modminds

v3.x is NOT a production release.  It is for developers only. By asking for help to create a custom payment module, it is obvious you are not a developer.  I suggeset deleting v3.x and downloading v2.3.1 which is the most recent stable release.



Chris