By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,746 Members | 1,928 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,746 IT Pros & Developers. It's quick & easy.

PayFlow Pro...No support

P: n/a


--
I have a problem that I am hoping someone can help me with. I am trying
to design a custom shopping cart for a friend. He wants it designed a
specific way so an integrated cart won't work for his purposes. No problem
there. We have a VeriSign/PayFlow Pro account with an SSL cert, however the
hosting company which we are using did not compile PHP with the --with-pfpro
extension and claim that they can not recompile as it is a shared server.
Is there a way to "real time" proccess credit cards working around this
limitation? I have been looking through the docs (that are available) from
VeriSign for the SDK, but can't seem to make sense of the perl sources (Perl
is not my strong point.)
Any help would be GREATLY appreciated! Thank you!

si***@charter.net

Jul 16 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
John Siefer wrote:
I have a problem that I am hoping someone can help me with. I am trying
to design a custom shopping cart for a friend. He wants it designed a
specific way so an integrated cart won't work for his purposes. No problem
there. We have a VeriSign/PayFlow Pro account with an SSL cert, however the
hosting company which we are using did not compile PHP with the --with-pfpro
extension and claim that they can not recompile as it is a shared server.
Is there a way to "real time" proccess credit cards working around this
limitation? I have been looking through the docs (that are available) from
VeriSign for the SDK, but can't seem to make sense of the perl sources (Perl
is not my strong point.)


Unless the site is going to be getting more than 500 transactions a
month, I'd go with the PayFlow Link instead. That way all the processing
is actually done on the verisign server so you don't need the pfpro
support compiled into PHP.

I haven't used it before, but the dl() function can load a PHP extension
at runtime. It may be possible that would work for the pfpro extension:

http://www.php.net/manual/en/function.dl.php

--
Justin Koivisto - sp**@koivi.com
PHP POSTERS: Please use comp.lang.php for PHP related questions,
alt.php* groups are not recommended.

Jul 16 '05 #2

P: n/a
OK, I think I am now officially going nuts!
I tried to dl(pfpro.so) (along with the usual extension checks) and it
says the module doesn't exist. I talked to VeriSign and they said that the
payFlow Link option is not available on our server (it is a shared server).
Interland (our server) has told me "You can put a php.ini file in the /html
folder, but can not add any modules that were not installed in the first
place." (duh)
I know that in its VERY basic form, getting the code returned from
VeriSign is a matter of sending user information along with login info to a
program on VeriSign, but it seems that everyone is coming up with blank
stares on their faces. (Interland has all but told me that it can't be done
unless I use the Miva cart that comes on the server...Have to love that..But
I don't believe that for a minute!)
Any other suggestions out there? Help save a man's sanity! lol
Thanks a ton!

--
John Siefer

"Justin Koivisto" <sp**@koivi.com> wrote in message
news:5I*****************@news7.onvoy.net...
John Siefer wrote:
I have a problem that I am hoping someone can help me with. I am trying to design a custom shopping cart for a friend. He wants it designed a
specific way so an integrated cart won't work for his purposes. No problem there. We have a VeriSign/PayFlow Pro account with an SSL cert, however the hosting company which we are using did not compile PHP with the --with-pfpro extension and claim that they can not recompile as it is a shared server. Is there a way to "real time" proccess credit cards working around this
limitation? I have been looking through the docs (that are available) from VeriSign for the SDK, but can't seem to make sense of the perl sources (Perl is not my strong point.)


Unless the site is going to be getting more than 500 transactions a
month, I'd go with the PayFlow Link instead. That way all the processing
is actually done on the verisign server so you don't need the pfpro
support compiled into PHP.

I haven't used it before, but the dl() function can load a PHP extension
at runtime. It may be possible that would work for the pfpro extension:

http://www.php.net/manual/en/function.dl.php

--
Justin Koivisto - sp**@koivi.com
PHP POSTERS: Please use comp.lang.php for PHP related questions,
alt.php* groups are not recommended.

Jul 16 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.