Closed (fixed)
Project:
Authorize.Net® Webform Payments
Version:
7.x-2.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Issue tags:
Reporter:
Created:
11 Oct 2010 at 05:17 UTC
Updated:
10 Dec 2018 at 01:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
obsidiandesign commentedThe features/code outlined in http://www.authorize.net/support/ARB_SOAP_guide.pdf would need to be added to the module. Right now, I wouldn't add these features until after Webform 3.x support is included, as I see that as a higher priority. It's definitely doable - if you have the time, feel free to implement it & then submit a patch with the features included.
Bryan O'Shea
Obsidian Design
Comment #2
jmcclelland commentedThis is ugly and could use some serious refactoring (maybe the authorizenet code could all be moved to a authorizenet_api module that could be shared amongst all the authorizenet modules?).
However... it seems to be working. It's not patched against the current version. Instead, it's patched against the patched webform 3 version (http://drupal.org/node/897090#comment-3622736).
jamie
Comment #3
obsidiandesign commented@Jmcclelland - thanks for another awesome patch. I'm definitely open to moving the actual connection code out (I've thought about doing something similar with the connection code for the Salesforce Webform module that I maintain for a similar reason). Would that make things easier to work with?
Comment #4
jmcclelland commentedWhile working on this project, I noticed several other modules providing authorize.net features (like http://drupal.org/project/ec_authorize_net, http://drupal.org/project/ubercart, and http://drupal.org/project/authorize_donate). Seems like if all the modules were all able to share a single module which contained the authorize.net code and provided the necessary functions to process a payment, it would free everyone up to focus on exactly how their module is distinct (e.g. this module could focus on just webform integration).
By the way... thanks for your work on this module - it's really doing the trick for us :).
jamie
Comment #5
Windsinger commentedHi,
has this been added to any newer development builds? I have it partially working as it correctly submits the ARB to authorize.net, but the initial charge is failing; the drupal response is saying "There was an error processing your credit card. Credit card number is required. If the error persists, please try another card.
I had to do some bad programming to get this code to work in the latest development release so I am not knowing what I am doing really...
thanks!
Comment #6
jenlamptonI'm bumping this feature request to the 7.x branch. It won't likely be supported for 6.x but it's a good feature and should be added. I hope to work on it myself this week.
Comment #7
jenlamptonI'm going to be working on this in the 7.x.2.x branch, so bumping version number here.
Comment #8
jenlamptonOkay - I've got an a version using Accept.js with recurring billing: 7.x-2.0-alpha1. I'd love some help testing it before a final 1.0 release.
Comment #9
jenlamptonAnother release is out with recurring payments, I'm going to close this issue but if anyone has any issues please open new issues against this branch.