Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I'm attaching a module which I derived from the current D7 dev version of uc_payment_pack to provide a very basic option for handling credit card payments, but without actually using a payment gateway or storing card #'s. I'm calling it "Credit Card Lite."
That is, similar to how the "Check" payment option will record for each order a date, check #, and whether the check cleared or not, my derivative module will record for each order the date, and whether the card pymt cleared or not. My module records no credit card numbers; it assumes the vendor will follow up with each customer via telephone or in person.
Also, I modified the mailing address variables that were stored under the rubric "make checks out to this address ..." to instead display "this name and address will appear on your card statement ..."
The ideal use case would be for a small vendor who doesn't yet have an online merchant account, Paypal, Authorize.net, etc, but who can process credit card payments over phone or in person with a card reader. I see that someone requested a similar feature of Ubercart in D6 here:
http://drupal.org/node/963610
Does this look like a worthwhile feature to support for UC? Suggestions? Easier ways to accomplish the same with existing UC code?
Do please note that I only wrote this derivative module (in 2hrs) for particular client, and I would be hard-pressed to continue supporting the module if there is large feature set.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | uc_cc_lite-7.x-1.1-dev_tar.gz | 4.16 KB | pgreenhough-1 |
| uc_cc_lite-7.x-1.x-dev.tar_.gz | 3.52 KB | westbywest |
Comments
Comment #1
TR CreditAttribution: TR commentedI don't think this should become part of Ubercart core, but it would be nice if you would publish it on drupal.org as a standalone module. It is very, very similar to a number of other payment methods, like Check, Purchase Order and probably a few others I don't know about. The only real difference is the text presented to the customer explaining how the payment works.
Comment #2
TR CreditAttribution: TR commentedComment #4
westbywest CreditAttribution: westbywest commented@TR Thanks for the response. The original motivation for writing / deriving the module was to provide my client with the basic accounting ability to track (manual) credit card transactions separately from check transactions, hence the superficial code changes.
Writing a custom module to just form_alter() the existing check payment method in uc_payment_pack would not have been adequate, as I need to retain the ability to process check transactions. Also, the 2nd existing method "other" was a bit too vague and non-customizable to display on customer-facing payment forms.
A possible further development of this module could be to add support for tracking credit card transaction fees (i.e. similar to how tax rates are tracked).
Since it's likely not worth the effort support this as a stand-alone module, do you know of similar existing contrib modules for UC? I couldn't find any in my own search, hence writing my own.
Comment #5
natukI, too, have use for this, so having it as a separately maintained module makes sense.
Comment #6
pgreenhough-1 CreditAttribution: pgreenhough-1 commentedI added this module to one of my client's stores using the 7.25 Drupal. Testing it revealed a few issues relating to database calls and a descriptor that was too long for the current database field size. I made a few changes, and now the module seems to work very well.
In case anyone else would like to use it, I have attached a revised derivative module (uc_cc_lite-7.x-1.1-dev). Thanks to westbbywest for making it available in the first place.