Any Payment Modules That Take Payments Internally?

[taktikz]

It seems that PayPal and Google Checkout both have to redirect to their own pages and then back to my site once payment is made. Is there any payment module that doesn't take the visitor to an external page?

[bellini13]

i believe paypal has this ability, to accept payments your website directly, its called website pro i think. it costs $30 a month. i am not sure if google allows you to do this, you really need to check with google and paypal to see how this works.

 

otherwise you will need to find a merchant account for accepting credit card payments, and then purchase or use a payment module for that merchant. you can start by looking at authorize.net

[tomerg3]

There are many US payment gateways that support that, and have PS modules with that option.

 

A few are Authorize.net, FirstData, USAePay, you can find payment modules for them on our site at http://www.presto-changeo.com/en/8-payment-modules

[ScubaLessonsInc]

I used something called off line credit card module where by it temporarily captures the cc data, then I use mail alerts to notify me there is an order, I immeidately grab the data and change the status which deletes the data to keep it secure.. then I use the "Square.com" or "SquareUP.com" app to process the cc payments. Online the charges are only 4% if I have the card in hand the charges are only 2.9% and I have the funds in my account next day. I highly reccomend it.

 

Here is the offline cc module link: http://www.prestashop.com/forums/topic/58273-module-offline-credit-card-payment-v401production/

 

Here is the square link:

https://squareup.com/

 

what I like about this is the great software on my phone and I can use it to accept cc's at trade shows or onsite to upgrade scuba lessons.. or upgrades to add videos or picture packages for tourist divers.. great for impulse buying

[MacSnood]

Keep in mind that if you take payments on your own site instead of transferring the payment operation to a third party site, then you are responsible for seeing that your site, your payment application, and the physical environment it is hosted in, is compliant with PCI-DSS (the Payment Card Industry Digital Security Standard), meaning you must use a vendor approved by PCI Council (ASV - Approved Scanning Vendor) to scan your web site at least once every quarter for vulnerabilities, and each year you must audit your web site and fill out the Self-Assessment Questionnaire (SAQ).  Otherwise you may not legally take credit cards.

 

If you outsource credit card processing, you are still responsible for your site's PCI compliance, but your PCI questionnaire is 13 questions long.  

 

If you host your own payment application, and if that application ever electronically stores the cardholder data (such as allowing customers to register a card for future use, or keeping the card data in case a refund is necessary) your questionnaire is 200 questions long.

 

It is a really bad idea, even for someone who has some programming knowledge, to try to write a homegrown credit card payment application unless they are experienced in writing PCI compliant, high-security applications.  It opens up a ton of liability for the merchant.

 

PCI compliance is required by *every* merchant who takes credit cards, no matter how small the business is, and most small businesses find it is much cheaper and easier simply to outsource the payment process.