Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
This project integrates Drupal with Recurly, a subscription billing service that takes the headache out of subscription management. It can work in conjunction with your existing payment gateway or merchant account (see the list of supported payment gateways) or you can use the included Recurly Gateway (which is included free with all accounts).
This project includes a few sub-modules that allow users to choose how deeply they wish to integrate their Drupal site with Recurly:
Recurly: The main Recurly module provides basic Drupal integration, including receiving push notifications from Recurly.com. It also includes built-in pages for users to view invoices, subscriptions, and to upgrade/downgrade their subscription level.
Recurly Hosted Pages: Rather than hosting account management yourself, you can use Recurly.com to handle all aspects of subscription management through their hosted pages option. This requires the least amount of integration with Drupal, thus the least responsibility for customer data. Recurly's hosted pages are PCI-DSS Level 1 compliant. Sites using this solution will still need to comply with the shortened self-assessment questionnaire (SAQ-A) to meet PCI compliance on their own site.
This module integrates the popular open source ad server Revive Adserver (formerly OpenX and before that Openads) with Drupal. The last versions the Drupal 6.1.x branch of this module was tested with were OpenX 2.6 and OpenX 2.4. The Drupal 6.2.x branch and 7.1.x versions of this module have been tested with Revive Adserver is 3.0.5 but have not been tested with any previous versions of Revive Adserver and its previous incarnations (OpenX/Openads).
Webform Stripe adds super simple Stripe integration to Webforms, so that submissions can be "purchased".
With this, you can use webforms for event registrations, online donations, or even for simple products where you need to gather additional information from a user. Each webform can have fixed pricing, or it can be determined dynamically from another field component on the form.
This module changes the default functionality of Commerce to use a static url in checkout instead of dynamic one that changes in every order.
It is supposed to be a helper module for banking institutes that don't accept dynamic urls.
It simplifies development of redirection-payment modules, by allowing developer to deal only with each bank and not with the static url needed.
All Greek banksm and probably many other banks, that offer a redirection payment method require static urls to work. This is where commerce_static_checkout_url comes in, it creates the static url so the bank can accept and validate requests from your site.
Greek Banks Modules
Modules for the greek banks Alphabank, Eurobank and Winbank - Peiraius are already available while a module for NBG is under development but there is no scheduled release date.
Multilingual support, for the dev revision
In order for a site to be multilingual, you have to set all prefix paths for all availiable languages, do not use domain for language identification, and finally enable the Session detection method.
Allows the management of one or more "splash offers", which are modal popups with an accept or reject form. If a user accepts the offer then a new page will open with a provided accept url. If they reject the offer, the modal will close. (If they select Do not Show Again, then a cookie is set so as to avoid futher display.) You may define the who, when and where of the splash offers with precision controls. Factors such as: user role, site url, device, and whether the offer has been previously viewed (cookies), cookie duration, etc. are configurable for each splash offer created.
The module was born as a way to advertise a website companion app and offer a button to download, but it's generalized nature has the potential for many other applications.
This project creates a new entity type and thus depends on the Entity API:
This module extends Commerce Stock to allow "reserving" a product's stock when a customer adds it to their shopping cart. This removes the risk of overselling when multiple customers are attempting to buy the same product at the same time.
The Drupal RETS Real Estate Framework (dRealty) enables administrator-developers to get real estate data via RETS and maintain a copy of that data in Drupal. dRealty is focused on that one-way data flow, and it does not include a user interface beyond administrative and configuration pages.
The Drupal 8.x release is being designed, and the download is unusable and unsupported until further notice. If you would like to join the 8.x work then review the issue "Plan for dRealty for Drupal 8". The next hangout for coordination is scheduled to be April 22, 2016, at 1 pm ET.
Repeat customers are your best customers; you can rely on them to keep coming back to your store so long as you provide the goods or services they need. They are a steady revenue stream, an easy sell. But to quickly close the sale you need to make it easier for them to find and purchase more of the same stuff they've ordered previously.
This module lets your customer (or you, the admin) duplicate a previously placed order. It works by modifying the user order history page (e.g. user/4/orders) to display a "Re-Order" button for each previous order. The user can click on the link to have all the items from that previous order added to his or her current cart. Items added to the cart in this manner will have the current price, but will otherwise preserve all the same attributes as in the previous order.
When stock tracking (using the Inventory API) is enabled, products are only added to the current cart if they are in stock.
The Ubercart Disable Store module adds the ability to disable Ubercart store (hide/disable add to cart, etc) for some conditions.
Ex. Wholesaler requires Reseller Accounts to shop: If your website should display Ubercart products to some or all but only allow show Add to Cart forms for certain roles, for instance, then this module is for you.
This module integrates Shopify with your Drupal website.
Your Shopify products are synced to your Drupal site in real time as Drupal entities. These product entities are fieldable, themable, and completely Drupalized. Shopify's clean and intuitive interfaces power your store's back office and Drupal is used for product display. Customers check out using Shopify's checkout workflow.
Commerce Credits allows you to have users buy or win credits. The credits these users buy or win are fully configurable and can expire after some time. The process used for these credits is also fully configurable through Rules. It allows you to entirely define your own process for the payment and the use of these credits.
Unfortunately, there isn't much of an English Alipay document describing the different services.
More information would be available in Chinese at: 平台商产品 （专为交易平台所提供的收款方案）.
Currently supports the following Alipay service types:
✓ Instant Payment / 支付宝即时到账收款接口(tested and supported)
Through an instant payment channel, an Alipay account owner is able to remit directly to seller, enabling quick gathering and withdrawal of funds, resulting in an improved utilization of funds. (see screenshot of the payment pane on checkout when the Instant Pay payment method is enabled)
More work and testing to be done on:
Escrow Payment / 支付宝担保交易收款接口
The third-party (Alipay) guarantees that the buyer can receive goods and seller can obtain the funds. The usually procedure being: