Closed (fixed)
Project:
e-Commerce
Version:
master
Component:
payment
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
28 Jul 2007 at 00:58 UTC
Updated:
29 Nov 2007 at 17:19 UTC
Guys,
there are many companies on the world that has a custom payment system. There are too many! We just cant support them all. If we create the module, who are going to maintain, fixing bugs and answering issues? Its just too much work.
Thats why we selected a few but very popular ones. We will maintain them.
New payment gateways should be created as a separated module. See the current modules, study.
Here is a list of new payment gateways requested. Anyone interested on develop them can see it.
Comments
Comment #1
brmassa commentedfor proposed new modules see:
http://drupal.org/node/71706
http://drupal.org/node/79674
http://drupal.org/node/92516
http://drupal.org/node/65343
Comment #2
brmassa commentedsee http://drupal.org/node/68371
see http://drupal.org/node/148613
see http://drupal.org/node/75219
Comment #3
simeGood thread.
A bit of history, there is a "New Payment Modules" section of this page:
http://drupal.org/node/66801
The link there back to the issues queue doesn't work any more though. It relied on new tickets for gateways being marked "postponed" in the "payment" component type. There were half a dozen in the search results but they've all be differently marked it seems. (It was a while ago since I did that).
Also, I myself recently encountered this issue of new gateways. I usually recommend eway (which is in ecommerce) but I can't also control my customer's decisions. So I've started this for any Australian related code I need to maintain.
http://drupal.org/project/ecommerce_au
E-Commerce has a reputation for bloat, so it would be great to convince gordon to move eway and ccard in here and become a co-maintainer. I've come to the conclusion that the only payment types in ec core should be generic or international.
Comment #4
brmassa commentedSimon,
i agree.
massa
------
more one
see http://drupal.org/node/130302
Comment #5
brmassa commentedone more: http://drupal.org/node/71555
Comment #6
brmassa commentedand this one: http://drupal.org/node/103992
Comment #7
brmassa commentedhttp://drupal.org/node/112535
Comment #8
brmassa commentedGoogle Checkout module also must be created as a separated module: http://drupal.org/node/71568
Comment #9
abramo commentedfor 2checkout see: http://drupal.org/node/74078
Comment #10
brmassa commentedLinkPoint at http://drupal.org/node/141785
Comment #11
Jim Phlew commentedWhen one says "create a new module" relating to a new payment gateway, is this referring to simply adding a module in ecommerce/contrib/ ?
Any references to tutorials specifically for adding attributes for use with one's new module to existing product types for the newbs that want to help ... other than the existing module code?
Comment #12
gordon commentedWe have the API over at http://drupalecommerce.org/api which includes a couple of examples (a little incomplete) on how to develop the 2 types of gateways, (hosted and self hosted).
You can also checkout the paypal and authorize.net modules, http://drupalecommerce.org/api/file/ecommerce-5--4/paypal/paypal.module/54 and http://drupalecommerce.org/api/file/ecommerce-5--4/contrib/authorize_net....
Lastly you can always grab us on #drupal-ecommerce
Comment #13
brmassa commented