Follow for free plugins, new theme releases and theme news
Plugin Description
Overview:
This plugin facilitates selling of products and services on any public page
of a WordPress website, and accepting credit card payments for these
products and services via the Stripe payment processor.
Because this plugin facilitates credit card payment processing specifically
via Stripe, it is able to leverage the main security feature of that service,
in that the credit card numbers are sent to the Stripe servers directly via
their Checkout API, and never to the server running the website. Because
the credit card numbers are physically absent from the website server, the
operators of the website server are not subject to various government
regulations that might have otherwise come into effect had their server
indeed stored credit card numbers. And obviously, even if the website
server or its storage get compromised by criminals, there simply would not
be any credit card numbers for them to steal.
The way this plugin is used, is that first, the administrators specify which
products and services are being sold, their descriptions, prices, etc. by
inserting special shortcodes with that information directly into the pages
and posts on which they want to render the user payment buttons for these
sales. When site visitors load these pages, they see the associated payment
buttons, clicking on which opens payment entry forms. Submitting a payment
creates a “pending transaction”, details of which can be automatically
emailed to the site operator(s). For each pending transaction, site
administrators can click a special “Charge” button on the plugin’s admin
page to charge that transaction via Stripe. This creates a record for the
customer and the charge on the Stripe servers, from which point the
transaction can be administered via the Stripe website as any other Stripe
transaction.
Stripe test transactions are also supported. These are transactions in
which no actual real credit card gets charged.
Currently only USD are supported.
Demo at: http://maratbn.com/projects/rainbow-pay-press/#demo
Technical summary and special considerations:
Initially, buyer identity, stored partially on the website server, is tied
to their credit card number stored entirely on Stripe servers, via a special
“Stripe Token”, which is obtained directly from Stripe, via the plugin’s
JavaScript logic, running in the buyer’s browser. For this reason,
JavaScript needs to be enabled in the buyer’s browser.
Plugin relies on special server-side PHP library stripe-php to communicate
with the Stripe servers to direct them to charge credit cards. This PHP
library in turn relies on PHP cURL support enabled on the server. The
plugin will check if this support is enabled, and will issue admin dashboard
notification if it is not, which will also give advise on how to enable it.
If website administrators wish to enable automatic email notifications, they
would need to insure that a Mail Transfer Agent (MTA) is properly configured
on their website server. Even when the MTA is properly configured, the
email notifications are still likely to get filtered by SPAM filters, so
adjustment of SPAM filters might also be needed.
Requires:
- PHP version >= 5.4
- PHP cURL support enabled (Install module ‘php-curl’ on Debian / Ubuntu)
- PHP multibyte string support enabled (Install module ‘mb-string’ on Debian / Ubuntu)
- Proper Mail Transfer Agent (MTA) configuration for notification emails.
Official project URLs:
https://wordpress.org/plugins/rainbowpaypress
https://github.com/maratbn/RainbowPayPress
http://maratbn.com/projects/rainbow-pay-press
Screenshots
Examples of shortcode syntax, and display of all the transaction details entry fields that can
be made available to the buyer on any page of the website.
The official Stripe Checkout Dialog that appears when the buyer clicks to enter the Stripe
token id or Stripe card email fields.
RainbowPayPress admin menu.
Example of transaction details entry fields filled out by the buyer just before transaction
submission.
Transaction submission confirmation message displayed to the buyer after transaction
submission. The confirmation message includes the timestamp of the submission and the Stripe
token that can be used by the website administrator(s) to charge the buyer’s credit card.
The ‘Pending Transactions’ and ‘Charged Transactions’ tables as they appear to the website
administrator(s) on the ‘Transactions’ admin page, containing the data for example
transactions. New transactions are initially inserted as new rows to the top of the ‘Pending’
table, Clicking the ‘Charge’ button charges the transaction, and moves the associated record
to the top of the ‘Charged’ table. The ‘Charged’ table contains additional columns ‘Customer
ID’ and ‘Charge ID’. These data tokens are created by the Stripe business logic when the
transaction is charged, and they are rendered as web links, clicking on which takes the user to
the associated records on their Stripe account on the Stripe website.
The ‘Items’ table as it appears to the website administrator(s), containing an example list of
items that can be specified for sale via RainbowPayPress shortcodes.
The RainbowPayPress ‘Settings’ page as it appears to the website administrator(s) with some
example settings.
A screenshot of a customer record as it appears on the Stripe website. This record was created
when the associated transaction was charged by clicking on the ‘Charge’ button on its row on
the ‘Pending Transaction’ table on the ‘Transactions’ admin page. Once a transaction is
charged, all records associated with that charge can be tracked on the user’s Stripe account.
