I'm developing a shopping cart system for a client using Joomla! 1.5 and VirtueMart and am in the market for a payment gateway provider. That said, I have a couple of unique requests:
Not PayPal -- The client sells tobacco accessories, which is against PayPal ToS.
Allows the sale of tobacco accessories/products -- my client primarily sells glass pipes and waterpipes for tobacco use only. If there's a chance a payment provider will classify these as "paraphernalia" or other things contravening their ToS, I'd prefer to avoid inquiring only to be told I can't use their service. This is why Google Checkout isn't an option, btw.
Good support for VirtueMart -- I've never really programmed a payment module before, so easy of integration with VirtueMart is important.
I'm waiting on a response from PsiGate, though I'm leaning towards Pivotal Payments given the client already uses that company for processing in-store transactions. That said, Pivotal seems to have pretty poor support for VirtueMart -- I can only find a forum post about their payment module, and it seems the people in that thread were having a really hard time implementing it.
Epic-level gratefulness for anyone with suggestions.
VM has very good support to Authorize.net. I have also recently implemented a Link Point (now called First Data) payment module. There is a really good step by step for the Link Point module that worked perfectly for me on VM 1.1.5 here - http://forum.virtuemart.net/index.php?topic=35263.msg107934#msg107934
Related
So I'm trying to implement a payment solution for my website and after quite a bit of research, I'm still lacking a complete solution. I'm running Laravel 5.0 and need general shopping cart payment functionality. I thought I would post this to try to create a reference to help others that may be having this issue. I got as far as getting test transactions into the Paypal sandbox and that's where the brick wall has seemed to come in, but a complete overview would be helpful. I’ll list my issues that I need to overcome in order to issues some run into.
Issues needing to be resolved to complete the payment solution implementation
My biggest issue with what I've seen has been receiving the
notification of successful payment processing back, but I'll walk
through what I've seen thus far. I'm not sure how to set up a listener or other methods of detecting a correct payment processing
Dealing with Credit Card information when I’m trying to avoid it
for the time being – I’d like that to be done on the gateway website
Potentially kicking off some of the calls to these APIs in Laravel
when the user checks out
I’m trying to move items to my server, but the development is being
done locally which creates an added issue
The options
There’s simply Paypal
I’ve taken the basic form implementation as far as getting payments into Paypal, but I can’t seem to get payments out. I’ve tried the returnURL and that doesn’t seem to work
I do not necessarily like this option because it seems to be leaving a lot of information in the form that would seem to be better kept private on the server
I’d like to use something complete on git but I seem to find the documentation incomplete
https://github.com/thephpleague/omnipay-paypal
--Not sure how to implement this in laravel
https://github.com/ignited/laravel-omnipay
--doesn’t appear to be being used
https://github.com/net-shell/laravel-paypal
https://github.com/anouarabdsslm/laravel-paypalpayment
--The card information is not intuitive here as that’s what going to
paypal’s supposed to manage
It would be nice to use Paypal express but I don’t see a ton of resources specifically for that.
There's Aimeos.
I don't necessarily feel safe with manually implementing the vsrf
protection and it doesn't seem to offer that much more on the payment
front than
I’m open to others that are complete and charge similar fees to Paypal
Stripe doesn’t work for me. I’m not doing a basic subscription
Any complete thoughts would be greatly appreciated as documentation left short has caused issues in this case. Thanks!
This PayPal PHP SDK will make all of the PayPal classic API calls very quick and easy for you. It's available on Packagist/Composer and can be applied to Laravel very easily.
It supports Express Checkout, Payments Pro, Invoicing, Transaction Search, Transaction Details, Refunds, etc.
This is done in Laravel 4, but I had begun this "PayPal Glass" project a while back to show how the class library / sdk can essentially replicate everything you can do within a PayPal account. Here it is running on my local test server.
So yeah, that SDK should be able to handle everything you need to do with PayPal inside a Laravel project.
I'm working on a Magento marketplace where the client would like to use paypal delayed chain as payment method. Here Client will hold the vendors payment for 15 days and then execute payments. The scenario is Client don't want to hold payments for highly credible vendors. He wants to pay them right away. But in delayed chain, we can't execute payments based on vendors. When the time comes to pay vendors, all vendors will be paid at once based on transaction id or pay-key which used to create payment.
I need to implement this scenario in Magento. Does anyone have solution on this potential issue?
After digging deep about this issue, I found that paypal doesn't support what I asked from their API or the API is still isn't matured to accommodate the need. So we went with another solution to overcome this problem. Solution is not efficient but it's the only working solution as of now.
We have to go with checkout by vendor, so that we can execute payment based on vendor since each order is associated with a vendor.
I am planning to list a Gmail Contextual Gadget on Google Apps Marketplace. More than a year ago I created a vendor profile and a listing (so I am familiar with those steps), but I never made the gadget commercial. Now I'm ready for setting up the gadget for sale but I am wondering about the billing is implemented. As I've read in the Marketplace billing documentation, Google does not provide any solution for this, but recommends that I implement it myself or use a third-party billing product.
So my questions are:
- Which are the basic steps to create a billing solution for your listing?
- Is there any way keep the payment "manual", in that sense that I enable the product for installation manually (with a token etc) for a customer when the payment is received?
- How long time do I have to estimate for this?
Really appreciate an answer!
You need to use the Licensing api
https://developers.google.com/google-apps/marketplace/licensing
I have a magento installed and ready to go, the only thing is I cant do a actuall transaction and get the money from my bank. any help would be appreciate.
You need to get a merchant account. There are numerous providers of these, but be very careful, the legal and financial pitfalls are as numerous as the providers.
You will probably find some interesting reading on sites like Merchant Maverick: http://www.merchantmaverick.com, their discussion of "Liquidated Damages" should be required reading for all online merchants.
Peter's answer is required reading, but if you'd like to get started quickly Paypal is built in and offers a great integration into Magento. This should help you get started (of course you'll need to sign up for a Paypal account and link it to your bank): http://www.magentocommerce.com/knowledge-base/entry/setting-up-paypal-for-your-magento-store/
The next big topic in my new start-up company is recurring billing inside Magento. We will have a few recurring products we'd like to offer alongside some standard one-time products. I've researched the best gateways and so far we think either ARB or CIM from Authorize.net is the way to go.
Some questions come up though such as:
If Authorize.net is going to handle the recurring aspect, what is the point of Magento's built-in recurring profiles system? As far as I can tell it's to integrate with the 3rd party by actually taking the user to the 3rd party site? Using Authorize.net would eliminate the need for recurring profiles right?
Are we limited to purchasing one of two or three $300 modules out there to get started with ARB or CIM? So far Magento only supports SIM or DPM. Or do I have to sit down and extend the built-in Authorize.net payment method? Basically I am trying to say we are on a start-up budget and $300 is a killer at this moment.
If we went with ARB over CIM that means if a customer came back to purchase a second item later on that they would have to re-enter their information (CC #, exp. date, etc.) whereas CIM would have this ready to go...is that the correct explanation?
We need the flexibility to create unique payment schedules during checkout. For example: We will sell a custom website and hosting package. We want to charge the user 50% of the website cost upfront and 50% upon completion and setup a recurring payment for the hosting package all at time of checkout.
Along with question #4, currently Magento's recurring profiles limit nominal items to be purchased separately than regular products. This is not acceptable for us and a customer must be able to purchase all wanted items together in one checkout page.
Sorry for this lengthy post but I'm very curious to see what our options might be given all we want/need to do. Any advise is good advice!
The Magento recurring billing code allows customers to view and edit their subscription inside the Magento webstore, so there's no redirection to third party.
Short answer: yes, or roll your own.
I believe that is the case, but you need to check with Authorize.Net on that.
Not sure what the question is here?
Then refer to your earlier question on this topic that I answered. You can choose to override the core functionality, but you need to familiarize yourself with the reasons why Magento chose to enforce that restriction. I believe that is likely due to a restriction in the Paypal interface, and other recurring billing gateways such as Authorize.Net may be able to cope with one-off and recurring items in the same transaction.
HTH,
JD