Download the PHP package pronamic/wp-pronamic-pay without Composer

On this page you can find all versions of the php package pronamic/wp-pronamic-pay. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package wp-pronamic-pay

Pronamic Pay

WordPress plugin WordPress WordPress rating WordPress WP compatibility [PHP from Packagist]() Build Status Coverage Status Built with Grunt codecov

The Pronamic Pay plugin adds payment methods like iDEAL, Bancontact, credit card and more to your WordPress site for a variety of payment providers.

Supported payment providers

Provider Name
ABN AMRO ABN AMRO - iDEAL Zelfbouw - iDEAL 2.0
Adyen Adyen
Buckaroo Buckaroo - HTML
European Merchant Services EMS - e-Commerce
ING ING – iDEAL Advanced - iDEAL 2.0
Mollie Mollie
MultiSafepay MultiSafepay - Connect
Pay.nl Pay.nl
Rabobank Rabobank - OmniKassa 2.0
Rabobank Rabo iDEAL Professional - iDEAL 2.0

Supported WordPress e-commerce extensions

Name Author WordPress.org GitHub Requires at least Tested up to
Charitable Studio 164a WordPress.org GitHub 1.3 1.7.0.11
Contact Form 7 Takayuki Miyoshi WordPress.org GitHub 5.2.0 5.7.6
Easy Digital Downloads Pippin Williamson WordPress.org GitHub 1.8.6 3.1.0.3
Event Espresso 4 GitHub 4.4.7.p 4.10.8.p
Event Espresso 4 Decaf WordPress.org GitHub 4.4.4.decaf 4.10.8.decaf
Formidable Forms Strategy11 WordPress.org GitHub 2.0.22 6.5.4
Give WordPress.org GitHub 1.8.0 2.27.0
Gravity Forms Rocketgenius 1.9 2.7.5
Gravity Forms AWeber Add-On Rocketgenius 1.4.2 3.0
Gravity Forms Campaign Monitor Add-On Rocketgenius 2.5.1 3.9.1
Gravity Forms MailChimp Add-On Rocketgenius 2.4.1 5.2.0
Gravity Forms User Registration Add-On Rocketgenius 1.8 5.1.1
Gravity Forms Zapier Add-On Rocketgenius 1.4.2 4.2.1
MemberPress Caseproof, LLC 1.9.21 1.9.53
Ninja Forms The WP Ninjas WordPress.org GitHub 3.3.15 3.6.23
Restrict Content Pro Sandhills Development, LLC 3.0.0 3.4.4
WooCommerce Automattic WordPress.org GitHub 2.3.0 8.2.2

Installation

Extract the zip file and just drop the contents in the /wp-content/plugins/ directory of your WordPress installation and activate the plugin from the Plugins page. Next, create a new configuration with the account details for your payment service provider account and enable the payment method in one of the supported e-commerce plugins.

Are there any known plugin conflicts?

Unfortunately WordPress is notorious for conflicts between themes and plugins. It is unavoidable as you have no control over what other plugins and themes do. While we do take steps to avoid conflicts as best we can, we have no control over other plugins or themes.

As conflicts are found we will update this list. If you discover a conflict with a another plugin, please notify us.

Here is a list of known plugin conflicts:

WPML

The WPML plugin(s) can conflict with multiple gateways. A lot of the gateways use home_url( '/' ) to retrieve the WordPress home URL. The WPML plugins hooks in to this function to change the home URL to the correct language URL. This can result in incorrect checksums, signatures and hashes.

WordPress HTTPS

The WordPress HTTPS can conflict with the OmniKassa payment method. It can cause invalid signature errors. The WordPress HTTPS plugin parses the complete output of an WordPress website and changes 'http' URLs to 'https' URLs, this results in OmniKassa data that no longer matches the signature.

Links

All versions of wp-pronamic-pay with dependencies

PHP Build Version
Package Version
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package pronamic/wp-pronamic-pay contains the following files

Loading the files please wait ...