Back to neotek ↗Get Sandbox Access

Explore Our Products

Each product is called with a scope. Request it when you generate a token, and make sure your app is subscribed to the product in the environment you are calling. Open Banking and premium products take a scope each; the B2B Unified products share one.

One token can cover several products — separate their scopes with spaces, for example e_statement single_api.


Open Banking products

These read the customer's bank data, so each one needs an Accounts Link created and consented before you call it. See Open Banking Prerequisites, and Configuring Your Open Banking App for the one-time app setup.

Each product has its own scope, listed below. Request the scope for every product you intend to call, separated by spaces — for example e_statement single_api.

ProductScope
Single APIsingle_api
Income Verificationincome_verification
E-Statemente_statement
Average Balanceaverage_balance
Account Insightsaccount_insights
Credit Profilingcredit_profile_assessment
Cash Flowcashflow

Premium products

These do not read consented bank data, so they need no Accounts Link and no consent flow — just a token with the right scope.

ProductScope
IBAN Verificationiban_verification
National Address Verificationnational_address
Financial Statementqawaem_establishment_information
Digital Signaturedigital_signature
Establishment Detailsestablishment_information

B2B Unified products

These front multiple Saudi banks behind one REST API. Like the premium products they read no consented bank data, so they need no Accounts Link and no consent flow.

One scope covers all of them: b2b_unified. Unlike the products above, these do not take a scope each — request b2b_unified once and it covers every product in this table. You still need a subscription per product in the environment you are calling.

ProductScope
Paymentsb2b_unified
Statementsb2b_unified
Analyticsb2b_unified
Payrollb2b_unified
SADADb2b_unified
MOIb2b_unified
Virtual IBANb2b_unified