NOTICE - USING CODEIGNITER-PAYMENTS ALONE DOES NOT MAKE YOU PCI COMPLIANT
It is highly recommended that you attempt to architect your application to achieve some level of PCI compliance. Without this, the applications you create can be vulnerable to fines for PCI compliance violations. Using codeigniter-payments does not circumvent the need for you to do this. You can check out the PCI compliance self assessment form here: https://www.pcisecuritystandards.org/merchants/self_assessment_form.php
Available via Sparks. For info about how to install sparks, go here: http://getsparks.org/install
You can then load the spark with this:
There are config files for each gateway in the /config folder of the spark. You need to enter your own API usernames and passwords (the ones in there are mine, used only for testing purposes) in the config of each gateway you would like to use.
If you want to test locally (and you should), you need to set "force_secure_connection" to FALSE in config/payments.php
By default, test api endpoints will be used. To enable production endpoints, change the mode in /config/payments.php from 'test' to 'production'. Note that if you are a Psigate customer, you must obtain your production endpoint from Psigate support.
The following gateways are supported:
- PayPal Payments Pro
- Authorize.net (AIM)
- QuickBooks Merchant Services
- Eway (Australia)
- Amazon SimplePay
- oneoff_payment: Makes a one time charge
- reference_payment: Make a payment based on a previous transaction. Mimics a card vault. Currently only implemented in PayPal Payments Pro.
- authorize_payment: Authorizes a charge, which is essentially a hold. This requires later capturing the funds you authorized (most gateways require you do this the same business day).
- capture_payment: Finalize an authorization, actually charges the customer.
- void_payment: Cancel a payment that has not been settled (transactions get settled at the end of the business day).
- refund_payment: Refund (or credit) a customer for a settled transaction.
- get_transaction_details: Get details from a particular transaction.
- change_transaction_status: Changes a transaction's status, ie to Accept or Decline. Only available with PayPal.
- search_transactions: Query transactions by parameters you define. Only available with PayPal.
- recurring_payment: Start a new recurring profile.
- get_recurring_profile: Get info about a profile.
- activate_recurring_profile: Activate a recurring profile that has been suspended.
- cancel_recurring_profile: Cancel a recurring profile.
- suspend_recurring_profile: Hold the recurring billing, but don't cancel.
- recurring_bill_outstanding: Charge outstanding payments to a customer.
- update_recurring_profile: Update amounts, names, addresses, etc.
If you use a method that is not supported, the gateway will return a local failure.
You can see the params available for each method in /config/payment_types/method_name
An important parameter, that you will use often, is 'identifier.' 'Identifier' is used to uniquely identify recurring transactions and payments. After each payment (ie authorization, capture, recurring billing), an identifier will be returned in the response which you can use to make later calls with that affect that payment.
Examples for all gateways are available in /examples. A request is formatted thusly:
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.:
'type' => 'local_response', //Indicates failure was local 'status' => $status, //Either success or failure 'response_code' => $this->_response_codes[$response], 'response_message' => $this->_response_messages[$response], 'details' => $response_details
Access response properties by naming your call something like this:
$response = $this->payments->payment_action('gateway_name', $params);
Then you can do:
$status = $response->status;
Gateway responses will usually have a full response from the gateway, and on failure a 'reason' property in the details object:
'type' => 'gateway_response', 'status' => $status, 'response_code' => $this->_response_codes[$response], 'response_message' => $this->_response_messages[$response], 'details' => $details
You can access this like $response->details->reason. You may want to save the full gateway response (it's an array) in a database table, you can access it at $response->details->gateway_response
Copyright (c) 2011 Calvin Froedge
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.