Barion Smart Gateway for mobile: Difference between revisions

From Barion Documentation
Jump to navigation Jump to search
No edit summary
No edit summary
Line 13: Line 13:
To provide a consistent and secure user experience, you must utilize a first-party solution called "CustomTabsIntent" for displaying the Barion Smart Gateway on Android. It's essential to note that WebView does not support Passkey authentication.
To provide a consistent and secure user experience, you must utilize a first-party solution called "CustomTabsIntent" for displaying the Barion Smart Gateway on Android. It's essential to note that WebView does not support Passkey authentication.


[https://developer.chrome.com/docs/android/custom-tabs/guide-get-started/ Google's step-by-step guide] will help you using CustomTabsIntent.{{NotificationBox|title=Action Required for Android Apps|text=If your application currently employs WebView to display the Barion Smart Gateway, it is imperative to prioritize refactoring.|color=#1993C7}}{{NotificationBox|title=IMPORTANT|text=Failure to implement CustomTabsIntent will result in users being unable to log in to their Barion Wallet.|color=#FF7A3D}}
[https://developer.chrome.com/docs/android/custom-tabs/guide-get-started/ Google's step-by-step guide] will help you using CustomTabsIntent.{{NotificationBox|title=Action Required for Android Apps|text=If your application currently relies on WebView for the Barion Smart Gateway integration, it is essential to prioritize refactoring.|color=#1993C7}}To assist you in this transition, [https://developer.chrome.com/docs/android/custom-tabs/guide-get-started/ Google provides a comprehensive step-by-step guide for integrating CustomTabsIntent seamlessly].


=== iOS ===
By adhering to these guidelines and implementing the recommended solutions, you can ensure that your mobile application seamlessly leverages the power of the Barion Smart Gateway, enhancing user convenience and security in payment transactions.{{NotificationBox|title=IMPORTANT|text=Failure to implement CustomTabsIntent will result in users being unable to log in to their Barion Wallet from the application.|color=#FF7A3D}}
 
== iOS ==
To provide a consistent and secure user experience, you must utilize a first-party solution called "SFSafariViewController" for displaying the Barion Smart Gateway on iOS. It's essential to note that WKWebView and UIWebView do not support Passkey authentication.{{NotificationBox|title=Action Required for iOS Apps|text=If your application currently relies on WKWebView or UIWebView for the Barion Smart Gateway integration, it is essential to prioritize refactoring.|color=#1993C7}}To assist you in this transition, [https://developer.apple.com/documentation/safariservices/sfsafariviewcontroller Apple provides a comprehensive step-by-step guide for integrating SFSafariViewController seamlessly].
 
By adhering to these guidelines and implementing the recommended solutions, you can ensure that your mobile application seamlessly leverages the power of the Barion Smart Gateway, enhancing user convenience and security in payment transactions.{{NotificationBox|title=IMPORTANT|text=Failure to implement SFSafariViewController will result in users being unable to log in to their Barion Wallet from the application.|color=#FF7A3D}}

Revision as of 13:48, 22 September 2023

Barion Smart Gateway integration for mobile applications

Barion simplifies the process of payments through the Barion Smart Gateway, enabling users to make secure transactions using their Barion balance or credit card directly from within mobile applications. Before you start to integrate we recommend reading this article first.

To ensure a smooth integration experience, please review the following guidelines:

Payment Initiation

When an application initiates a payment, it should be presented to users as a responsive website, mirroring the web payment experience. However, specific technologies must be employed to unlock the full functionality of the Barion Smart Gateway.

User Authentication

For user authentication within the Barion Smart Gateway, a passkey is required. To seamlessly display the Barion Smart Gateway within your application, consider the following platform-specific instructions:

Android

To provide a consistent and secure user experience, you must utilize a first-party solution called "CustomTabsIntent" for displaying the Barion Smart Gateway on Android. It's essential to note that WebView does not support Passkey authentication.

Google's step-by-step guide will help you using CustomTabsIntent.

Action Required for Android Apps
If your application currently relies on WebView for the Barion Smart Gateway integration, it is essential to prioritize refactoring.

To assist you in this transition, Google provides a comprehensive step-by-step guide for integrating CustomTabsIntent seamlessly. By adhering to these guidelines and implementing the recommended solutions, you can ensure that your mobile application seamlessly leverages the power of the Barion Smart Gateway, enhancing user convenience and security in payment transactions.

IMPORTANT
Failure to implement CustomTabsIntent will result in users being unable to log in to their Barion Wallet from the application.

iOS

To provide a consistent and secure user experience, you must utilize a first-party solution called "SFSafariViewController" for displaying the Barion Smart Gateway on iOS. It's essential to note that WKWebView and UIWebView do not support Passkey authentication.

Action Required for iOS Apps
If your application currently relies on WKWebView or UIWebView for the Barion Smart Gateway integration, it is essential to prioritize refactoring.

To assist you in this transition, Apple provides a comprehensive step-by-step guide for integrating SFSafariViewController seamlessly. By adhering to these guidelines and implementing the recommended solutions, you can ensure that your mobile application seamlessly leverages the power of the Barion Smart Gateway, enhancing user convenience and security in payment transactions.

IMPORTANT
Failure to implement SFSafariViewController will result in users being unable to log in to their Barion Wallet from the application.