Open BankingB2B SuiteERP Integration
GuidesChangelog
Menu

Categories

Open BankingB2B SuiteERP Integration


  • GENERAL INFORMATION

    • Documentation guide
    • Documentation guide
    • SingleView B2B Core APIs
    • SingleView Open Banking
    • Platform architecture
    • KSAOB standards
    • Security best practices
  • Getting started

    • Introduction
    • Become a User
    • Quick Lookup
  • GETTING STARTED

    • Integration guide
    • Become a user
    • Integration guide
    • Prerequisites for Sandbox
    • Developer console
    • Establishing secure connection
    • Establish secure connection
    • Authenticating your request
    • Generate access token
    • Making your first test api call
    • Make test raw data API call
    • Prerequisites for production
    • Make test data use case API call
    • Moving to production
  • Authentication

    • Generate Signature
  • ERP API Services

    • Configure API Account
    • Create Group & Company
    • Supplier Services
    • Account Services
    • Balance Enquiry
    • Statements
    • IBAN Validation
    • POS Transactions
  • CONSENT MANAGEMENT

    • Overview
    • Create a consent
    • Retrieve consent details
    • Revoke a consent
  • AUTHENTICATION

    • Header parameters
    • Obtain access token
    • Generate signature
  • Data APIs

    • Account statement
    • Balance enquiry
    • IBAN verification
    • POS transactions
    • Raw statement
  • Raw Data APIs

    • Introduction
    • View accounts
    • View balance
    • View transactions
    • Identify account holders (Parties)
    • Review direct debits
    • Review scheduled payments
    • Review standing orders
  • Payment APIs

  • DATA USE CASE APIS

  • SADAD

  • Plug-and-Play Integrations

    • Payly
  • Virtual Accounts

    • Overview
    • Create new virtual account
    • Block/Unblock virtual account
    • VA balance enquiry
    • VA statement
  • RESOURCES

    • Errors & codes
    • Collections
    • API version management
    • Bank connectivity
    • User inputs
    • POR Details
    • Error codes
  • SME Onboarding (Draft)

    • Overview (Draft)
  • API Archives


Overview

Digital bank account for SMEs powered by SingleView in partnership with Bank Albilad

info

This is a draft version of the SME Onboarding APIs. The final version is expected to be released by the end of September. The API specifications are subjected to go through a few more changes before the final version is released.

SingleView SME Onboarding enables digital channels to onboard eligible SME customers and open business accounts with Bank Albilad in the Kingdom of Saudi Arabia.

SingleView provides the API integration layer through which approved digital channels can access the services required for SME onboarding.

The APIs support the key stages of the onboarding journey, including customer OTP verification, customer validation, user management, Nafath identity verification, retrieval of onboarding reference data, and SME account creation.

Onboarding flow

  • Generate OTP
    The journey starts by generating an OTP for the customer.
  • Validate Customer
    The customer's identity and SME information are validated using the required identification, unified number, date of birth, mobile number, and OTP details.
  • Manage User
    A digital user profile is created and the customer defines credentials such as the Pass Code and Security PIN.
  • Nafath Call Status
    Verify Nafath call status before initiating Nafath verification journey.
  • Initiate Nafath Verification
    The customer is directed through the Nafath identity-verification journey. The integration initiates the request and subsequently checks its status.
  • Nafath Verification Status
    Check status of Nafath verification before proceeding to creation of account.
  • List of Values
    Reference data for industry and sector retrieved on demand whenever required by an onboarding screen.
  • Create SME Account
    After successful verification, the validated customer and business information is submitted to create the SME account.
  • Registration completed
    A successful account-creation response marks the onboarding journey as completed.
  • Callback
    A configured callback can be used to notify the consuming application after account creation.

Prerequisites

Before integrating the APIs, ensure that you have:

Integration requirements

  • An approved SingleView integration
  • Valid API authorization credentials
  • A CompanyId assigned for the integration
  • A mechanism for generating and maintaining the required Signature
  • Access to the appropriate SingleView environment
  • A secure server-side environment for making API requests

Authentication overview

All API requests must be authenticated using the credentials and security mechanism provided during the SingleView integration. Requests use common headers such as:

Header

Description

SVReferenceID

Unique identifier used to track the API transaction

CompanyId

Identifier assigned to the client by SingleView

Device

Channel or device initiating the request to be mentioned as web

DateTimeStamp

Request timestamp in ISO 8601 format YYYY-MM-DDTHH:mm:ssZ

Authorization

API authorization token (Access token)

Updated September 1, 2026

Was this helpful?