Being uploaded!
+Because you think the idea of an open source PHP project supporting many payment gateways with one API is sexy as hell. Because you're not a douche. Because you like writing code and want to sharpen your teeth with payment APIs. These, and many others, are all excellent reasons to contribute to PHP-Payments.
+PHP-Payments relies heavily on __call magic methods and matching methods and keys via arrays. Taking this approach allowed us to eliminate duplicate code and keep an extremely clear detail of what methods and parameters were supported by each method within each gateway, within the driver itself. When you instantiate PHP-Payments, the library first autoloads some helper classes such as a utility class, a response class, a request class, the payment driver abstract class. When you call a method, PHP-Payments make sure the driver and method you're using exists, and via the method_map() function which is implemented in each driver, ensures you've submitted the required keys for that method. If all checks out, the request can be made.
+Calvin started writing code for a freelance project in February of 2012 that needed an integration with PayPal Payments Pro. Finding that the PayPal SDK was not that great, and thinking "payment gateway implementations should be an abstraction - not an involved integration project", Calvin started writing code for a CodeIgniter package. When the package was released, it only supported PayPal Payments Pro and was very simple.
+Follow Calvin on Twitter: @calvinfroedge
+Phil provided early support, encouraging Calvin (who was new to PHP) to continue developing the code and to package the code as a CodeIgniter spark. When Phil made the call for speakers for the first CodeIgniter on tour conference, Calvin asked to speak and promised to radically improve his payments class (which by then supported 3 gateways). Amazingly, and probably against his better judgement, Phil obliged. PHP-Payments would not exist had Phil not taken a chance on an unproven developer.
+Follow Phil on Twitter: @philsturgeon
+Joel was the first person to fork the spark CodeIgniter payments and contribute a gateway to the codebase. He is responsible for the BluePay payments support. He has also contributed extremely valuable ideas on how to improve the code and has made great feature suggestions.
+Follow Joel on Twitter: @eclarian
+James made the first donation to CodeIgniter payments. He needed a payment integration for his own project and CodeIgniter payments met his need. His gift was a huge confidence booster and was most appreciated.
+Follow James on Twitter: @outofcontrol
+
+<?php
+include('/path/to/payments/payments.php');
+
+$p = new PHP_Payments;
+
+$config = Payment_Utility::load('config', '/path/to/your/gateway/config');
+$params = array('cc_number' => 4111111111111111, 'amt' => 35.00, 'cc_exp' => '022016', 'cc_code' => '203');
+
+$response = $p->oneoff_payment('name_of_payment_driver', $params, $config);
+
+
+ Though the project began as a CodeIgniter spark, PHP-Payments is now a framework agnostic API. Writing an interface to bring it to your framework is easy, and your framework could already be supported. Check out the frameworks page for more info.
+Please note that not all drivers implement each of these methods. In addition, the params available in each method may not be used in a particular driver's implementation. If you use a param in a request which is not used, it will appear in your error log, but will not create any ill effects in the request - it simply will not be sent to the gateway.
+ +$v) +{ + if($v[0] != '.') + { + include $mdir.$v; + $class = str_replace('.php', '', $v); + $ex = explode('_', $class); + foreach($ex as $k=>$v) + { + $ex[$k] = ucfirst($v); + } + $class_name = implode("_", $ex); + $class_instance = new $class(); + + ?> + +| # | +Parameter | +Example | +
|---|---|---|
| + | + | + |
+include('/path/to/lib/payments.php');
+
+$payments = new PHP_Payments;
+
+$config = Payment_Utility::load('config', '/path/to/config/file'); //You can do this or you can make this an array. Config file is recommended since configuration needs differ by gateway.
+
+//Make the call
+$response = $payments->payment_action('gateway_name', $params, $config);
+
+
+There are two types of responses returned, local responses and gateway responses. If a method is not supported, required params are missing, a gateway does not exist, etc., a local response will be returned. This prevents the transaction from being sent to the gateway and the gateway telling you 3 seconds later there is something wrong with your request.
+ +Accessing response properties looks like this:
+ ++$status = $response->status; ++ +
Gateway responses will usually have a full response from the gateway, and on failure a 'reason' property in the details object:
+ ++$gatway_response = $response->details; + +$failure_reason = $response->reason; ++ +