Do Apple's iMessage Extensions allow: Custom Payment providers and Custom Authentication? - ios

We would like to port our existing application to iMessage soon.
Our application uses traditional Register / Activate through email, Log-In, then Browse the goods, Make a purchase, pay with your credit card.
We use a reputable payment processor and their tokenization services to process the credit card payment.
My questions are two-fold:
Does Apple allow the use of Custom Authentication (Sign up, Activate, Log-in with your own systems)?
Does Apple allow the use of Non-Apple Pay payment processing. Capturing CC information in the iMessage Extension app and tokenizing it using our existing payment provider?
I could not find any information about it. All documentation for new features largely includes info on things that are newly supported, but they do not like disclosing things that are restricted.

Related

Will Apple accept my app if I disable Sign in with Third parties

Apple just rejected my app due to I don't offer Sign in with Apple in my app as my app allow login with Google and Linkedin, and these(sign in with Google and Linkedin) are configurable like if some user don't want this it'll be disable by Admin.
So Can I go with another try to remove this option for that user which we give to Apple for Review and also tell them its configurable and not mandatory. So will Apple accept my app ?
Thanks
Personally I do not recommend using different configurations only for the App Store review process, because you can get rejected from App Store completely for cheating on the process. Read more at:
https://developer.apple.com/app-store/review/guidelines/#introduction
If you attempt to cheat the system (for example, by trying to trick
the review process, steal user data, copy another developer’s work,
manipulate ratings or App Store discovery) your apps will be removed
from the store and you will be expelled from the Apple Developer
Program.
About Apple Sign, here is Apple guidelines regarding this feature:
4.8 Sign in with Apple
Apps that exclusively use a third-party or social login service (such
as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with
LinkedIn, Login with Amazon, or WeChat Login) to set up or
authenticate the user’s primary account with the app must also offer
Sign in with Apple as an equivalent option. A user’s primary account
is the account they establish with your app for the purposes of
identifying themselves, signing in, and accessing your features and
associated services.
Sign in with Apple is not required if:
Your app exclusively uses your company’s own account setup and
sign-in systems.
Your app is an education, enterprise, or business
app that requires the user to sign in with an existing education or
enterprise account.
Your app uses a government or industry-backed
citizen identification system or electronic ID to authenticate users.
Your app is a client for a specific third-party service and users are
required to sign in to their mail, social media, or other third-party
account directly to access their content.
Read more:
https://developer.apple.com/app-store/review/guidelines/#sign-in-with-apple

Working of Apple Pay in iOS swift

I have integrated the code required for Apple Pay in my app based on the documentation available with Apple.
However, as a beginner, I have a doubt.
We have not used any third party payment processors like PayPal, Stripe etc.
Is it mandatory to use a third party processors? Can we just use the code and passbook/wallet and do the transactions?
Note: Merchant IDs, Payment certificates are created in the developer account.
Based on Apple documentation a payment provider is recommended but not mandatory.
Using one of these SDKs or hosted solutions is highly recommended
About develop your own payment process...
The alternative is to provide your own server-side solution to receive
payments from your app or website, decrypt payment tokens and
interface with the payment provider to process the authorization.
Handling credit and debit card payments can be complicated and unless
you already have the expertise and systems in place, an Apple Pay SDK
or JS API from a payment provider is the quickest and most reliable
way to support Apple Pay in your app or website.
In my opinion, It's better use a payment provider than develop your own. You're working with money, credit cards numbers...

Using PayPal to pay end users

I am developing an iOS application that rewards users for specific activities with cash payments. Yes, I understand there are restrictions on this with the App Store and I've considered these. My questions is specifically about the PayPal SDK and whether it is suitable for allowing an iOS application to connect with a user's PayPal account, so the user can elect to receive payment for their rewards. Essentially, I need a "receive payment" button in lieu of a "Pay Now" button. My questions is about iOS specifically and whether or not the PayPal SDK is suitable for receiving payments as a user.
The PayPal-iOS-SDK is for enabling a user/customer to authorize and pay for purchases, or pre-authorize future payments for purchases. Not what you seem to be looking for.
Instead, check out PayPal's Payouts API, which replaces the never-to-be-depreciated MassPay API (for the differences, see this Stack Overflow Q&A). There's also a remote possibility that you're a candidate for the AdaptivePay APIs.

How to pay out money to multiple paypal or venmo or checking accounts from a single business account inside an iOS app

In our app, we are trying to implement a payout feature. If the user correctly performs Action A, we want to be able to pay some incentive money to this user, assuming the user has already connected his account to PayPal or Venmo.
How can I implement this, do PayPal and/or Venmo SDKs/APIs make this possible?
Venmo does not allow you to send money from a business to customers. PayPal does, I believe. You should do this from a backing web service, rather than the app itself. To complete the payment from the app, you would need to embed your account information in the app itself, which would be a security disaster.

Using iTunes store client data for authenticating users in iPhone App

I know that the iTunes Store stores client information, such as the client name and credit card information. Eg, if you want to buy a game, you have to log in using your apple account and provide credit card details. These details are already stored with Apple
I want to build an app that uses this credit card information stored with Apple to allow clients to make payments. Note: I do not want to use the in-app purchase model.
Does Apple provide an API that given the client username and password, allows me to access the credit card information and then make payments?
The idea is to build a charity donation app around this. But the in-app model does not support this.
In a nutshell, we basically want to use the existing iTunes infrastructure to build a charity donation app. Any ideas?

Resources