[Wiki] changed: Project/Horde_Payment

duck  Thu, 29 Jan 2009 20:13:06 -0500

Modified page: http://wiki.horde.org/Project/Horde_Payment
New Revision:  1.12
Change log:  steps

@@ -38,8 +38,22 @@
  * Limit payment methods per application
  * Limit payment methods per amount
  * Virtual host support
  * Possibility to add a testing process request
+
++ Payment process for user
+
+++ Step 1: Type selection
+When the user is redirected to the selling interface, he/her will be  
asked to select a payment module. The list will be populated with all  
modules available that are active, linked to application owning the  
transaction and in the amount value parameters. If there is only one  
module available, the selection screen is avoided and user is  
redirected directly to the next step. User can always come back and  
choose another method, as revoke a transaction at any time.
+
+++ Step 2: Enter data
+User is asked for additional data required by the selected module.  
Values are stored in database for administrative purposes. This step  
is automatically skipped for modules does not need additional data  
entered by user. (See Horde_Payment_Method::hasLocalForm())
+
+++ Step 3: Validation
+The validation process of the payment module will be called or the  
user will be redirected to the remote validation page if the module  
has it. Here is where the selling application will be called back to  
be notified about authorization status change. (See  
Horde_Payment_Method::hasRemoteValidation(),  
Horde_Payment_Method::process())
+
+++ Step 4: Redirection page
+The user will be redirected back to the selling application page or  
to the result of the “authorizationReturn” call.

  +++ authorizationRequest() usage example

  <code type="php">

--
To unsubscribe, mail: [email protected]