Account Access implementation Options

Account Access may be implemented in one of the following ways:

  1. SELF_HOSTED
  2. SELF_HOSTED_CALLBACK

Implementation Overview

The following summarises the options available to both merchants and partners (acting on behalf of merchants):

Self-Hosted In this implementation mode:
  • The user interface is handled by you for Bank Selection.
  • The signal that the PSU and ASPSP have finished interacting is sent via a POST to the URL defined in the merchantPostAuthUrl of the /consents/ request.
Self-Hosted-Callback In this implementation mode:
  • You handle the user interface and you also manage the ASPSP OAuth Callback URL
  • The signal that the PSU and ASPSP are finished interacting is sent via a POST to the URL defined in the merchantPostAuthUrl of the /consents request.
  • The details of how to process this callback differs from the SELF_HOSTED flow. You need to process the OAUTH callback from the ASPSP directly, parse the information and send it back to the Nuapay TPP platform.
  • This option is useful if you want to style your callback handler or have mobile apps handle the callbacks using mobile deeplinking.
  • In the context of mobile apps, Deep Linking consists of using a uniform resource identifier (URI) that is opened within a mobile app rather than simply launching a Web browser.