WorldPay integration for WooCommerce.
- Minimum Requirements
- Installation
- Setup
- Security Concerns about WorldPay HTML API
- Not Issue
- Features
- Not Supported / Not Implemented
- Best Practices
- Test Sandbox
- FAQ
- Coding
- Feedback
- Security
- Change log
- Credits
- License
- PHP v7.2
- php-curl
- WordPress v4.9.8
- WooCommerce v3.4.5
$ composer require itinerisltd/wc-worldpay
Payment response(redirection) and Enhancing security with MD5 are mandatory.
On WorldPay's integration setup page:
- Enable Enable the Shopper Response
- Enter
<wpdisplay item=MC_callback>
as Payment Response URL - Enable Payment Response enabled?
- Enter a 25-char random passphrase as Payment Response password
- Enter a 30-char random passphrase as MD5 secret for transactions
- Enter
instId:amount:currency:cartId
as SignatureFields
Then, fill in the same information on WP admin dashboard - WooCommerce > Settings > Payments > WordPay.
Note that WorldPay truncate long Payment Response password without notices!
- Leaking MD5 secret for transactions
- Allow evil hackers to set up fake checkout pages, pretending to be the merchant
- WorldPay would accept these checkouts and charges the credit cards
- Leaking Payment Response password
- Allow evil hackers to pretending to be WorldPay
- WordPress would accept evil hackers' payment callbacks and changes order payment statuses
If Payment Response password(also known ascallbackPW
) is incorrect, InvalidResponseException
is throw to stop the world.
Credit card holders see white screen of death in such case.
- Shipping address
- Reject according to fraud check results
- Token payment
- Recurring payment
- Refund
- Void
Although WorldPay accepts insecure HTTP sites, you should always use HTTPS to protect all communication.
Always double check payment status on worldpay.com
.
Use this test credit card.
No! support.worldpay.com
does not support HTTPS.
This is unacceptable. Please encourage them to use HTTPS everywhere.
Never! This plugin will only works on actively supported PHP versions.
Don't use it on end of life or security fixes only PHP versions.
- Articles on Itineris' blog
- More projects on Itineris' GitHub profile
- Follow @itineris_ltd and @TangRufus on Twitter
- Hire Itineris to build your next awesome site
Thanks! Glad you like it. It's important to make my boss know somebody is using this project. Instead of giving reviews on wp.org, consider:
- tweet something good with mentioning @itineris_ltd
- star this Github repo
- watch this Github repo
- write blog posts
- submit pull requests
- hire Itineris
Read the followings before developing:
- WorldPay HTML API
- Omnipay: WorldPay
- thephpleague/omnipay#255 (comment)
Omnipay\WorldPay\Message\PurchaseRequest::getData()
$ composer test
$ composer check-style
Pull requests without tests will not be accepted!
Please provide feedback! We want to make this library useful in as many projects as possible. Please submit an issue and point out what you do and don't like, or fork the project and make suggestions. No issue is too small.
If you discover any security related issues, please email hello@itineris.co.uk instead of using the issue tracker.
Please see CHANGELOG for more information on what has changed recently.
wc-worldpay is a Itineris Limited project created by Tang Rufus.
Full list of contributors can be found here.
wc-worldpay is licensed under the GPLv2 (or later) from the Free Software Foundation. Please see License File for more information.