When a webview response is received, the App will need to direct the customer to the URL given as the start address. The App should monitor the progress of the webview, and once it reaches the URL
provided as the close address, it should close the web display and continue with the transaction process.

<?xml version="1.0" encoding="UTF-8"?>
<mobile>
  <webview>
    <start>URL the customer must be directed to</start>
    <close>URL that marks the end of the process</close>
    <abort>URL that marks an error during the process</abort>
    <code>Transaction code used in completing the request</code>
  </webview>
</mobile>

To complete the transaction, the App must now make a second request to the gateway. This request includes will trigger the final authorisation stage of the transaction, and return the authorisation response. The request must be sent to:

[<https\://<<base_url](https\://<<base_url)>>/gateway/mobile_complete.xml>

Request layout for transaction completion

<?xml version="1.0" encoding="UTF-8"?>
<mobile>
  <store>Store ID</store>
  <key>Authentication Key</key>
  <complete>Transaction code obtained in the WebView response</complete>
</mobile>

If the App detects an error during the webview process, or the webview reaches the URL given as the abort address, then it should close the web display and send an abort request to the gateway at the following URL:

Request layout for transaction abort

<?xml version="1.0" encoding="UTF-8"?>
<mobile>
  <store>Store ID</store>
  <key>Authentication Key</key>
  <abort>Transaction code obtained in the WebView response</abort>
</mobile>