I was wondering if someone knew of a way to theoretically have one eCommerce store to act as a medium where sellers can sign up and sell goods and use their PayPal account to receive payments instead?
So, Vendor A signs up, stores their PayPal information. Whenever a customer purchases items form Vendor A, the money goes straight to Vendor A's PayPal account rather than the eCommerce store acting as a middleman and later has to payout all the vendors.
Sounds possible to me, as long as you have the vendor's paypal information, however that would make your data a security risk, because you would have to store the paypal information for multiple vendors.
Related
I want to create a platform where I have 2 kinds of users, Seller and Buyer.
Let's imagine that the Seller is selling a $10 product and I need get 10% of the value to me. Which is the correct way to do that transaction? The buyer need to pay to my account and I transfer the money to the seller after that? How can I do that transaction in a secure way for me and my customers? I need use gateways like Stripe or Paypal for that?
How the majority of platforms pay me with only my bank data? In platforms like Amazon, Shpfy... I think they don't have a person that do manual transfers every day for each seller.
You need Stripe Connect that allows you to work with merchants and payout them. Let me know, if you have a question with Stripe and Stripe Connect.
How shall I integrate custom shopping cart app with PayPal to accept indirect credit card payments without forcing buyers to register at PayPal?
There's a custom shopping cart web application and the task has been set to replace current credit/dept card payment with PayPal. The goal is to let the customers pay with their cards via PayPal. However, there are some constrains:
customers should enter their credit cards details (number, expiry date, secure code) not in shopping cart's page, but PayPal's page,
every payment must consists of authorization (blocking total sum) and subsequent capture if the ordered items are available and can be delivered,
customers aren't forced to create / login to PayPal account if they wish to pay via card.
The trouble is I'm really confused with the number of possible options at PayPal. The choice between REST API and Classic API isn't that problematic, but choosing the proper product from the whole list (like Classic API products or REST API products) isn't that obvious for PayPal newbie. Some other similar questions point to DoDirectPayment (but I don't know if it's the best choice) or suggest Website Payments Standard (I'm not sure if they're still available).
I was also considering Express Checkout, but the demo seems to force to create PayPal account.
ExpressCheckout is designed to be used in concert with a direct credit card acceptance method (such as PayPal's DoDirectPayment, or a non-PayPal credit card acceptance method), although it can be configured to also do guest payments. This is why the demos of the normal configuration handle only PayPal account creation; that's the normal usage.
One key question you need to ask yourself is whether you want to have access to the credit card information & be the "merchant of record" yourself or not.
YES: Doing this gives you the most flexibility, but will require you to go through some merchant vetting and carries some security obligations (PCI) even if you are using some solution which tries to distance you from the actual raw card numbers (e.g. collecting them via PayPal or Braintree code and immediatly encrypting & tokenizing them). In short: if you want full access to the card, then you have legal obligations re: handling that account access which technology can reduce but not eliminate.
NO: If you are content to always treat your customer's card information at arms length through PayPal, via the legal structure of a PayPal account (whether the user actually has a PayPal account or is just doing a "guest" payment on PayPal where they give PayPal their credit card for one-time use) then you can reduce your vetting & security constraints (no PCI requirements at all).
If you want (or need) access to the customer's card [YES above] then the "classic" API solutions are either DoDirectPayment (for when you collect the card info) or Hosted Sole Solution (for when PayPal collects the card info on their page). HSS meets all 3 of your requiremens above; DDP fails requirement #1.
If you can live with access to the customer & the payment but NOT the card account itself [NO above] then you can use Website Payments Standard, or EC with Guest Checkout option; both meet all three of your requirements.
All of the above solutions are not only still supported, but have tens or hundreds of thousands of integrated merchants and are the biggest/mainstream ways in which PayPal payments are handled.
If you prefer the newer products & are in the first category above (real card access, not guest payments) then you can also use Braintree or the RESTful APIs. These newer products don't yet have as much flexibility & coverage as the older products, but hey, less complexity can be a good thing as long as they have what you need. These products are generally designed around plugins for your web pages rather than entering card information on PayPal's site, however, so they don't meet your first requirement.
You can also do PayFlow (several variants) or Adaptive Payments or or or.... but in general I would advise picking either the most well-established or the new-and-growing options as being better supported & more future-proof.
Now that PayPal has acquired Braintree, the preferred integration method is v.zero. It is designed to be very easy to accept PayPal, Credit Cards and other options. (Venmo, Bitcoin, etc.)
Evening
I have a client who is asking to build an eCommerce tool in which multiple stores are able to create accounts and their products in order to sell them via a web app.
This is not like any regular eCommerce sites since we are working with multiple stores each one of them with an unique bank account.
The quick solution is to ask the stores users to give me the bank account and all extra sensitive information and do the transaction via coding my self... but i don't want to mess with such delicate data that is why im looking for some service that helps me do that.
I know that i can use auth net to build something like that but my main client will have to pay for each of those merchant accounts, which is not a very good option.
Any of you had the chance to work in something like this before? Can you tell me which services you used? Would be extraordinary to use the same payment gateway to do everything but i am probably asking for too much...
Waiting for answers, thanks in advance
You definitely don't want to be storing bank information and card data if you are not Level 1 PCI compliant. There is a lot of financial liability if you do so.
There is a company called Base Commerce (www.basecommerce.com) which allows developers such as yourself to create a 'partner' account and associate multiple merchant accounts under it. You can spin up or down as many accounts as you want, all programatically, at no cost (except for the small % transaction fees that are normal in payment processing). You will also get commissions on the transactions your merchants process.
Suppose there is an auction site that uses google checkout exclusively. How would one set things up so that when the buyer sends money to the seller google checkout sends something like 1% of it to the auction site much like how ebay charges a fee.
Google Checkout is a payment flow between one seller and one buyer. There is no support for automatic third party commissions.
You need to setup two separate transactions where the seller pays the auction broker the commission or listing fee.
I'm not sure this is the right place to ask but anyway:
I have an e-commerce platform that I want to monetize based on a percentage of revenue made (eg. a store that uses my platform has an order for $100, so I get 1% or $1, while they get $99).
Currently I offer paypal and credit card payments (via my merchant bank) to all stores on the platform (ie. all payments made, regardless of the store, are through the same paypal and merchant account). I then pay these stores per month which is ok for the moment because there are only a few stores using the platform.
Moving forward I want to automate this process and ideally have it operate in real time.
Paypal have an "Adaptive Payments" API that allows chained or parallel payments on a single transaction processed in real time. This means I can skim my 1% and pass the rest of the money along my customer in real time.
I was wondering if there is a similar real-time service for Credit Card processing*? If not, is there a bank/merchant that allow API payment access so I can automate payments per day or week? OR should I just transfer all money from my bank to paypal and use this to pay my customers?
*I realise you can process credit card payments through Paypal without having to sign up, but this is less than ideal. I want the credit card processing to happen on my page as at the moment I'm seeing about 70% of orders using this over paypal.
I was wondering if there is a similar real-time service for Credit Card processing?
No there isn't. True merchant accounts do not allow for split payments. Only one entity can receive a payment and it must be the business the merchant account has been set up for. Receiving the payment for someone else is called factoring and is against all of the major credit card issuers' rules. If a merchant account is found to be factoring it will be closed and the merchant who owns the account will be blacklist. This will prevent them from ever having a true merchant account again. Additionally, there is no way to send money with a merchant account other then issuing a refund for prior purchases.
If not, is there a bank/merchant that allow API payment access so I can automate payments per day or week? OR should I just transfer all money from my bank to paypal and use this to pay my customers?
Other then using adaptive payments, this is definitely the easiest and most straight forward way to accomplish this.