41–50 of 86 posts
The part that I find really offensive is - they're still taking new account signups, with zero support for those users.
Earlier quoted context omitted.
Braintree is pretty great, I like working with their API and customer service (always ready and willing to talk on the phone, which is great). Avoid Authorize.Net like the plague. Horrifically bad XML API that will make you want to claw your eyes out.
Where is there XML in Authorize.Net's API? Here's how you charge a card using the AIM (Advanced Integration Method) interface (Perl sample code): my $post_values = { "x_login" => "API_LOGIN_ID", "x_tran_key" => "TRANSACTION_KEY", "x_version" => "3.1", "x_delim_data" => "TRUE", "x_delim_char" => "|", "x_relay_response" => "FALSE", "x_type" => "AUTH_CAPTURE", "x_method" => "CC", "x_card_num" => "4111111111111111", "x_e…
http://www.authorize.net/support/AIM_guide_XML.pdf
We also used XML through their CIM to manage customer profiles. To be fair, this was all in PHP, and the code was inherited so I'm not sure if there was a better way to deal with Auth.net's API.
I do know that their dashboards were thoroughly unpleasant to deal with and I felt the API was obtuse in many different locations.
Earlier quoted context omitted.
What are you talking about? FeeFighters is a Samurai project. And Groupon bought them out.
FeeFighters didn't build Samurai. As I understand it, they acquired the team/project who did.
Integrating the acquisition of a small company into a large company is hard. I suspect there are very few acquisitions where customers do not experience at least some pain. I am deeply sorry for customers who have had support tickets get dropped or experienced slow responses during this period of integration. We are working to smooth things out.
When we got bought, in addition to some personal stuff, like moving across the country (most of our team moved to Palo Alto, so we could all be together instead of distributed), we had to very quickly build additional functionality and scalability into our product to support the ambitious goals that Groupon has for our technology. Since we have been more focused on development and since Marc and Stella, who were doing a lot of our customer service, did not come along with the acquisition, our customer service has suffered.
It is really uncool how quickly other startups are to snipe at each other. We started a business, pivoted, built something valuable, sold it at a profit, and are now in an amazing position to solve the customer problems we initially set out to solve. If that resulted in you having a bad customer experience, it is perfectly reasonable to complain about it, and we are listening and working to fix it. But (Fred from Fleapay) why would you insult us by saying that we didn't build our product (we did)? And what do you know about why Groupon bought us? And what does Ayn Rand have to do with this anyway?
As always, if you are a customer and you want to talk, I am at sean@feefighters.
Earlier quoted context omitted.
Where is there XML in Authorize.Net's API? Here's how you charge a card using the AIM (Advanced Integration Method) interface (Perl sample code): my $post_values = { "x_login" => "API_LOGIN_ID", "x_tran_key" => "TRANSACTION_KEY", "x_version" => "3.1", "x_delim_data" => "TRUE", "x_delim_char" => "|", "x_relay_response" => "FALSE", "x_type" => "AUTH_CAPTURE", "x_method" => "CC", "x_card_num" => "4111111111111111", "x_e…
I don't have the code handy (was client work for a third party), but we definitely used XML through Auth.net's AIM. Here are the API docs for it: http://www.authorize.net/support/AIM_guide_XML.pdf We also used XML through their CIM to manage customer profiles. To be fair, this was all in PHP, and the code was inherited so I'm not sure if there was a better way to deal with Auth.net's API. I do know that their dashboa…
That's the one we use. I didn't even know they had an XML option--and now I'm going to try to forget it! :-)
Hello everyone -- this has been an interesting and painful conversation to watch. I am Sean, co-founder of FeeFighters. Integrating the acquisition of a small company into a large company is hard. I suspect there are very few acquisitions where customers do not experience at least some pain. I am deeply sorry for customers who have had support tickets get dropped or experienced slow responses during this period of in…
Earlier quoted context omitted.
Braintree is pretty great, I like working with their API and customer service (always ready and willing to talk on the phone, which is great). Avoid Authorize.Net like the plague. Horrifically bad XML API that will make you want to claw your eyes out.
Where is there XML in Authorize.Net's API? Here's how you charge a card using the AIM (Advanced Integration Method) interface (Perl sample code): my $post_values = { "x_login" => "API_LOGIN_ID", "x_tran_key" => "TRANSACTION_KEY", "x_version" => "3.1", "x_delim_data" => "TRUE", "x_delim_char" => "|", "x_relay_response" => "FALSE", "x_type" => "AUTH_CAPTURE", "x_method" => "CC", "x_card_num" => "4111111111111111", "x_e…
Hello everyone -- this has been an interesting and painful conversation to watch. I am Sean, co-founder of FeeFighters. Integrating the acquisition of a small company into a large company is hard. I suspect there are very few acquisitions where customers do not experience at least some pain. I am deeply sorry for customers who have had support tickets get dropped or experienced slow responses during this period of in…
I just discovered that FeeFighters got acquired due to this post. I'm so disappointed. This product does not belong at Groupon. We've been emailing Sean recently to ask him about Samurai and I guess this explains the no response. I really loved what he was doing and sung the FeeFighters praises from the mountaintops whenever I could. I really wish that product had stuck around. All the info that they were producing o…
I had a great experience with Sean and FeeFighters before they were acquired. I can understand being in a crowded market and eyeing the exit. It could certainly be handled more gracefully. GroupOn should either support the product, or at the very least support people trying to migrate their data away. That's the really frustrating part of this. I lucked out to have this come to a head early on, with only 25 cards vau…
I'm stuck with a merchant account provider I detest, that's raised my rates just about every month for 3 years, because there's no way to get my customers' info back out of the payment gateway. It's either keep wasting money on rates nowhere near what I initially agreed to, with lousy support, or lose even more money by asking every customer to re-enter their billing info. Just a few percent deciding to ignore the mail and let their subscriptions lapse would be more costly than the fees.
These days, in the US at least, there's affordable options for both payment info vaults that can connect to multiple gateways, or gateways offered by merchant companies that will give you your data if you decide to leave them. A few years ago, that wasn't really the case.