Lean Technologies Beneficiary Name Verification API
Beneficiary name retrieval operations
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/lean-technologies-beneficiary-name-verification-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Lean Beneficiary Name Verification API
description: API for retrieving beneficiary name from an IBAN
version: v2.0.0
servers:
- url: https://sandbox.sa.leantech.me
description: Sandbox
- url: https://api2.sa.leantech.me
description: Production
security:
- bearerAuth: []
tags:
- name: Beneficiary Name Verification
description: Beneficiary name retrieval operations
x-displayName: Beneficiary Name Verification
paths:
/verifications/v2/beneficiary-name:
servers: []
post:
operationId: beneficiaryNameVerification
summary: Get Beneficiary Name
description: Retrieves the beneficiary name and account status for a given IBAN
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/BeneficiaryNameRequest'
example:
iban: SA2810000011100000461309
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/VerificationResponseBeneficiaryNamePayload'
examples:
'1':
summary: Success - Active account
value:
status: OK
results_id: d2d95011-f834-4979-83eb-9c35b95f093c
message: Data successfully retrieved
timestamp: '2025-07-25T11:01:04.709087696Z'
meta: null
status_detail: null
verifications:
beneficiary_name: JON DOE
account_status: ACTIVE
'2':
summary: Success - Blocked account
value:
status: OK
results_id: e894ede4-dd81-41fb-b52d-fb4fec16c16c
message: Data successfully retrieved
timestamp: '2025-05-19T12:09:54.672818827Z'
meta: null
status_detail: null
verifications:
beneficiary_name: JON DOE
account_status: BLOCKED
'3':
summary: Failed - Unsupported by bank
value:
status: FAILED
results_id: f894ede4-dd81-41fb-b52d-fb4fec16c16c
message: Beneficiary Name Verification Failed
timestamp: '2024-04-30T07:54:25.224020260Z'
status_detail:
granular_status_code: UNSUPPORTED_BY_BANK
status_additional_info: This endpoint is currently not supported for this bank.
'4':
summary: Failed - Bank issue
value:
status: FAILED
results_id: f894ede4-dd81-41fb-b52d-fb4fec16c16c
message: Beneficiary Name Verification Failed
timestamp: '2024-04-30T07:54:25.224020260Z'
status_detail:
granular_status_code: BANK_ISSUE
status_additional_info: Your bank is currently experiencing technological problems. Please try again later.
'400':
description: Bad Request - Invalid parameters
content:
application/json:
examples:
InvalidIbanExample:
summary: Invalid IBAN format
value:
timestamp: '2025-07-25T11:01:04.709087696Z'
status: INVALID_PARAMETERS
message: The request provided invalid parameters.
metadata: null
'403':
description: Forbidden
content:
application/json:
examples:
ForbiddenExample:
summary: Operation not allowed
value:
timestamp: '2025-07-25T11:01:04.709087696Z'
status: OPERATION_NOT_ALLOWED
message: You are not allowed to do this operation
metadata: null
tags:
- Beneficiary Name Verification
components:
schemas:
ResultStatus:
description: The status of the request
type: string
enum:
- OK
- PENDING
- FAILED
- CONSENT_EXPIRED
- PROCESSING_STARTED
Result:
type: object
properties:
status:
$ref: '#/components/schemas/ResultStatus'
results_id:
description: The unique identifier for the request
type: string
format: uuid
message:
description: A message describing the status of the request
type: string
meta:
description: Meta information about the request
type:
- object
- 'null'
additionalProperties:
type: string
timestamp:
description: The datetime of when the request was made
type: string
format: date-time
status_detail:
description: Additional information about the status
type:
- object
- 'null'
allOf:
- $ref: '#/components/schemas/StatusDetail'
required:
- status
- results_id
- message
- timestamp
BeneficiaryNamePayload:
description: Beneficiary name and account status retrieved from the bank
type: object
properties:
beneficiary_name:
description: Name of the account holder
type: string
account_status:
description: Status of the bank account
type: string
required:
- beneficiary_name
- account_status
BeneficiaryNameRequest:
type: object
properties:
iban:
description: International Bank Account Number to retrieve beneficiary name for
type: string
required:
- iban
StatusDetail:
type:
- object
- 'null'
properties:
granular_status_code:
description: Granular status code
type:
- string
- 'null'
status_additional_info:
description: Additional information about the status
type:
- string
- 'null'
VerificationResponseBeneficiaryNamePayload:
allOf:
- $ref: '#/components/schemas/Result'
- type: object
properties:
verifications:
$ref: '#/components/schemas/BeneficiaryNamePayload'
securitySchemes:
bearerAuth:
type: http
scheme: bearer