Payment Initiation Service Provider Checkout Page implementation Options
Edit me

Your PISP checkout page may be implemented in one of two ways:

  1. CHECKOUT
  2. SELF_HOSTED
Checkout In this mode you can leverage on the Nuapay user interface for the Bank selection, bank confirmation and payment submission confirmation screens.
Self-Hosted The user interface is handled by you, the merchant (or partner, acting on behalf of a merchant).

Checkout Mode

In Checkout mode you will:

  1. Retrieve the appropriate authorisation (merchants will typically use their API Key; partners will need to provide an OAuth token for the required merchant).
  2. Call the /payments endpoint (see Create Payment) and set the integrationType to CHECKOUT
  3. Manage the returned payment identifier with some Nuapay-provided JS and CSS to render the Bank Selection screen for your payers.

A detailed overview of the various steps involved in this flow is provided in the image below.

Checkout Flow
CHECKOUT Flow

For more on this see Checkout Payment Page Setup.

Self-Hosted Mode

In Self-Hosted mode:

  1. You will design your own Bank Selection screen; use Retrieve Banks to populate your interface.
  2. Once you payer has selected a bank, call the /payments endpoint (see Create Payment)
  3. Set the integrationType to SELF_HOSTED
  4. Specify the bankId provided by the payer in step 2
  5. Manage the returned payment identifier as required.

A detailed overview of the various steps involved in this flow is provided in the image below.

Self-Hosted Flow
SELF_HOSTED Flow

For more on this see Self-Hosted Payment Page Setup