If you are a developer that does not want to (or can't) use the Mobile WebViews inside of your native mobile app, there is a workaround using the Web Components.
This option works best for components that won’t be used on an ongoing basis, such as the Card Issuance and Card Activation (for physical cards). We will use the Card Issuance Web Component in our example below:
-
Inside of the mobile app, create an app-token for the logged in user following our OAuth guide
-
Add a link or button in your native app to a webpage that has embedded the Card Issuance Web Component.
-
Add the app-token as a URL param to the link and then pull it into the HTML embed
-
This token can only be used one time, so if the user refreshes the page the app won’t work
-
-
You can hard code the public-key, because it’s public facing and won’t change
-