3 ms·

Look at BrainTree and Balanced Payments. We use BrainTree at http://nextproof.com http://nextproof.com to process payments and then ACH funds to our customers a

Look at BrainTree and Balanced Payments. We use BrainTree at http://nextproof.com http://nextproof.com to process payments and then ACH funds to our customers a few days later. It works great but you will need to contact them. Also, be aware you are likely violating Stripe's terms of service (see section 12). You are doing what is called 3rd party payment aggregation. It has higher risks and usually requires special permission. Stripe would probably prefer you use Stripe Connect so payments go to your users' accounts (but you can still levy a fee so it may fit your needs).

rush-tea 13y ago
Thank you for your response. What confused me is why one payment processor (Stripe) would not allow it while others (in your example, BrainTree) is OK with it. My question is that if this 3rd party aggregation policy is just custom made for each payment gateway (means they make their own policy), or is it legally bound by the US law? I want to make sure that I do not break any laws here. Thank you for your input. PS: also I notice some marketplaces like zaarly or airbnb has some kind of insurance for protection / safety while other marketplaces do not. If I want to offer insurance or some kind of protection, how should I start? I tried to find information on google, but probably due to my limited knowledge on this area, I do not find information that is relevant. Thanks.
- callmeed 13y ago
  Stripe is about simplicity (for developers) and being fairly standardized and automated. Payment aggregation has higher risks and Stripe probably doesn't want to deal with them at this point. BrainTree, if you contact them directly, can work with various merchant accounts. We had to get special permission to do payment aggregation. Also, our underwriting merchant held a % of our funds in escrow for the first 12 months of our operation. The main issue with payment aggregation is increased fraud. We had to deal with it and you will too if you get any sort of traction. What happens is people will make fake seller accounts and then make purchases through those accounts using stolen credit cards. Once you ACH those funds to them, guess who is on the hook for chargebacks? If you said "I am", you are correct. In 2011, we lost a good amount of money (five figures) in a 3-month span. Also, if your chargeback rate is too high (> 1%), you will likely get a warning from your merchant processor and possibly get booted. FYI, there is a YC company helping people deal with some of these issues: https://siftscience.com https://siftscience.com Using something like Sift Science or simply manually reviewing and approving accounts is the best way to go initially. To answer your other question, I don't think there are US laws regulating payment aggregation (yes). I don't think the new money transmitter laws apply here, but I could be wrong.

rush-tea 13y ago

Thank you for your response. What confused me is why one payment processor (Stripe) would not allow it while others (in your example, BrainTree) is OK with it. My question is that if this 3rd party aggregation policy is just custom made for each payment gateway (means they make their own policy), or is it legally bound by the US law? I want to make sure that I do not break any laws here. Thank you for your input. PS: also I notice some marketplaces like zaarly or airbnb has some kind of insurance for protection / safety while other marketplaces do not. If I want to offer insurance or some kind of protection, how should I start? I tried to find information on google, but probably due to my limited knowledge on this area, I do not find information that is relevant. Thanks.

callmeed 13y ago
Stripe is about simplicity (for developers) and being fairly standardized and automated. Payment aggregation has higher risks and Stripe probably doesn't want to deal with them at this point. BrainTree, if you contact them directly, can work with various merchant accounts. We had to get special permission to do payment aggregation. Also, our underwriting merchant held a % of our funds in escrow for the first 12 months of our operation. The main issue with payment aggregation is increased fraud. We had to deal with it and you will too if you get any sort of traction. What happens is people will make fake seller accounts and then make purchases through those accounts using stolen credit cards. Once you ACH those funds to them, guess who is on the hook for chargebacks? If you said "I am", you are correct. In 2011, we lost a good amount of money (five figures) in a 3-month span. Also, if your chargeback rate is too high (> 1%), you will likely get a warning from your merchant processor and possibly get booted. FYI, there is a YC company helping people deal with some of these issues: https://siftscience.com https://siftscience.com Using something like Sift Science or simply manually reviewing and approving accounts is the best way to go initially. To answer your other question, I don't think there are US laws regulating payment aggregation (yes). I don't think the new money transmitter laws apply here, but I could be wrong.