talking to a port, and server daemon: partly OT

I have to hook up a credit card processor (SERVEBASE) for a website (perl).

The way servebase works is that you send them name data pairs, either
on the query string or using POST to their website script.

SERVEBASE sends back XML on the *same* port. Parsing the XML doesn't
bother me, talking back and forth on the port does.

It looks me that sending the request is not difficult, should I
probably use:

IO::Socket::INET; and tcp instead of udp

Now for the more OT stuff:

How do I setup a daemon to dump this back to the database? This will
be on a linux box and probably later a FreeBSD. Some flavor of Apache, I
would think.

What port should I use?

Cheers,
Jeff

Re: talking to a port, and server daemon: partly OT

Jeff Thies wrote:
> I have to hook up a credit card processor...
> How do I setup a daemon to dump this back to the database?

Your customers will be entrusting you with their credit card data.
They will be expecting that the transaction will be done in a
competent, responsible and professional manner.

Do you have absolute confidence in your programming ability to
guarantee that there will not be any breaches of confidentiality
in this process? The news is full of stories where credit card
numbers were exposed to the world due to amateur programming.

If you are serious about this business, you should obtain the
services of a commercial credit card processing service.

-Joe

Re: talking to a port, and server daemon: partly OT

"Jeff Thies" wrote in message
news:rDCJe.4937$ns.1575@newsread1.news.atl.earthlink.net...
>I have to hook up a credit card processor (SERVEBASE) for a website (perl).
>
> The way servebase works is that you send them name data pairs, either on
> the query string or using POST to their website script.
>
> SERVEBASE sends back XML on the *same* port. Parsing the XML doesn't
> bother me, talking back and forth on the port does.

What do you mean by "same port"? Do you mean the same connection (as all
HTTP connections work) or the remote server initiates a connection back to
you (in a similar fashion to non-passive FTP).

Re: talking to a port, and server daemon: partly OT

Tintin wrote:
> "Jeff Thies" wrote in message
> news:rDCJe.4937$ns.1575@newsread1.news.atl.earthlink.net...
>
>>I have to hook up a credit card processor (SERVEBASE) for a website (perl).
>>
>> The way servebase works is that you send them name data pairs, either on
>>the query string or using POST to their website script.
>>
>> SERVEBASE sends back XML on the *same* port. Parsing the XML doesn't
>>bother me, talking back and forth on the port does.
>
>
> What do you mean by "same port"? Do you mean the same connection (as all
> HTTP connections work) or the remote server initiates a connection back to
> you (in a similar fashion to non-passive FTP).

I've done a number of CC processor hookups and usually they need an http
path to talk back to you. I asked them about this path and they said,
it's not the path but the port. That and I've read through their 50 page
manual (no example scripts) and nowhere does it mention HTTP1.1 as you
would with a persistant connection.

I'm a little flumoxed! My integration manager is on vacation.

Cheers,
Jeff

>
>
>