I'm exploring how to develop some g-suite applications (eg. gmail add-on, spreadsheet add-on, etc...). It's not clear to me whether the g-suite platform offers a payment API to let me charge customers $2.99 USD per installation? Then google will automatically settle the sales revenue into our bank account? I can't find any technical literature that confirms or denies the existence of this feature.
Or do I need to take a more traditional approach by directing the customer (eg. in the form of an iframe or something) to a page on my web server, where I integrate my own merchant service provider of choice (eg. paypal, stripe, etc...) to handle credit card payments? Then I need to oauth2 authenticate them on my server, confirm their billing is in good standing, before providing access to paid features?
I think for your case you should go and read carefully the G Suite Marketplace Developer Agreement.
In there you have this line which explicity says that you would need to pay Google a "Listing Fee"
3.2 If you choose to distribute Products through the Market for a fee, you will pay Google a non-refundable listing fee ("Listing Fee") as set forth at https://code.google.com/googleapps/marketplace/fees.html.
Related
I want to make a payment system in which users can connect their PayPal account to a website. In this step, login required.
When transaction occurs, without having to log in again, users can pay to the site.
This would be quite different from PayPal subscriptions -- just auto payment like upwork client account.
What you are looking seems to be a "Reference Transactions" solution. It can be tested in sandbox, but to use it in live, the business account would need to be approved for this feature by PayPal. To do this the account owner would need to contact their PayPal account manager or PayPal's general customer support (not MTS), and explain the business need for this feature.
As far as implementing the solution, the only public documentation I'm aware of is for classic APIs: https://developer.paypal.com/docs/classic/express-checkout/ec-set-up-reference-transactions/ . Any newer API or vault solution does not appear to be publicly available at this time, but you could always contact PayPal's support and ask if there's something they'd rather you implement than those classic APIs. The more significant hurdle is the business approval for the feature mentioned earlier.
My company is looking to use the vaulting feature with Paypal for storing credit card info. I am not on the development side of things. I just need to know do we just need to have a paypal account to use this vault? Do we need to have a business account or a contract with paypal in order to use this? This is very time sensitive so any help would be greatly appreciated.
Scott
Yes, you will need to set up a PayPal account for this functionality.
Those in charge of the financial account to which the PayPal account will be linked (i.e. your company's bank account) will also need to answer questions regarding the bank account's validity correctly in order to unlock full API access for your developer(s):
https://developer.paypal.com/docs/api/
Your developers will also need to be set up, once the PayPal account has been confirmed and validated, with authorized logins for the account, as well, so they can test and ensure that PayPal transactions are confirmed during the development process.
A word of caution: Though I'm unaware of your business, its practices, etc. it's a hefty sum of responsibility and potential liability to offer the storing of user-sensitive financial information. If you're not prepared to handle the legal ramifications if this data is ever stolen or accessed without authorization, then this is not the development path your company should take.
You would just need a business account to use REST API PayPal.List of countries supported.
The REST API supports many countries for PayPal account payments. All you need is to upgrade to a Business account. For country-specific offerings and limitations, refer to PayPal Offerings Worldwide and visit your country-specific site for further details.
No need of a PRO account.
When I was setting the paypal application I see this note:
Important: Live credentials are disabled for some capabilities. We
require additional information from you for these capabilities as
noted below.
And this:
Accept PayPal and allow direct credit card processing Non U.S.
developers, please note that direct credit card processing is not
offered to you when using REST APIs. Your live credentials are
inoperable for direct credit card processing but your test credentials
are enabled for sandbox testing.
What I understand of this is that a Non U.S. account could no process Direct Credicard payments, but they don't say anything about others payment capabilities.
So I made my application, use the REST API in Sandbox and everything works great.
No I was setting the live application and I couldn't. After reading again the Documentation I found this:
Do I need a U.S. PayPal account to sign up? To accept payments using
the new REST APIs and PayPal Mobile SDK, we currently require a U.S.
PayPal Business account. But stay tuned for more country support. Note
that most countries can use our Classic APIs.
Some is very confuse the message, Am I or Am I not able to use an UK business account to process payments (with for example paypal balance) with the REST API?
The REST API is currently only available to US merchants. UK merchants cannot yet use the feature - sorry.
From the FAQ page on Developer.PayPal.com:
Do I need a U.S. PayPal account to sign up?
To accept payments using the new REST APIs and PayPal Mobile SDK, we currently require a U.S. PayPal Business account. But stay tuned for more country support. Note that most countries can use our Classic APIs.
I was using Paypal Sandbox for testing transactions last year using my PayPal developer account.
I just checked last week that I cannot access my old account, so I decided to sign up for a new account. However, you need now to sign up for a business account. Business account is only available to U.S. businesses (I came from outside the US).
I was hoping if you can suggest an alternative and free developer account (similar to PayPal), but with a different payment gateway.
Thank you.
How about stripe ?
Stripe
Uses a JavaScript based API to complete transactions.
Simpler to integrate with multiple platforms.
You don't need a US Business account to use developer.paypal.com.
Simply sign up via https://www.paypal.com/ for a live PayPal account, either Premier or Business, and you'll be able to log in to developer.paypal.com with it.
Note however that the new REST API is currently available for live US Business accounts only, but this won't affect the availability of other Sandbox products or functionality.
I'll look into why the messaging states that you do, because that's not correct. Thanks for pointing this out!
We currently use the Website Payments Pro recurring billing solution from Paypal for a SaaS web application (user signs up for a monthly billing subscription to our service) but are becoming increasingly concerned that all of our credit card data is 'locked in' to Paypal and we can never get access to it.
The ideal for us is at the point of signup to store a users credit card details in a third party system (vault) whilst processing the transaction through Paypal's Website Payments Pro billing solution. This would give us the freedom to change our payment processor without having to ask everyone of our users to re-enter their card details - storing payment details in a third party PCI compliant system would allow us to do this.
Does anyone know of any such solutions that would allow us to store credit card details without transacting against them and whether these would be available to UK based companies ?
Thanks - appreciate any help you can give.
Mike
PayPal now offers such a service
https://developer.paypal.com/webapps/developer/docs/api/#vault
I found that Briantree.com offers that service
I'm not aware of anything that does this (but would love to hear otherwise). The reason it doesn't exist I would assume is because 'my' PCI-DSS requires that any third party that I pass card details to is also PCI compliant.
Therefore, this 'vault' provider would only be able to return to you a full card number if you were fully PCI compliant (and if you were, then why would you need to use a 3rd party vault?!)
So the best you could optimistically hope for is a 3rd party that both vaults the details and also allows interaction with 'n' other payment gateways, but this would obviously only allow you to switch between gateways that the vault supports. Given that the 'vault' would need to generate income, as well as the gateways that it communicates with, I can't see this being cheaper than choosing and interacting with a single gateway directly.