Online Payments guide for Web Developers (#OLSSTRPAYWEBDEV01)
| Last updated: | Applies to: | In industries: | Of versions: | Article notes: | Special contents: | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| 20120508 (Andy) | Pro, MultiUser, MultiSite, MultiView | 
   |
8.X (and higher) |
|
Download the templates |
Before we begin...
This guide is intended for web developers that are involved in implementing StorMan's Online Payments system. Unlike many other myStorMan knowledgebase articles, this page is not password protected - so we welcome you to link your developer directly to this page.
Note: If you are not a web developer, or are looking for more general Online Payments information, please refer to #OLSSTRPAY01.
How does the Online Payments system work?
This is explained in our general article, via #OLSSTRPAY01.
General notes for web developers
- The payment pages are hosted on our server (www.storpay.com).
- As we host the payment pages, your client's website will NOT need an SSL certificate.
- You will need to place a or (or similar) link or button on your client's website. The button or link can be placed anywhere on the website; we merely use the standard "A HREF" hyperlink call to link to the web pages served on www.storpay.com. Please ask your client to ask StorMan Software for this link.
- We do NOT recommend the use of frames or iframes, as the SSL certificate used on www.storpay.com will throw up an error which may scare off some of your client's Customers.
- You may use a pop-up window if you prefer; but keep in mind that some visitors may use pop-up blockers with their web browsers.
Template customisation rules & guidelines
Out of the box, our Online Payments system uses standard (default) templates. If your client is happy with the default templates, all we need is a transparent .PNG file of their company logo at 300px (W) by 100px (H). If your client wants you to customise these templates (you can download them below) so that they look like the rest of their website, please view our rules & guidelines below...
- Do NOT change any of the form field names.
- Do NOT change the form name or form submission details.
- Do NOT change any dynamic variable names.
- Do NOT remove any fields from any of the forms.
- Do NOT add any new fields to any forms.
- StorMan is NOT able to provide dynamic content processing through the use of PHP, ASP or any other technologies - pages supplied need to be static only.
- The customised Online Payments pages will need to be designed in such a way so that all images and stylesheets are stored & referenced locally with the pages... for example: <img src="./images/logo.png" /> and NOT this: <img src="http://www.ourwebsite.com/images/logo.png" /> or this: <img src="/images/logo.png" /> If you reference images or stylesheets that are NOT hosted on www.storpay.com, the SSL certificate used on www.storpay.com will throw up an error which may scare off some users. Alternatively, you can use the following as a prefix to any URL's (such as images, stylesheets, HTML pages): <!--4DHTMLVAR vtABSURL-->For example: <link href="<!--4DHTMLVAR vtABSURL-->media/css/storage.css" rel="stylesheet" type="text/css" />
Template files
Use the link below to download the latest version of our Online Payments templates.
The files are described in detail underneath...
| Filename | Purpose |
|---|---|
| authnetprocess.shtml | This page is called by Authorize.net after a payment has been processed. You will not need to customise this file unless the client uses Authorize.net as your payment processor (generally, only clients in the USA will use this payment processor). You can customise the look and feel of this page, but you must keep the following line of 4D code intact:<!--4DHTMLVar vtAuthNetProcessForm--> |
| confirmpay.shtml | This page displays the amount to pay (read-only) & credit card information. It acts as a final data entry / confirmation step before submission to the payment processor. You can customise the look & feel of this page - but understand that this page contains a large number of 4D code snippets; all of which must remain in tact and in use. However, you may be able to re-order some elements. |
| error.shtml | This page is called when the system experiences an error (the error wording is generated by our system). You can customise the look and feel of this page, but you must keep the following line of 4D code intact: <!--4DHTMLVAR vtErrorMessage--> |
| login.shtml | This page is used to accept the end-user’s StorMan Agreement Number and payments Password - allowing them to continue and make a payment. You can customise the look & feel of this page - but understand that this page contains a number of 4D code snippets; all of which must remain in tact and in use. |
| pay.shtml | This page displays the summary details of the payment - including whether the payment was successful or not. You can customise the look & feel of this page - but understand that this page contains a number of 4D code snippets; all of which must remain in tact and in use. |
| query.shtml | This page displays the end-users Agreement information including Amount Due and Due Date. The end-user enters the amount to pay as well as credit card information. |
| querynopass.shtml | This page is similar to the one above, but is displayed only when the end-user doesn't enter their password at the initial login screen. It hides the end-users Agreement information (including Amount Due and Due Date) for privacy reasons. The end-user just needs to enter the amount to pay as well as credit card information. |
| maintenance.shtml | This page displays a 'Service Unavailable’ message in place of the code block (below). The wording of the message is configured by StorMan staff. You can customise the look and feel of this page, but you must keep the following line of 4D code intact: <!--4DHTMLVAR vtErrorMessage--> |
Ready to test it?
Once the templates are installed and an online payments URL has been provided to you by StorMan, you should run the following tests...
- Start by trying to access the StorMan Webserver on the client's local LAN, by browsing to http://internal.IP.address.of.storman.server:19812 - if the connection is successful, you should be prompted with a "Login for StorMan.4DC" dialog (which you can close; if the prompt itself appears, then all is OK). If you DON'T see this prompt, check to ensure that the StorMan Webserver is actually running (in StorMan, select , then ).
- If the above works, move on to the WAN by browsing to http://client.external.ip.address:19812 - if the connection is successful, you should be prompted with the same "Login for StorMan.4DC" dialog from above (which you can close; if the prompt itself appears, then all is OK). If you DON'T see this prompt, then the port has not been forwarded properly through your router or firewall and you will need to correct this.
- If the above works, visit the URL provided by StorMan and attempt to login to the Online Payments system with a StorMan Agreement number & password to ensure the pages load correctly. We would also recommend testing the payment function in its entirety by taking a $1 payment with the facility owner (on their credit card) to ensure the process completes successfully.
Further assistance
If you require further information, please contact your client, or contact StorMan Software directly.
| Related articles: | Article tags: | How did we do? | ||
|---|---|---|---|---|
|
Did we miss a tag? |