Processing multiple third-party ecommerce transactions

I am currently planning to develop a web application that will allow a third party to list and sell their own products on it.

Despite the fact that I have experience in developing solutions for e-commerce, I personally do not want to do anything with the payment system itself (legally, not technically) so that any transactions are between the buyer and the seller, and I myself am a third-party.

I hesitate to use Paypal, because I want to seem professional, and I do not trust them and do not like them. I also do not want to use any bank or trading account, ideally I would need it for each client (and not centralized), which would lead to excessive contributions to the seller.

What is the best way to do this? Perhaps I would be ready to accept any part of the transaction (preferably with a low level of risk), if absolutely necessary. I try to minimize costs and overhead as little as possible.

At first it will be a site based on the UK, but with potential global access. It will also be developed in (possibly) PHP, but this should be regarding the problem.

Thank you for understanding!

+4
source share
3 answers

We launch www.hitmeister.de a major trading platform in Germany. What you are planning is similar to what we are doing, for sure ...

In our system, a contract is concluded between the buyer and seller. All funds pass through our accounts, which makes us an intermediary in the transaction. The client can pay through direct debit, credit cards, paypal, etc. The seller can receive money only by bank transfer. We keep the money deposited until the transaction is completed.

Obtaining this setting for Paypal and direct debit was not a big problem. Credit card operators usually do not like these mechanisms, since you are becoming a (semi) acquirer. They will do it though, if you talk to them.

Hope that helps

+1
source

Is your business attracting sellers paid by their customers (or helping them get money) or attracting customers to them, process and transmit relevant information? I agree that the first is a big legal and CR mess. Who wants to process calls or emails from random idiotic people about their purchases and payments? It is better to be in the latest business to attract customers and disseminate information.

If this is only the last, ask each seller to provide a URL pattern or verification link in the form that they use to establish the service. By URL pattern, I mean URLs with variable components, such as transaction amount, customer ID, etc. ... Use this template to redirect the client to the appropriate system when it is time to pay the seller. Thus, small merchants can use paypal, but large merchants with their own systems or something other than PayPal can also be supported.

Code every merchant for everything you do for them.

If he can work in this way in a business, then the main technical problems analyze the basic requirements for payment services (paypal, google payments, or maybe a merchant system cc or two) to understand what your site should feed on its site (this may be a URL pattern or it can be more) and creating related wizards for easy customization by merchants. The advantage is that if you do it right, you will also support the majority in home trading systems, because they will need to collect the same basic information.

0
source

Source: https://habr.com/ru/post/1299835/


All Articles