Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
1–10 of 15 posts
Re: Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
#2WePay has had this for years, the title is a bit sensational.
Re: Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
#3WePay has had this for years, the title is a bit sensational.
So does Balanced Payments for Marketplaces[1]. Facilitating transactions is a huge pain point for businesses, so it's a big deal to see another company moving in to solve it.
Re: Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
#4Looking at Braintree's Marketplace docs, it appears you have to "onboard" each sub-merchant you want to send payouts to, which requires entering their name, address, date of birth, and their social security number. It then says "If [the social security number] is not provided, we will attempt to retrieve the full Social Security number based on the other applicant details."
So my question is: How is it possible / how do they retrieve someone's social security number using apparently just a name, address, and birth date? (Maybe I'm naive, but I thought socials were pretty secure)
Re: Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
#5So now there are 5 players in this space (that I know of).
Ordered by the launch date of their marketplace offering: WePay, Balanced Payments, Stripe, Paymill, Braintree.
Edit: Added WePay.
Re: Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
#6Looking at Braintree's Marketplace docs, it appears you have to "onboard" each sub-merchant you want to send payouts to, which requires entering their name, address, date of birth, and their social security number. It then says "If [the social security number] is not provided, we will attempt to retrieve the full Social Security number based on the other applicant details." So my question is: How is it possible / how…
Kristi from Braintree here. We work with one of the major credit bureaus to cross-reference the data provided to match it with a social security number.
Re: Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
#7Looking at Braintree's Marketplace docs, it appears you have to "onboard" each sub-merchant you want to send payouts to, which requires entering their name, address, date of birth, and their social security number. It then says "If [the social security number] is not provided, we will attempt to retrieve the full Social Security number based on the other applicant details." So my question is: How is it possible / how…
Kristi from Braintree here. We work with one of the major credit bureaus to cross-reference the data provided to match it with a social security number.
Ah, that makes sense, thanks!
Re: Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
#8So now there are 5 players in this space (that I know of). Ordered by the launch date of their marketplace offering: WePay, Balanced Payments, Stripe, Paymill, Braintree. Edit: Added WePay.
Elliott from WePay here - don't mean to turn these comments into a corporate stick-measuring contest, but our API has been able to support this use case since August of 2011.
Re: Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
#9So now there are 5 players in this space (that I know of). Ordered by the launch date of their marketplace offering: WePay, Balanced Payments, Stripe, Paymill, Braintree. Edit: Added WePay.
Elliott from WePay here - don't mean to turn these comments into a corporate stick-measuring contest, but our API has been able to support this use case since August of 2011.
Sorry Elliot I did not know that. I added WePay to the list.
Re: Braintree Takes On Stripe, PayPal With Debut Of “Marketplace”
#10Earlier quoted context omitted.
Elliott from WePay here - don't mean to turn these comments into a corporate stick-measuring contest, but our API has been able to support this use case since August of 2011.
Sorry Elliot I did not know that. I added WePay to the list.
Just to keep it historically accurate, PayPal's Adaptive Payments API supported marketplace use case since mid 2010.
Disclaimer: I used to work on it in my past life.