-
Notifications
You must be signed in to change notification settings - Fork 308
look into WePay #69
Comments
I got a phone call from a sales rep. He was on the merchant side and not the "API side," but said he'd pass me along to them. |
Haven't heard back from these folks, and now we're live with Balanced (#78). Closing. |
After a lot of analysis and consideration, I used WePay for my company which really depends on the marketplace feature. I think you should have spent more time on this, we've been really happy with them. One feature they have over the competition is refunds that credit all fees to both parties. Despite you getting lost with their sales people, their engineering team has been very responsive to us. For example, their google analytics integration was something I suggested to them and they turned around and implemented it within a short amount of time. |
Hi All, I am the lead developer for the API at WePay. Thanks for inviting WePay to the discussion. I'll try to keep this high level and if folks have follow up questions, I'll respond accordingly. Here are a couple of advantages of using the WePay API
We deal with many large crowdfunding platforms and we work with them every day to improve fraud detection and customer support. We typically encourage platforms to add us as an option and A/B test us against their other payment options. Ultimately, you should use the payments processor that has the highest conversion rates, and supports your customers the best. Please let me know if there are any specific questions you have or if there is anything at all we can help with! Thanks! |
Sweet! Welcome aboard @LeBlanc. |
WePay is nice, but AFAICT they don't let us handle all user interactions, and since they don't seem to have full i18n it'd be a step backwards in terms of UX. |
@Changaco It is the difference between WePay Connect and WePay Clear. With Clear, you assume a lot more of the PCI compliance. That is why they offer two 'versions' of the service. In my experience using the Connect version for about 4 years now, it hasn't been an issue on the customer end. If there is i18n languages that they don't support, it is worth talking with WePay about getting translations for them. They have always been responsive to me about these things. |
|
|
Obviously I had looked at WePay Clear, and as I said it doesn't let us handle all user interactions. I don't see evidence that WePay has any i18n, and if they don't have the underlying architecture it could take a while for them to implement it. Finally, WePay is still US-only for payouts. |
I saw that they have a Canada beta, but certainly they don't have the reach of Stripe or Braintree. |
Somehow missed WePay when switching away from Samurai (#58). Here's their marketplace use case.
The text was updated successfully, but these errors were encountered: