Token provider | 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) |
Apple Pay | + | + | + (n the Safari browser) | + (n the Safari browser) |
Samsung Pay | + | + | + | - |
Google Pay* | + | + | + | + |
*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 COF operation or as E-COM operation with additional payment confirmation by the payer via entering the CVC2 code and passing 3DSecure authentication.
Thereby, the following payment options are available for mobile apps developers:
For Apple Pay:
- using Assist SDK for iOS (via WebView) - for payment by the button on the IPS Assist payment page;
- using Assist.SDK for iOS - for payment by the button in app.;
- using Apple Pay SDK + TokenPay service (see Annex 1) - for payment by the button in app..
For Google Pay:
- using Assist SDK for Android (via WebView) — for payment by the button on the IPS Assist payment page;
- using Google Pay API + TokenPay service (see Annex 1) — for payment by the button in app.
For Samsung Pay:
- using Samsung Pay SDK + TokenPay service (see Annex 1) — for payment by the button in app.
- using Assist SDK for Android (via WebView) — for payment by the button on the IPS Assist payment page.
To receive payments by tokens on the online store website, the following options are available:
For Google Pay: only at the opening a payment page on mobile device:
by the button on the IPS Assist payment page;
using Google Pay API and TokenPay service (see Annex 1).