tomoharu
-
Posts
88 -
Joined
-
Last visited
Posts posted by tomoharu
-
-
It allows a customer to input CC info like on payment other forms, but you have to be able to then enter it manually into your merchant account's system. I don't like these because it allows too much room for error (if you type $1000 instead of $100 and the customer was using a debit card, plus you have to actually store the numbers somewhere, even if just in your store database, and that's rather insecure for the customer).
-
Thought this would fix itself once I got the newer version of CC in, but it still does this. Kind-of renders seller protection useless when there is no address.
Anyone have any ideas or am I the lucky one and This Only Happens To Me? I'll spin some straw into gold for you...or something like that.
-
You need a merchant account. However, and pointed out above, PayPal is a great one, very popular around the world and rather safe. Or, Google checkout is also good and is gaining popularity, but many, many people use PayPal rather than cards when shopping online, and it's been around for years. I'd strongly suggest this before getting a merchant account through a 3rd party or bank, since the fees can be very costly if you're not selling much to begin with. But since PP and Google's both accept credit cards, some small businesses stick with those.
Good luck! :)
-
check your path here: vhosts/presnet.co.uk/httpdocs/
-
nevermind: had to reinstall (twice) some of the 4.2.3 PPpro files and it works now.
-
We are evaluating CC4 and tried to install both our actual PayPal pro account and a SandBox demo account. Both result in a "Security header Not Valid" error when trying to complete a payment for a test purchase.
We disabled the "Enable card Validation" and tried all 3 Payment Action types.
We have the site on HostGator and have the shared SSL enabled.
Any help/suggestions would be appreciated.
Geoff
Get your own SSL, plus with a dedicated IP from your host, not shared. Many places offer them at low cost (like rapidssl.com).
-
I saw the fix for this problem for CC3: http://forums.cubecart.com/index.php?showtopic=16829 but am I alone in having this problem running V4? I used PPPro on a different cart prior to this month and all was fine with the addresses being carried over, but now, apparently when the customer uses a credit card, the address info is not carried into PayPal from the store. This wouldn't be such a big deal except that it makes printing PayPal shipping labels much easier and faster.
-
edited: nevermind, got it worked in
-
What php version is your host running? Is your SQL freespace limited (you should be able to check this in Cpanel or similar admin interface)? It does sound like an issue with your webhost, and perhaps for some reason they have (some?) SQL databases at low priority, or have changed settings.
(One of mine did that recently--completely shut down the site for days and they took half that time to even answer my support ticket. Problem was that they had inadvertantly downgraded the php version).
-
ya know the big reason people dont really trust reviews or testimonials anymore is because they can be edited, made up, tweaked etc etc...
Yeah, I can't really believe someone asked this. Fake reviews are usually so easy to spot, too. If you have good products, they sell themselves.
-
I just encountered this problem with my (active, running store) CC4 using PayPalPro. The gift certificates were a main selling point to me with this cart, as they were terribly screwy in OsCommerce. Now I see that it won't work with Cubecart and alt. checkouts. Is there any type of mod or fix for this? Thanks!
-
Hi I also get this same error message please can someone advise.
I get this error with Paypal pro
"The PayPal API has returned an error!
Ack:
Correlation ID:
Version:
Error Number:
Short Message:
Long Message: "
Many Thanks
I've installed CC, everything else works well, but get this same error, and I've used WPP with no problems (like this anyway) with other cart systems. Apparently Direct Payments work, but this rather blank message is what I get when clicking the express button. Anyone know how to work around this? Is it an API sig /cert issue? Thanks!
Is there an alternate Google checkout button?
in Technical Help
Posted
Best to check the Google checkout TOS first to make sure altering the button isn't a violation, but then can't you just edit the colours quite simply in any graphics editing program? Paint if that's all you have (which I hope it's not!).