Thread

How long it will take programming in PHP for Credit Card Processing? I’ve to implement coding for Credit Card, Direct Debit and Direct Deposit processing. I’ve Implemented PayPal option With CodeIgniter. Or is there a library supported by CodeIgniter for non-paypal payment methods…Please Help…I’ve to code it any way..

Thanks In Advance… :gulp:

Jenson M John

Use firstdata.com for CC processing .
Their api class for php is pretty straight forward , easy enough to set it up in 5 min 😊

It took me about a week the first time I did it, because at the time I wasn’t familiar with sending and receiving XML via POST. Be sure to take a look at the curl and encryption CI libraries, they save a LOT of time.

Authorize.net has an example of php code, as well as other examples available at:

http://developer.authorize.net/samplecode/

Typically the merchant will provide PHP classes that connect to their APIs. You will then load these classes as CI libraries, then in your model, use the library to handle the transactions.

Anyone have links to tutorial or any kind of learning material for it?

It depends on the merchant, iFadey.

Tutorial:

http://www.merchant-account-services.org/article/authorize-net-php-integration/1

Hmm this tutorial seems very detailed. Thanks for the link skunkbad 😊

Yes Colin you are right. Every tutorial I found is specific to some merchant

On the merchant I had to process with all they provided was a short ASP code example. No classes, no scripts, just a reference of XML fields, approval code definitions, etc.

Its 100% merchant specific, because there is no real standard of how credit card processing communication occurs, so long as it is ‘secure’ (PCI Compliant). I think some processors even have cloud SOAP services and javabeans that accept credit card data, and some allow raw socket connections and stream communication for integration with lower level programming languages.

So its basically an issue of getting whatever you can from the merchant and piecing together their unique puzzle, and deciding what features you want to implement. I for instance never implemented returns processing, because I preferred to just do it directly through the merchant gateway they provided.

hmm Brian then this thing really needs standardization in APIs. What do you think?

hmm Brian then this thing really needs standardization in APIs. What do you think?

It’d be nice, but I tend to think its intentional - a form of lock-in for those that require quite a bit of integration, and for those that offer especially easy integrations (like Authorize.net and PayPal who go so far as to offer whole classes in at least a half-dozen script languages and hundreds of pages in manuals - more than anyone would likely use on any project) its a selling point, so they don’t want to standardize and let other processors take away their competitive advantage.

Many things are not standardized for purely competitive reasons, as Microsoft has shown so many many times (Java VM, javascript, CSS ‘filters’, special HTML tags, PDF/XPS, et al).

So I wouldn’t hold my breath 😊

Hmm thanks for the info 😊

Thank u Guys..😊