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
  • RESOURCES

    • POR Details
    • Error codes
    • Errors & codes
    • Collections
    • API version management
    • Bank connectivity
  • API Archives


Make test data use case API call

Learn how to transform customer-permissioned banking data into actionable insights using SingleView Data Use Case APIs

Data Use Case APIs build upon Open Banking data to deliver business-ready outputs that support onboarding, verification, risk assessment, lending, personal finance, and compliance workflows.

Unlike Raw Data APIs, which provide direct access to banking information, Data Use Case APIs process and analyze financial data to generate meaningful results that can be integrated directly into business applications.

Prerequisites

Before making a Data Use Case API request, ensure that you have:

  • Created a Console account
  • Configured your application
  • Established a secure connection
  • Generated the required authentication credentials

Data Retrieval Flow

The following workflow illustrates a typical Data Use Case API journey:

Create Consent
↓
Customer Authorizes Consent
↓
Retrieve Consent Details
↓
Select Data Use Case Service
↓
Make API Request
↓
Receive Banking Data

Step 1: Create and Authorize a Consent

Open Banking data can only be accessed after obtaining explicit customer consent.

To create a consent:

  1. Submit a Create Consent request
  2. Define the permissions required by your application
  3. Specify the consent validity period
  4. Redirect the customer to complete authorization
  5. Verify that the consent status is Authorized
Outcome

An active consent that permits access to the data required for the selected use case.

Step 2: Retrieve Consent Details

Before making a data request, confirm that the consent is valid and active.

Use the Retrieve Consent Details endpoint to:

  • Verify consent status
  • Confirm granted permissions
  • Validate consent expiration
Outcome

Confirmation that the requested data can be accessed.

Step 3: Make a Data Use Case API Request

Once consent has been authorized, you can request one of the available Data Use Case services.

The following use cases are available:

  • 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 Response

A successful request returns processed insights based on the customer's authorized banking data.

The response may include:

  • Verification results
  • Financial indicators
  • Account summaries
  • Spending insights
  • Income analysis
  • Enriched transaction information

The information returned depends on the selected use case and the permissions granted through customer consent.

Updated July 2, 2026

Was this helpful?