More then one payment option for buyer

How do I add more then one payment option for the buyer on checkout?

I want to offer Paypal and my credit card merchant account (authorize.net)

Thanks!!

anyone know how to do this?

See this thread:
showthread.php?t=4879

It's a holiday weekend in the US.

I am just getting into this myself. Remote or local processing? From what I have read, if you want to process credit cards with Authorize.net and simply offer an option for clients with a PayPal account you can add a PayPal Express option with either local or remote processing with Authorize.Net as the primary gateway/processor, when you run the eCart Wizard.

Again, from my reading PayPal Pro (local) and PayPal Standard (remote) now allow a user to pay by credit care with an option to get a PayPal account at the end. But they don't need one. The PaPay Express will only allow a customer to pay with a PayPal account.

You will find more information in the eCart Help Documentation. However, the document is base on setting up with a local payment process. Personally, I have made a flow chart to help me follow the process. It is invalueable. The support team will be back on Monday and can help you better than I can. All the best. - Kevin

Thanks,

I figured it out, but have another issue

Originally Said By: Kevin373660

  Personally, I have made a flow chart to help me follow the process. It is invalueable. - Kevin  

Hey Kevin,

Would you like to add your flow cart to the collection?

WebAssist Extension Flowchart
204/

Sure, but it is not complete yet. I have not finished working hands-on with the final part of the payment confirmation process. It is just hand done while I am correcting, adding and modifiying it. When finished, I could send it to someone at WebAssist and they can correct and clean it up for the benifit everyone. It could be inhansed with flows for local/remote and optons that would be relavent depending on the compatible choice of gateway.

What I do with the knowledgebase is put articles describing procedures that have helped someone else. When more information becomes available it is added. If someone sees a flaw, I change it. Since this is not an official WA endeavor, it has the advantage of being a living document over a completely tested, ready for official publication type document.

The flowchart that's up there now is far from complete but I haven't had any complaints or suggestions. It's just an overview of how I understand things to work. The goal is just to help people get a head start on projects by using what others have learned in the past.

Incomplete is better than non-existent. :)

I can fancy-it-up. Others can add their insight as well. That's the benefit of making it a community project.