Using the Paystack Checkout in a Mobile WebView


When it comes to accepting payments with Paystack in your mobile applications, there are two ways to go about it:

  1. Using the Paystack library built for your tech stack of choice - You can integrate Paystack directly into your Android or iOS app using our mobile SDK. For mobile frameworks like Ionic or React Native, please find the libraries here.
  2. Using a WebView - You can also generate a checkout URL and embed it in a WebView on your mobile application. We'll be covering this option in this guide.
Code snippets
For the purposes of this guide, we'll include sample code for mobile apps built using Flutter, React Native, native Android, and iOS, but the flow described works for all the mobile app development stacks

Why use a WebView?

There are different reasons to consider using the hosted checkout in a WebView over integrating directly with the mobile SDK. Regardless of which method you choose, the payments are still being processed by the same underlying APIs. The only difference is the payment experience you'll be offering to your customers. Some of the pros of using a WebView are:

  1. By using our hosted checkout, the entire payment experience is controlled by Paystack. This means you don't have to build a checkout UI in your mobile application to accept payments, hence less code is required to integrate payments in your app.
  2. While only card payments are available on the mobile SDK, all other non-card payment types - such as bank transfer, USSD, Visa QR, Mobile Money, and Pay-with-Bank - are available on the checkout, and therefore available to the customer.
Integration Options
You can still accept payments via card on mobile if you're not using a WebView. All channels are available directly on the API and can be integrated into your application.

Generating the checkout URL

The first step in the integration is to initialize the transaction to get a checkout URL.

When a customer clicks the payment action button, initialize a transaction by making a POST request from your server, to our API. Pass the email, amount, and any other optional parameters to the Initialize TransactionAPI endpoint.

Show Response
2-H "Authorization: Bearer YOUR_SECRET_KEY"
3-H "Content-Type: application/json"
4-d '{ email: "[email protected]", amount: "20000" }'
2 "status": true,
3 "message": "Authorization URL created",
4 "data": {
5 "authorization_url": "",
6 "access_code": "nkdks46nymizns7",
7 "reference": "nms6uvr1pl"
8 }

Displaying Checkout in Your WebView

If the API call is successful, Paystack will return an authorization URL in the response. This URL should be returned to the frontend application, and loaded in the Webview widget. See the sample code below:

2Widget build(BuildContext context) {
3 return Scaffold(
4 body: WebView(
5 initialUrl: '',
6 javascriptMode: JavascriptMode.unrestricted,
7 userAgent: 'Flutter;Webview',
8 ),
9 );
Enable JavaScript on Flutter
Javascript needs to be enabled in the WebView for the checkout to load properly.
iOS Deprecation Notice

UIWebView has been deprecated in iOS 12.0 so for this guide we will use WKWebView.

We assume you have WKWebView in your storyboard in the view controller in which you want to show the checkout.

Once the checkout is loaded in the WebView, you'll need to listen for customer actions. That is, you'll want to know when the customer completes the payment or closes the checkout page. This can be done by listening for URL redirects in the WebView widget.

Handling WebView Redirects

Allow Redirect
Redirects should be allowed in the WebView widget to allow for bank and 3DS authorization. If the WebView blocks redirects, the customer will not be able to complete the transaction.

When customers complete the payment successfully, they are redirected to the callback URL set in your Paystack dashboard. You can override this, however, by passing a callback_url when initializing the transaction. This will override the callback URL set on your dashboard, and the customer will be redirected there instead. The WebView widget should now look like this

2Widget build(BuildContext context) {
3 return Scaffold(
4 body: WebView(
5 initialUrl: '',
6 javascriptMode: JavascriptMode.unrestricted,
7 userAgent: 'Flutter;Webview',
8 navigationDelegate: (navigation){
9 //Listen for callback URL
10 if(navigation.url == ""){
11 verifyTransaction(reference);
12 Navigator.of(context).pop(); //close webview
13 }
14 return NavigationDecision.navigate;
15 },
16 ),
17 );

If you have webhooks implemented, a charge.success event will be sent to your webhook URL, and it's recommended you use this to deliver value to the customer in your backend.

In your frontend, after detecting the WebView redirect to the callback URL, this means the transaction is successful. You can confirm the status by calling the Verify TransactionAPI, and then you can programmatically close the WebView widget and show the customer a transaction confirmation page in your app. This is handled in the verifyTransaction() method.

Handling 3DS properly

For card transactions that require 3DS authentication, when the customer completes the authorization, they're redirected to Automatically, when the URL hits, it should close the page. This is what happens on a web browser.

With WebViews however, the page doesn't close automatically. This is because the Javascript function window.close(), which closes the page in a browser window, won't work on a WebView. WebViews are native widgets and the window.close() method can only close windows opened by using the method. The workaround is to have your WebView listen for when the URL has been redirected to and then continue processing as usual by checking the callback function and any other process.

2Widget build(BuildContext context) {
3 return Scaffold(
4 body: WebView(
5 initialUrl: '',
6 javascriptMode: JavascriptMode.unrestricted,
7 userAgent: 'Flutter;Webview',
8 navigationDelegate: (navigation){
9 if(navigation.url == ''){
10 Navigator.of(context).pop(); //close webview
11 }
12 if(navigation.url == ""){
13 Navigator.of(context).pop(); //close webview
14 }
15 return NavigationDecision.navigate;
16 },
17 ),
18 );