Thanks for your input Norman - your rationale to not to give away details on the client end is spot on.
On Tue, Nov 19, 2013 at 8:50 AM, Norman Franke <nor...@myasd.com> wrote: > I've implemented two payment gateways that have a SOAP interface. I tend > to prefer that since the UI looks like the rest of my web site. And it's > trivial. I typically do basic verification myself and then pass the rest > off to the gateway APIs. > > You can get better rates and faster payment via other solutions, BTW. We > take electronic checks and get the money same day, for example. CCs are > next day. > > I also don't like any details of what processor I use available to > clients. In my case, it's 100% server-based. All the users see is a > Tapestry application and Tapestry form. > > Norman Franke > Answering Service for Directors, Inc. > www.myasd.com > > > > On Nov 18, 2013, at 4:11 PM, Chris Mylonas <ch...@opencsta.org> wrote: > > > Mood Gorning Tapestry Users, > > > > What is the consensus on e-commerce stuff? I'm currently looking at a > > couple of payment gateways to integrate with > > > > 1) Eway > > 2) Braintree > > > > The spark framework braintree uses has also made me curious for further > > development/integration with tapestry. > > > > > > Any comments are appreciated. > > > > Cheers > > Chris > >
