MojoEstate
Documentation
MojoScripts
 
   - Introduction
   - Getting Started
   - License Agreement
   - File Check
   - Installation
 
   - News
   - Program Configurations
   - System Behaviors
   - Display
   - Database Fields
   - Gallery File Types
   - Module Manager
   - Member Management
   - Member Mailings
   - Categories
   - Accounts
     - Permissions
     - Preferences
     - Conformations
   - Program Security
   - Admin Groups
   - Automation Routines
   - Debugging
   - Utilities
 
   - HTML Templates
   - Email Templates
   - Text Templates
   - Content Occurances
   - Strings and Tags
   - Featured Ads
   - Specific Program URLs
   - Customization Tips
   - Specific Templates
   - Payments
 
   - Payment Modules
   - Thumbnail Modules
   - View-On-Map Module
   - Chat Module
 
   - Troubleshooting
   - FAQ
   - Support
 
Payments

You can receive payments for single ads, bulk ads or subscriptions using our payment modules, you can add payment links from your desired payment provider or merchant gateway to the payment.html template or you can add information to process payments offline, your address for cash, check mails, etc. You could also add a form there to collect further information.

Using our payment modules, the user registers, selects the desired ad package or membership account and pays for the ads/subscription. After payment he/she is sent back to the site or a custom defined static return URL from the payment processor immediately after successful verification of the transaction, where he/she can post ads or use the account immediately.

For third party payment processing, offline payment processing it is recommended that you verify the transaction first by making sure the funds have arrived in your merchant account, via mail and so on, before assigning the purchased account to the user from the admin area.

The user can also purchase ads, bulk ad packages or recurring memberships at any time later via the buy ad/account upgrade link. The user is presented with a list of available packages and permissions, prices, validity periods (upgrade.html template) and can order the desired package.

Here is a sample of a payment process:

You have setup a commercial account scheme where the user needs to purchase ads. You have turned on "ad credit" system. You have setup the paypal payment module and an offline payment option such as your address for check payments.

The user arrives at your site > views your "buy ad" information page > decides to post an ad > registers > is forwarded to the payment page with various payment options you offer (in this case a paypal link and your address to mail a check) > he decides to use paypal and is forwarded to paypal for payment > successful verification > user returns to your static thank you page > logs in and posts an ad, uploads photos etc.

During the ad posting process, the user decides to make the ad featured, sponsored and add special visibility to the ad > he enters the "Add funds area" > enters an amount and selects paypal as processor > is forwarded to paypal for payment > successful verification > user returns to your static thank you page > as logged in user he can now post an ad with featured ad, sponsored ad and special visibility, upload photos etc.

Now the same user decides to purchase another ad allowance, or even a bulk of several ads > views your "buy ad" information page > orders a package > system checks here is enough funds on the balance for payment, if not, user forwarded to the payment page again with various payment options you offer > decides for paypal and is forwarded to paypal for payment > successful verification > user returns to your static thank you page > as logged in user he can now post an ad, upload photos etc.

Remarks:

1. If the user would have sufficient money on his account balance, the system would deduct the amount from this balance and the user would immediately be able to post ads and use his ordered account package.
2. If you are using only one dedicated payment processor, the payment options page is skipped and the user forwarded directly to the payment provider.

Additional notes:

  • In a subscription scenario, a cron job deducts money from users account balance directly when their membership expires at the end of the last membership term.
  • User area: In the user area, the user may view account balance and transaction history, make single and recurring payments.
  • Admin area changes: admin may view account balance field and transactions history


Copyright by MojoScripts.com
Terms | Privacy Policy