matt/uc_stripe
1
0
Fork 0
Code Issues 1 Pull Requests 2 Packages Projects Releases Wiki Activity

Update from remote.

Browse Source
This commit is contained in:
Matt
2019-10-04 21:05:43 -05:00
parent 017b4b731c
commit 01a5a1b15f
7 changed files with 923 additions and 361 deletions
Download Patch File Download Diff File Expand all files Collapse all files

53
README.txt
View File

@ -1,4 +1,8 @@
This is an Ubercart payment gateway module for Stripe.
This is an Ubercart payment gateway module for Stripe. It maintains PCI SAQ A
compliance which allows Stripe, the payment processor, to handle prcoessing and
storing of payment card details.
It is compliant with 3D Secure, 3D Secure 2, and Strong Customer Authentication (SCA)
Versions of the Stripe PHP Library and Stripe API that this module currently
supports are found in uc_stripe_libraries_info() in uc_stripe.module.
@ -15,9 +19,9 @@ section, and enable the gateway under the Payment Gateways.
c) On that page, provide your Stripe API keys, from
https://dashboard.stripe.com/account/apikeys
d) Download and install the Stripe PHP Library version 2.2.0 or >=3.13.0
from https://github.com/stripe/stripe-php/releases. The recommended technique is
to use the command
d) Download and install the Stripe PHP Library version 6.38.0 with stripe api
2019-05-16 or newer from https://github.com/stripe/stripe-php/releases. The
recommended technique is to use the command
drush ldl stripe
@ -25,8 +29,7 @@ If you don't use "drush ldl stripe", download and install the Stripe library in
sites/all/libraries/stripe such that the path to VERSION
is sites/all/libraries/stripe/VERSION. YOU MUST CLEAR THE CACHE AFTER
CHANGING THE STRIPE PHP LIBRARY. The Libraries module caches its memory of
libraries like the Stripe Library. (Version 2.2.0 support is maintained for
existing users; version 3.13.0+ supports PHP 7 and will get ongoing support.)
libraries like the Stripe Library.
(With the latest version of the libraries module you can use the command:
e) If you are using recurring payments, install version 2.x
@ -48,14 +51,35 @@ disabled on admin/store/settings/payment/method/credit - uc_credit never sees
the credit card number, so cannot properly validate it (and we don't want it to
ever know the credit card number.)
Upgrading from uc_stripe 6.x-1.x or 7.x-1.x
i) uc_stripe creates it's own payment pane. Ensure the correct ordering by visiting
store->configuration->checkout (admin/store/settings/checkout).
Upgrading from uc_stripe 7.x-2.x
===========================================
7.x-2.x does not use Stripe subscriptions for recurring payments, but instead
uses the uc_recurring module. This means you have control of recurring
transactions without having to manage them on the Stripe dashboard. (Credit
card numbers and sensitive data are *not* stored on your site; only the Stripe
customer ID is stored.)
7.x-3.x maintains PCI SAQ A compliance and has major implementation changes from
2.x. This version uses it's own payment pane in uc_cart to collect card info.
The card fields such as card number, expiration date, and cvc code have all been
hidden, and is handled entirely by Stripe's Element implementation.
Which means no credit card information gets processed at all by drupal. The last4,
and expiration date are sent back to drupal by Stripe's api.
7.x-3.x no longer creates a new stripe customer for each order. If a drupal user
already has a stripe customer ID, this module will attach future orders to that
exisiting stripe customer ID.
When upgrading from 2.x the ordering of the new stripe payment pane should be
verified at store->configuration->checkout (admin/store/settings/checkout).
An upgrade of the stripe library is required. See installation step d from above.
7.x-3.x Uses the uc_recurring module for recurring payments. It is also equipped
to handle recurring payments that require authentication (See the uc_recurring
steps below). Exisiting recurring payments set up with 7.x-2.x work without any
configuration changes.
Upgrading from uc_stripe 6.x-1.x or 7.x-1.x
============================================
The upgrade hooks, however, must move the customer id stored in the obsolete
uc_recurring_stripe table into the user table. When this happens the old
@ -84,6 +108,11 @@ Recurring payments require automatically triggered renewals using
uc_recurring_trigger_renewals ("Enabled triggered renewals" must be enabled
on admin/store/settings/payment/edit/recurring)
You should also set your email message for recurring payments that require
Authentication. The system will email your customers with a link so that they
can authenticate and have their payment processed.
(You can edit from here: admin/store/settings/payment/edit/gateways)
If you were using Stripe subscriptions in v1 of this module, you may have to
disable those subscriptions in order to not double-charge your customers.