payment

Hello,

In my drupal ecommerce, i need to edit a invoice until its sent. Because i need to add the serial number of the product into the invoice for every product that customer buy.

Exist any module for do that or a way to add this function in the invoice module?

I think that is needed for the business that sell informatic products and others products that for garanties need a serial number.

Thanks for all.

Hello there!
I´ve recently installed ecommerce, and frankly I think it´s just too much for what I need. It seems far too complex. But as I need a good, solid, stable module that can manage recurring payments and scheduled reminders (and only that), using eC seemed the obvious thing to do. :)

We administrate online courses in a Drupal Platform, and the student´s payments are manually managed outside Drupal.
We have courses that can be paid in two or three (monthy) times.

Op dit moment ben ik voor een project de mogelijkheden aan het bekijken van e-commerce icm Drupal. Nu zijn er al diverse ontwikkelingen gaande qua e-commerce modules en enkele payment gateways. Voorbeelden hiervan zijn e-commerce module, Quickfile, Ubercart, ProtX Payment Gateway, La Caixa payment gateway, E-Commerce PayFlow Pro

Hello there!
I don´t know how to use a simple Billing platform for student´s payments, where student´s can pay using personal checks, cash at the school´s office, or credit cards.
When a student uses ie. cash to pay, you should be able to enter to his profile and write that down somewhere, or maybe after some time of not fullfilling that payment slot the student could get an email with a reminder.
The ecomm module is far more complete and server heavy than this.
How did you guys solve this issue?
Thanks for your opinions!!!
Rosamunda

Hello folks,

I have updated the Linkpoint API for the ecommerce module - for drupal 5.x. The module has been tested and I think up to Drupal's standards. I applied for a cvs account but was denied since the module already exist. AjK (I guess he manages the cvs accounts) wrote back and said to contact the maintainer, which the old 4.6 linkpoint_api.module has:

$Id: linkpoint_api.module,v 1.3 2005/10/12 04:06:07 mathias Exp $

Hope this is the right place to ask.

I have a drupal 4.7 payment module created for interwallet. I want to migrate it to Drupal 5 and contribute it back to the community.

I have the following questions:

1. Is there a difference between Drupal 4.7 and Drupal 5 payment API?
2. Is the module supposed to work as-is, after a standard Drupal 5 module migration process, or are there any other changes I need to make?
3. Where to put it when I contribute it? Should I put it under the 'contrib' subdirectory of the e-commerce package? Or should I make it a separate drupal module?

I've been muddling my way through my first Drupal/e-commerce project, and I've managed to get my large list down to just a small handful of questions. If anyone has some guidance for me on any of them, that would be great. just as some background, I'm quite familiar with e-commerce in general, having used osCommerce, ZenCart, Xcart, and others quite extensively, but I'm not wrapping my head around this one for some reason. I'm also a Drupal newbie, but not a CMS newbie. We're running E-commerce version 3, on Drupal 4.7.

Drupal E-Commerce module currently support for single currency only. This means all of your products can only base on a signle currency format, within DB, for customer browsing, for transaction, and also for accounting. This will be a trouble, if you hope to setup an auction system as like as eBay, or even simply hope to use Paypal module in where local currency is not support. The need of multiple currency supporting is clear.

By the way it is also a complex problem (from http://www.xencraft.com/resources/multi-currency.html) :

when redesigning the software to accommodate different or multiple currencies, the designer should be careful as to which aspects are determined either by user preference (which may in turn be indicated by locale), by regulation, by the nature of the application, or perhaps by other factors. The appropriate determining value(s) will need to be a part of the API.

Hi guys,

I recently updated the worldpay.module for 4.7 and included an automated "callback" after the order is processed...i.e. the worldpay server tells the drupal site that the transaction was either APPROVED or CANCELLED (Denied happens at the worldpay end and the order is cancelled).

So a Drupal site admin who is setting up their worldpay enabled shop, enters in the worldpay_callback the worldpay server sends the "y" or "c" flags to. The problem is securing that transfer of information or in other words, validating the source.