Difference between revisions of "Custom Modules"
(New page: == Custom Payment Processors == If you would like to integrate a payment processor that is currently unsupported (not integrated) in AWBS, there is a devkit available upon request. ===...) |
(No difference)
|
Revision as of 11:17, May 8, 2008
Contents
Custom Payment Processors
If you would like to integrate a payment processor that is currently unsupported (not integrated) in AWBS, there is a devkit available upon request.
Custom Offsite processors:
For custom offsite processors (processors that take the customer to their website to gather the credit card information), you will use the includes/cp3.php already in AWBS along with the samplecallback.zip from the devkit.
The cp3.php file is where you will edit the information that gets passed to the processor.
The samplecallback page can be renamed as desired and should be placed in your AWBS web directory. Setup the return url to point at this page at your processor or in the cp3.php file if the processor supports passing in the return page.
More information is given in the devkit....
Make sure you have selected 'custom offsite' module in the system setup, module setup of AWBS.
Custom Onsite processors:
For custom onsite processors (processors where the credit card information is gathered on your website), you will need to use the includes/cp2.php file already in AWBS along with the ccfunctions.php file in the devkit. The ccfunctions.php file goes in the includes/customonsite directory.
More information is in the devkit....
Make sure you have selected 'custom onsite' module in the system setup, module setup of AWBS.
