Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.We need a way for customers to update their own credit card information when their card expires, etc. - I'm unaware (and unable to find) a different Ubercart solution, though there may be one (IMHO there should be one). However, a feature addition to this module may be the only way since it directly interfaces with PayFlow recurring profiles.
Comments
Comment #1
beifler commentedI just realized the UC Recurring module may have a feature for this, but I don't know. - Also realized Ubercart core has no need to store CC info.
Comment #2
kwinters commentedHi Bren,
Ubercart only stores CC info in the database in test mode, because it's a PCI compliance nightmare to store that long-term in the site's database. All that information is in stored exclusively on PayPal's side.
The gateway seems to allow modifying CC info from the Drupal side, but I'll have to add an interface for it and set up the new service requests. That will be a fair chunk of work.
The workflow I'm envisioning is:
* User goes to their account page tab that lists their recurring subscriptions (where they'd go to cancel)
* A new Edit Credit Card button takes them to a form with just the CC fields (name on card, number, etc.) -- needs to be HTTPS
* Submitting the form sends a request to PayPal with the new info, and returns a success or fail message
There are potentially a lot of enhancements to the whole process (letting customers know when they need to update their card info, etc.) but that will probably be a lot of work and uc_recurring may already do a lot of this. So, if we're going to do anything before a uc_recurring integration then I think it should be minimal to avoid wasted effort.
Comment #3
kwinters commentedI've backported the credit card update feature from 6.x-2.x. It's in the 6.x-1.x dev branch now (tarballs are released every 12 hours for dev branches, or you can use CVS to get them immediately).
Setting status to review, since it's a fairly major new feature and I'd like to have someone else try it out before making an official release.
An important note: URLs of the pattern /user/*/pfp_cpanel/*/cc_update should now be forced to use HTTPS in a live environment because it contains a credit card form. I will document this on the main page when I roll a release.
Comment #4
cwithout commentedI was able to test it using the dev Payflow environment. The credit card data was updated successfully and the recurring fee was charged as it should have been. I'm not currently able to test it on the Live environment.
Comment #5
kwinters commentedAvailable in the 6.x-1.4 release.