I have an app with Free, Premium and Gold subscription plan. Based on the plan user can access features like filters, messages, likes.
Now, I'm planning to have an web app only for payments using stripe. So, users will directed to web app to pay payments.
Will apple allow this approach or will they insist to use in-app purchase?
I'm little confused here. Need your suggestion here?
This is a question for Apple Review team, you should reach out to them directly and clarify. Stripe doesn't replace in-app purchases and you need to use Apple's API to perform in-app purchases. See here for details
Related
My app is dependent on Camera. We are showing alerts and live view of camera in app. User can purchase plans to enable AI feature on camera firmware and we are also providing cloud storage for history. So can we use other payment sdk other then Apple pay as our app is dependent on Camera(Hardware). We are not restricting any feature inside the app. All features are turn on on Camera firmware.
We want to use Third party payment gateway not Apple pay as our app is dependent on hardware.
Based on the description, your use case sounds like in-app purchase, which is different from Apple Pay. You can read this doc to learn the difference between Apple Pay and in-app purchase.
For in-app purchases, you have to use Apple's in-app purchase SDK.
I am going to build an eCommerce website that supports PayPal.
Buyers connect their PayPal account to the website before they get products.
The website should collect funds without a normal checkout flow whenever buyers buy products.
For this, I've researched the Permissions Service API on PayPal.
But, I can't find enough descriptions to build such a website.
I would like to know how to integrate PayPal for this.
What you are looking for is 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.
I plan to use a 3rd party payment gateway for in-app purchases for an app distributed through the Google PlayStore. I'm aware of Google's policies regarding payments for in-app purchases (https://play.google.com/about/monetization-ads/payments/)
My content / service delivery model is as follows:
When a user pays for a plan he gets—
Certain features in the app
Certain features in our web portal, completely outside the app
Our deployment staff going and visiting the user's location and
providing training and setup services.
For some plans, we will be delivering a physical device to user's
locations (a POS machine to accept card payments)
Since my offerings are a combination of physical and digital goods and services provided within and outside the app, it does not clearly fall under the categories Google mentions in the link above.
My question is: Can I use a 3rd party payment gateway to accept payments within the app given my content / service delivery model?
Do I risk being blacklisted? Does Google give a time window to react by sending an email first before pulling apps down.
I know my question is similar to this one: Android In-app purchases and I'd like to get similar opinions on my planned content / service delivery model.
Kindle PlayStore app, distributed via Play Store also seems to be an example of an app using different payment method from Google's billing APIs
I am new with paypal.
After searching for info it seems paypal has a lot of technologies, APIs etc to be consumed and I cannot choose to right one for my case
My business case:
Simple marketplace android application with 2 main actors:
Seller
Buyer
Actions:
When buyer want to buy something via marketplace -> he pays via own paypal account to seller (buyer can see paypal page and authorize payment)
Seller automatically send fee payment to marketplace's paypal account (seller does not need any time autorize payment to marketplace, it should be automatically after buyer send money to seller)
Thanks for every help!
There are a number of ways to get that done depending on the experience you would like for all parties involved.
PayPal would recommend that you use the Adaptive Payments API for this because it's exactly the sort of thing they built it for. Specifically, you could setup a chained payment. That will automatically split the payment between the seller and the marketplace / app owner.
I personally don't like the Adaptive Payments checkout experience, so I prefer to build the same functionality with Express Checkout.
For this, though, you would need to have the sellers that sign up with your marketplace create a billing agreement with the app (marketplace) so that you can trigger payments on their behalf.
Then you would build a reference transaction payment to yourself from the seller account any time you need to. So this could be as each transaction happens, or you could tally up some number of transactions and only process the reference transaction payment to yourself when the total reaches some amount, or do it once per week / month, or whatever you want to do in that case.
I recommend Express Checkout as your payment solution.
https://developer.paypal.com/docs/classic/products/express-checkout/
EC provides mobilized checkout page, and you do not need to apply for special approvals. And by setting PAYMENTREQUEST_n_SELLERPAYPALACCOUNTID in SetExpressCheckout API, you may achieve parallel payments easily.
https://developer.paypal.com/docs/classic/express-checkout/ht_ec-parallelPayments/
https://developer.paypal.com/docs/classic/api/merchant/SetExpressCheckout_API_Operation_NVP/
I'm building an application for a new small business. They run events at race tracks, and the application is a registration system for said events. As a small business the owner doesn't want to worry about handling people's credit card info. They are just starting up and we are building from the ground up. So we are looking at using third party services like Google Wallet and PayPal.
So looking at the documentation, we have the Instant Buy API. Seeing as we aren't planning on taking direct credit card payments, it seems like a pain to setup payment processing through another service to use the Instant Buy. But we aren't selling a "Digital Good", as far as I can tell (I haven't seen a documented definition for this), so does that mean we can't use the API for Digital Goods? I haven't found any documentation that lays this out as a policy. It seems like it would be a lot simpler to implement, even with the cut Google takes.
There is a page at the google wallet documentation site called Which API Should I Use?, the first item there is:
The quick answer: it depends on your goals, your platform and what
kind of goods or services you're selling. The Instant Buy APIs are for
selling physical goods, while digital goods sellers should use the
Google Wallet for Digital Goods API for web apps or Google Play In-app
Billing for Android for native Android apps. To engage your customers
with offers and loyalty programs, use the Wallet Objects API.
Now, the Instant Buy APIs are for those business that have an existing payment gateway setup, but need to offer Google Wallet as a payment option.
In your situation, as you don't have a payment processor setup:
To sell physical goods on web apps and mobile apps that run on
browsers, use Instant Buy for web. You'll keep your existing payment
processor and optimize your payment flow with Google Wallet, just like
with Android. You can use Instant Buy for web to sell digital goods,
but if you lack a payment processor or resources to maintain and
develop a PCI-compliant online store, you should use the Google Wallet
for Digital Goods API.