Payment

Abstract

Payment is a new feature in Tiki5 The Payment API is built to be hooked from multiple parts of the system. While there is a user interface, the primary purpose of it is for management. Payment requests should be hooked to actions in the system. A good example is the PluginMemberPayment. A payment request is like an Invoice. A registered payment will execute a set of behaviors when events occur. Supported events are 'complete', for when the payment is fully paid, and 'cancel' when the payment is abandoned. The behaviors can only be registered through the API. Manually created payments must be handled manually. Behaviors are stored in lib/payment/behavior/ and are named like the behavior called ('sample' would be in sample.php). Inside those files, a function named payment_behavior_sample is expected to be present. When the behavior is registered, an array is provided.