Payment systems
Moderator: General Moderators
Payment systems
After creating a website for a friend, that required a content management system, I found that a lot of the available and well known ones (joomla, magento, etc) required that you used a template system, limiting what you can and can't do in terms of web design. It also meant that the way you create and design sites has to be changed to tailor to the CMS, something which I don't think a web designer should have to do.
So basically, I set about creating a simple CMS system, coded in PHP which could be implemented with ease into any website design that's in standard html, and handled the content and navigation.
It worked well, and my friend then wanted some extended features like user login, private messaging and that sort of thing. I followed the same principle, whereby the design of the site is the priority and the code integrates into pretty much every conventional html web template. As well as this, I've coded the whole thing in simple PHP, so that if anybody else looks at the code they'll only need fundamental PHP knowledge to know what it does, and be able to edit and add to it.
Now, I'd like to add an e-commerce type system, allowing my CMS to take payments. This way, if I get any clients or friends in the future that want to run a shop site, my system will be able to handle it.
Basically kind of like Joomla et al, without the irritating templates and limiting features. It will be easier to design and develop for.
I'd like to ask firstly, for opinions on the concept.
And secondly, for advice on accepting payments and such, as it's not like anything I've done before. Is this possible with just PHP and Mysql, or will I need to use things like Paypals API, or learn some more things (like SOAP)?
Thanks for the help.
So basically, I set about creating a simple CMS system, coded in PHP which could be implemented with ease into any website design that's in standard html, and handled the content and navigation.
It worked well, and my friend then wanted some extended features like user login, private messaging and that sort of thing. I followed the same principle, whereby the design of the site is the priority and the code integrates into pretty much every conventional html web template. As well as this, I've coded the whole thing in simple PHP, so that if anybody else looks at the code they'll only need fundamental PHP knowledge to know what it does, and be able to edit and add to it.
Now, I'd like to add an e-commerce type system, allowing my CMS to take payments. This way, if I get any clients or friends in the future that want to run a shop site, my system will be able to handle it.
Basically kind of like Joomla et al, without the irritating templates and limiting features. It will be easier to design and develop for.
I'd like to ask firstly, for opinions on the concept.
And secondly, for advice on accepting payments and such, as it's not like anything I've done before. Is this possible with just PHP and Mysql, or will I need to use things like Paypals API, or learn some more things (like SOAP)?
Thanks for the help.
Re: Payment systems
look into online payment gateways, the most known of which are paypal (though a local solution might be more customized to your needs).
Re: Payment systems
Hi Sephern
you stated
Also you said
you stated
Does this mean that you're not writing this in OOP ?I've coded the whole thing in simple PHP
Also you said
I'm kinda with you on Magento as I can't fully get my head around their templates ( i'm sure some on here probably can though). but joomla I feel I could achieve almost any design if needed. However having some sort of template system is at the core of MVC programming and on the size of project your'e looking at making not having this in place would become a nightmare further down the line. IMHOjoomla, magento, etc) required that you used a template system, limiting what you can and can't do in terms of web design.
Re: Payment systems
It uses basic OOP principles, and keeps the design of the site, and the coding separate. You can basically place content tags for main content, and the same with navigation. You basically take out the content and nav, and replace them with include tags.
For UserCP stuff, it has the userCP design on one (mainly HTML) page, which uses and include usercpdata.php, which contains the coding for the UserCP. That means that web designers can basically redesign the whole interface easily, without having to have access to the underlying php underneath. When it comes to the PHP, it doesn't really get more complicated than, includes, SQL statements, while loops and functions.
My problem isn't that I find Magento or Joomla to difficult, its just that I don't like to be limited in design options, and I don't think that people should be.
As for payment gateways, such as paypal. Would this require knowledge of their API, and something like SOAP or an alternative technology, or is this solely achievable in PHP? If it does require something else, where would you suggest getting started with this?
Finally, could you expand what you mean when you say a more local solution, as I don't understand what you mean by that.
For UserCP stuff, it has the userCP design on one (mainly HTML) page, which uses and include usercpdata.php, which contains the coding for the UserCP. That means that web designers can basically redesign the whole interface easily, without having to have access to the underlying php underneath. When it comes to the PHP, it doesn't really get more complicated than, includes, SQL statements, while loops and functions.
My problem isn't that I find Magento or Joomla to difficult, its just that I don't like to be limited in design options, and I don't think that people should be.
As for payment gateways, such as paypal. Would this require knowledge of their API, and something like SOAP or an alternative technology, or is this solely achievable in PHP? If it does require something else, where would you suggest getting started with this?
Finally, could you expand what you mean when you say a more local solution, as I don't understand what you mean by that.
Re: Payment systems
A gateway is a remote service, so again - no, you can't do this without interfacing with their API. It doesn't have to be SOAP, but some data format will have to be used obviously (XML, JSON, query-strings, etc.). Some of those gatways provide ready libraries to interact with their APIs. For example, check out Paypal developers site - https://cms.paypal.com/us/cgi-bin/?cmd= ... rview_land
By a local solution I meant a payment gateway in your local geographical location (I have no idea where you are from). Those can sometimes offer better pricing packages and work with local banks.
By a local solution I meant a payment gateway in your local geographical location (I have no idea where you are from). Those can sometimes offer better pricing packages and work with local banks.
Re: Payment systems
A local system would not be ideal, as hopefully this is a solution I will use on several sites in the future, not all in the same area.
Would you recommend any particular way of interacting with API's, tutorials pertaining to these methods, and any other gateways than paypal that I should consider using as well?
Would you recommend any particular way of interacting with API's, tutorials pertaining to these methods, and any other gateways than paypal that I should consider using as well?
Re: Payment systems
I was talking about a local provider, not a local system.. as in, the same country 
Re: Payment systems
I live in the UK. I wouldn't like to rule out using it for sites based in Americaland, and elsewhere.pytrin wrote:I was talking about a local provider, not a local system.. as in, the same country
Re: Payment systems
There is some misunderstanding here. It doesn't matter where you are for connecting to the service.. it's done through the Internet which is not limited to a specific geographical location. Local providers however, can usually give you (pricing) solutions more adapted to your local banking and tax systems.
Re: Payment systems
Yet if the payment gateway is linked to UK currency and taxes, then if I made a site for someone based in say, America, they would then have to deal with a potentially alien currency, and the tax would not be relevant at all?pytrin wrote:There is some misunderstanding here. It doesn't matter where you are for connecting to the service.. it's done through the Internet which is not limited to a specific geographical location. Local providers however, can usually give you (pricing) solutions more adapted to your local banking and tax systems.
Would this not also mean I would not be accepting paypal, which is accepted widely by consumers and trusted?