Page History
Tokenprovider | POS payment | Pay by button in mobile app (InApp) | Payment in the web-browser on the IPS Assist side (Web) | Payment in the browser on the online store side (Web) | Payment in a mobile app using web-view |
Apple Pay | + | + | + (n the Safari browser) | + (n the Safari browser) | +/- (only in Safari browser OS version 13 or higher) |
Samsung Pay | + | + | + | - | - |
Google Pay | + | + | + (in Chrome browser on mobile devices with Google Pay App installed) | + | - |
Google Pay (saved cards)* | - | - | + | - | + |
Mir Pay | + | + | + (in a browser on Android mobile devices with Mir Pay App installed) | + (in a browser on Android mobile devices with Mir Pay App installed) | + (on Android mobile devices with Mir Pay App installed)- |
*Payment by non-tokenized cards that saved in your Google account is possible depending on the merchant settings. Payments by such cards can be processed either as E-COM operation with additional payment confirmation by the payer via entering the CVC2 code and passing 3DSecure authentication or as COF operation.
...
For Mir Pay only when the buyer opens the page on a mobile device with Android OS in a browser:
- using DeepLink or UniversalLink and TokenPay service for mobile apps.
The following payment options using the button in the app are available for mobile apps developers:
...
- using Samsung Pay SDK + Assist.SDK;
- using Samsung Pay SDK + TokenPay service.
For Mir Pay:
- using Mir Pay API + Assist.SDK;
- using Mir Pay API + TokenPay service.
The implementation of payment with tokens via a web view in a mobile app has a number of restrictions associated with the limitations of token providers. This method can be used if payment by cards has already been implemented via the web-view. It allows to add the ability to pay using the Apple Pay button and with cards saved in buyer’s Google account.