We're looking to integrate a oppwa payment gateway to our ecommerce but we can't understand the logic of this system.
The question is, Oppwa need a merchant account to able get the payments? Or if not, where go the money?
Any idea about how is working Oppwa?
Thanks,
This depends on the payment gateway.
On my implementation, the payment gateway company requested some documents for helping me to set up a merchant account. Money is coming directly to my account.
Related
I am building an ecommerce store like amazon where sellers can sell and they receive money when a product is bought.
I am using stripe api with nodeJS for handeling payments. What is exactly the process of paying a user with stripe?
On their documentation they said of creating an account then transferring fund but in the process what about taking user's payment details like their bank account.
What are the steps which I need to follow for a paying a user out?
You'd need to use Stripe Connect. Each merchant you pay will need to be a connected account to your platform.
We are developing an application for restaurant usage, in that we have integrated Stripe Payment Gateway. Our application is having 3 types of users, Admin, Restaurant and Customer. Admin will take a charge from Merchant for using the application in each order they place through the application.
To manage this Payment Transaction we have used Stripe Connect, for example, if Customer is paying $2 then admin will take $0.5 as an application fee, and the merchant will receive the $1.5, but here the question is who will pay the Stripe Charge. We need that, Merchant will bear the Stripe Charge.
Here is the screenshot of a successful transaction. Can anyone guide me about this make sure?
You should review the different types of charge flows available when using Connect. Based on what you've described, it sounds like you want Direct charges, with the fees paid by the connected account, but it really depends on the details of your business. You can review the fund flow diagram to see if it matches what you need.
I am using Stripe API for a project.
My requirement is users using my app can pay some tips or service fees to other serving users. So basically it is a kind of user-to-user payment.
I have tried everything I can and I am searching on the Internet. But didn't find anything helpful.
Is it possible to do using Stripe?
I am new to Stripe. I have used PayPal before to achieve the same.
Thank you!
I don't know Stripe very well, but with most of the payment service providers you could only enter one account number to which the payments will be paid. This for security reasons so other people can't receive your payments by simply hacking a config value with the users' account number.
I am building a payment methodology using Stripe. My aim is to transfer money to user's bank accounts programmatically.
As I was investigating Stripe API reference, I found out Recipient object which seems being deprecated. Then I found out about StripeConnect which can achieve this, but still in beta.
My question is if there is any other way to transfer money to user's bank account without StripeConnect. Also I would like to have support in countries besides US and Canada. What is the best way to achieve this functionality by using Stripe?
Thanks.
The only way to do this currently is with Stripe Connect and either Managed or Standalone accounts. Connect itself isn't in beta only Managed accounts are.
I have a client who has content that he wants to publish on the web (and potentially for iPad). He wants the viewer to pay to subscribe for the content.
Is there a service out there I can integrate with to for handling the accounts and collecting the monthly subscription fee (using credit cards or something else)?
There are several services out there that can help you with this - Recurly (where I work), Chargify, CheddarGetter, Spreedly, etc. These services handle the recurring billing aspect, customer management, email communication, following up with failed payments, etc. You'll also need a payment gateway (to process the cards) and a merchant account (for the payment gateway to deposit the funds into).
Authorize.net and PayPal both have recurring billing features, but the logic for upgrading/downgrading accounts is not there or difficult to use, and you'll still need to handle customer communication for failed payments and other actions.
You need to use a payment gateway here, which will be responsible for handling the transaction between your site and the many different payment networks. There are a lot of operations happening in between, so you might want to check out the wikipedia article for a step by step information on that.
We personally use authorize.net in our company for many of its advantages, some of which are:
It has an API that makes it easy to integrate with any language.
It is a trusted brand already, proven by the number of merchants that use them.
It is secure.
It provides the service with a reasonable price.
Most of major payment gateway providers do support recurring billing or subscription plans, paypal,authorize.net etc, most of the time you have to log in to your account admin console and configure a plan, and send the payment plan id with the payment request to the payment gateway. some payment gateway providers, like Braintree supports to create recurring billing plans dynamically and assign users to that plan at the run time it self, how ever it's always better to go for a local payment gateway provider or a payment gateway which provides low fees, if your preferred payment gateway provider is not supporting recurring billing anther options is to store cc details on the server and and handle it your self but it's a great risk to store cc details on the server, and you will have to follow PCI standards and it's hard.