Telephony Payment Gateway (was [ot] Phone/Altigen/API/Yada yada...)

Re: Telephony Payment Gateway (was [ot] Phone/Altigen/API/Yada yada...)

From:

Date:

Time:

I'd be interested in that as well.

Mark Plemmons
Station One Technologies, Inc.
WebRise
mark@webrise.net

----- Original Message -----
From: "Aaron Lynch" <a.list@ninewire.com>
To: "optigold list" <isp-list@optigold.com>
Sent: Thursday, May 02, 2002 12:33 AM
Subject: Re: Telephony Payment Gateway (was [Optigold ISP] [ot]
Phone/Altigen/API/Yada yada...)

> Wow. This sounds super cool.
>
> Please let me know (on or off-list) what the total cost would be for a
basic
> altigen system (2-5 seats) and ballpark this development cost...
>
> And, can you lease the system or are there payment plans available?
>
>
>
> On 5/1/02 5:18 PM, Drew Mouton mashed the following keys :
>
> > Okay, the juices are flowing now <g>.
> >
> > We've already done enough work that I *think* it would it pretty
straight
> > forward to build a ContractValidator and a PaymentGateway - which would
> > interface with OptiGold to take one time payments while-you-wait, or
> > update payment info - without too much trouble.
> >
> > Is there enough interest? Folks - if you could let customers make
> > payments on the phone, and/or pre-screen them for validity of support
> > contracts, would you be willing to pay for that product? If there's
> > enough interest, we'd sell it to the initial adopters in the OptiGold
> > community for the development time cost. ('Course you'd also have to buy
> > at least a basic Altigen phone system, but we can even discount that).
> >
> >
> > It appears that on 5/1/2002 3:38 PM, Shawn Hogan at
> > shawn@digitalpoint.com said:
> >
> >>> Shawn, if you're actually interested, our core CTI 'product' we've
> >>> developed over the past couple years is a CTI library linking
AltigenAPI
> >>> to SQL DBs...so we may be able to collab, if there's an interest or a
> >>> need.
> >>
> >> I'll probably pick your brain a bit sometime in the future to see how
> >> flexible the API is... But if you are hooking it into a SQL database,
it
> >
> > Short answer: the API is *not* flexible, but we've already done the
heavy
> > lifting in our CTI library to make it possible to get into and out of
DBs
> > without too much trouble. (It only took two years to make it work...)
> >
> >> would probably work for what I want... Like enter your support contract
> >> number. If it's valid (against a database) transfer them to the
correct
> >> extension. If it's not valid or expired, give them the opportunity to
> >> purchase a support contract via a credit card right there by punching
it in.
> >> That would be ideal... :-)
> >
> > Can do: we already have some stuff that works that way.
> >>
> >> And of course if I ever get around to implementing something like that
> >> internally, I could carry some of that over to Optigold... Like
customers
> >> could make a one-time credit card payment by punching it into the phone
or
> >> something.
> >
> > We'd want to write a payment gateway that was sufficiently generic to be
> > applied to other DB sources as well...but we'd make it 'specially
> > tailored to OptiGold. <g>
> >
> > Drew
> >
> > ---------------------------------------------------
> > To subscribe, unsubscribe or to search list archive
> > please visit http://www.optigold.com/lists/isp.html
> > ---------------------------------------------------
>
>
> ---------------------------------------------------
> To subscribe, unsubscribe or to search list archive
> please visit http://www.optigold.com/lists/isp.html
> ---------------------------------------------------
>
>

---------------------------------------------------
To subscribe, unsubscribe or to search list archive
please visit http://www.optigold.com/lists/isp.html
---------------------------------------------------

Sales:
888/4-DPOINT

Support:
858/452-3696