What is Payment?
Payment is a general payment platform which allows other modules to use any of the payment methods that plug into Payment. With Payment we only need one one Paypal, one credit card and one iDEAL module to use with every single webshop or payment form that you want (applies to any payment method that works with Payment). This shortens development time and improves support, because only one instead of three Paypal modules need to be maintained, and simplifies UX, because all payment (method) information is now located in one place.
Project contents
| submodule | requires | is enhanced by | integrates with |
|---|---|---|---|
| Payment The main API |
|||
| Payment Form Field Provides a field to add payment forms to entities. |
|
||
| Basic Payment Method A 'dumb' payment method type that always successfully executes payments, but never actually transfers money. It can be useful for collect on delivery, for instance. |
|
||
| Billing Adds billing information to payments |
|
||
| Payment Reference Field Provides a field to add payments to entities. |
|
- is enhanced by means the submodule offers extra features when the listed modules are enabled.
- integrates with means the listed modules offer extra features when the submodule is enabled.
Modules that use Payment
| module | requires | description |
|---|---|---|
| Drupal Commerce | Payment for Drupal Commerce | Makes all payment methods usable within Drupal Commerce. |
| Drupal Commerce | Payment for Ubercart | Makes all payment methods usable within Ubercart. |
Further integration planned with
- iDEAL (in progress)
- iDEAL Lite/Basic/Only
- Moneybird (in progress)
- Paypal
- Webform
- Credit card processing
Differences between Payment and Pay
"But we already have Pay!", you say. This is right. Payment is the continued development of iDEAL, with the iDEAL-specific code stripped out and a bunch of improvements, which are also based on experience with Drupal Commerce. It takes a different approach to be more light-weight and flexible than Pay is. Some differences:
- Pluggable payment status information
- Strict separation between API and UI
- Strict separation between API and specific payment methods
- Extensive developer documentation (workflow diagrams exist, but need to be added/published)
- More integration with core and other contributed modules
- More test coverage
Downloads
Recommended releases
Development releases
Project Information
- Maintenance status: Actively maintained
- Development status: Under active development
- Reported installs: 23 sites currently report using this module. View usage statistics.
- Downloads: 409
- Automated tests: Enabled
- Last modified: May 22, 2012