Payment | |
Payments can be entered manually (for cash or check payments) or through PayPal, CCLite for community currency payments, or using Credits. Payments don't require a relationship to a site user. Each payment is standalone and can be paid by anyone, provided they can view it. Visibility is managed through permissions. Provided a direct link to a payment, anyone can view and pay the amount, which is useful, for example, to forward an invoice to a manager. The payment mechanism enables actions to be registered when the payment is completed, allowing other components in Tiki to request payments and act on them. |
Membership Management | |
Payments can be combined with PluginMemberPayment and group expiration to automatically subscribe members to a group or extend their membership upon payment. Here are typical steps to have a monthly membership feature at a Tiki site:
Upon payment confirmation by PayPal IPN or manual payment entry by a staff member (in the case of a physical check or cash payment), the memberships will be extended. |
Cart | |
Initial support for a shopping cart has also been added. The cart feature is composed of a module to display the cart content and proceed to check-out and a wiki plugin to add items to the cart. The plugin must specify the information about the product purchased. Once products are added and check-out is done, a payment request is recorded and the invoice is presented to the user. All handling of the cart's content by the site's owner is manual. The cart does not calculate taxes or shipping costs. It only adds up the costs of all items. |
Development | |
The Payment API is built to be initialized in code and to have behaviors to be triggered on confirmation. For custom usage or further deployment in Tiki (member management is one use case), see Payment. Some tips about how it works: https://www.paypal.com/en_US/ebook/PP_OrderManagement_IntegrationGuide/ipn.html |
Notes | |
|
Files/URLs | |
tiki-admin.php?page=payment
|
Related | |
|
Alias | |