Open BankingB2B SuiteERP Integration
GuidesAPI ReferenceChangelog
Menu

Categories

Open BankingB2B SuiteERP Integration

  • GENERAL INFORMATION

    • Documentation guide
    • SingleView Open Banking
    • KSAOB standards
    • Security best practices
  • GETTING STARTED

    • Integration guide
    • Developer console
    • Establish secure connection
    • Generate access token
    • Make test raw data API call
    • Make test data use case API call
  • CONSENT MANAGEMENT

    • Overview
    • Create a consent
    • Retrieve consent details
    • Revoke a consent
  • Raw Data APIs

    • Introduction
    • View accounts
    • View balance
    • View transactions
    • Identify account holders (Parties)
    • Review direct debits
    • Review scheduled payments
    • Review standing orders
  • DATA USE CASE APIS

  • Plug-and-Play Integrations

    • Payly
  • RESOURCES

    • Errors & codes
    • Collections
    • API version management
    • Bank connectivity
  • API Archives


Integration guide

Follow a step-by-step journey to securely integrate with SingleView Open Banking APIs

This guide provides a structured overview of the integration process required to connect to SingleView Open Banking APIs. By following the steps outlined below, you will be able to establish a secure connection, authenticate requests, and access Open Banking data and services.

Integration Journey

The integration process consists of five key stages:

Step 1: Create a Console Account

The SingleView Console serves as the primary interface for managing your Open Banking integration. Before accessing any APIs, you must create and configure a console account.

Through the Console, you can:

  • Register and manage applications
  • Configure application settings
  • Manage API credentials
  • Monitor integration activity
  • Control user access and permissions
Expected outcome

A configured Console account with an application ready for integration.

Step 2: Establish a Secure Connection

SingleView APIs are accessible only through secure communication channels. Prior to making API requests, you must configure the required connectivity and security settings.

This includes:

  • Configuring mTLS connections
  • Registering and validating certificates where applicable
  • Verifying connectivity to the target environment
  • Ensuring compliance with security requirements
Expected outcome

A secure communication channel established between your application and the SingleView platform.

Step 3: Generate Authentication Credentials

All API requests must be authenticated and authorized in accordance with SingleView security requirements.

Depending on the API and environment, authentication may involve:

  • Obtaining access tokens
  • Including required authentication headers
  • Managing token lifecycle and expiration
Expected outcome

The ability to successfully authenticate and authorize API requests.

Step 4: Perform a Test Raw Data API Request

Once connectivity and authentication have been configured, you can validate your integration by accessing Open Banking data through the Raw Data APIs.

A typical workflow includes:

  1. Creating a consent
  2. Authorizing the consent
  3. Accessing customer banking data

Raw Data APIs provide access to:

  • Accounts
  • Balances
  • Transactions
  • Parties
  • Direct Debits
  • Scheduled Payments
  • Standing Orders
Expected outcome

Successful retrieval of customer-permissioned banking data under Open Banking Raw Data API services.

Step 5: Perform a Test Data Use Case API Request

Following successful validation of the Raw Data APIs, you may begin utilizing SingleView's data products and business use case APIs.

These services transform raw banking data into actionable insights that can support onboarding, verification, risk assessment, lending, and personal finance use cases.

A typical workflow includes:

  1. Creating a consent
  2. Authorizing the consent
  3. Accessing customer banking data

Available use cases include:

  • Build Financial Insights
    • Aggregate accounts
    • Generate E-Statement
  • Verify customers & accounts
    • Verify customer identity
    • Verify account ownership (Account Check)
    • Validate IBAN
    • Complete KYC check
  • Assess financial position
    • Review available balances
    • Assess income
    • Assess expenses
    • Evaluate creditworthiness
Expected outcome

Successful retrieval of customer-permissioned banking data under Open Banking Data API Use Cases services.

Next Steps

After completing the integration journey outlined above, you may proceed with:

  • Expanding your implementation to additional APIs
  • Performing end-to-end testing in the sandbox environment
  • Configuring production environments
  • Preparing for go-live

For detailed implementation instructions, refer to the relevant sections of this documentation.

Updated July 2, 2026

PreviousSecurity best practicesNextDeveloper console
Was this helpful?