DotNetInvoice Forums

We have hosted a site on discountasp.net. I am new to ecommerce side of programming, so pardon my ignorance.

 This is what we plan to do:
Customer signs up and he is going to post a listing (for sale). We will charge him for 2 months minimum first time. (we will have other options for different durations). So lets say he selects 2 months, he will be billed say $50. This page (similar to shopping in Register.com will be developed by us).

When the client oks the page, we need to authorize payment, generate an invoice on the fly programmatically and email the invoice to the customer too. At this point, we need to set a reminder for say 45 days for this customer. We email a reminder to customer saying his listing will expire by a certain date. If he chooses to extend, he clicks a link to login and he will be taken to the same shopping cart page as before and extends his listing period for which he is invoiced after authorizing payment.

I am sure we can do this with better with your software but wanted to make sure. Couple of questions I have are:

Can we send 2 reminders..say after 45 days past the invoice date and then 7 days past this date. (I want two reminders before 2 months or before the expiring of the listing period)

We have asp.net memberships with other details in another custom table. Can we integrate these tables with your software to maintain customer details like Credit Card Details?

Can I use another payment component along with your software (we plan to use Authorize.net) or should I use your payment component only?

 Will your software suit my needs as I have explained. It is sort of recurring billing but initiated by the user and not automatic.

 Thanks

Jags

Jags,

1. Yes, you can send 2 reminders. You can send unlimited reminders if I'm not mistaken.

2. Yes, DNI uses the ASP.NET membership provider so if you already have a DB with that information it will integrate for login. Pulling credit card information may be a little more challenging, but that info is designated in the web.config so it should not be too difficult.

3. We have built in Authorize.NET support in the application. If you want to use a different component it's easy enough - you just have to plug it into the architecture.

4. DNI is an invoicing system. As long as you create the page where the client can sign up and post his listing, you can pretty easily create a recurring invoice using existing stored procedures. The one thing we don't have is a "recur until this date" feature for our invoices.

Let me know if you have any other questions,