For the complete documentation index, see llms.txt. This page is also available as Markdown.

Account requisites

Retrieves detailed account requisites report for a specific account. This endpoint provides comprehensive banking and account information for customer reference and payment processing.

Endpoint: GET /v2/report/account/{accountId}

Request

Path Parameters

Parameter

Type

Description

Required

Example

accountId

string

Account ID to generate requisites for.

Yes

"U5aTFci52DRo"

Query Parameters

Parameter

Type

Description

Required

Allowed Values

Default

option.format

string

Output format for the report.

No

Unknown, PDF, XLSX

Unknown

Headers

Key

Value

Required

Authorization

Bearer <JWT>

Yes

Accept

application/json or format-specific

Yes


Response (200 OK)

Returns the account requisites report in the requested format, either as base64-encoded data or raw file content.

Response Fields

Field

Type

Description

Example

data

string

Report content as base64-encoded bytes or raw data.

"JVBERi0xLjQK..."

name

string

Report file name.

"account_requisites_ACC123456789_20240522.pdf"

Typical Report Content

Account requisites reports typically include:

Account Information

  • Account holder name

  • Account number

  • Account type

  • Currency

  • Account status

  • Creation date

Banking Details

  • Bank name

  • Bank address

  • SWIFT/BIC code

  • ABA/Routing number

  • IBAN (for international accounts)

  • Bank code

Contact Information

  • Customer contact details

  • Customer address

  • Phone number

  • Email address

Compliance Information

  • Tax identification number

  • Regulatory information

  • Compliance status


Error Responses

  1. Account Not Found:

    json

  2. Unauthorized:

    json

  3. Invalid Format:

    json

  4. Access Denied:

    json


Notes

  • Format Options:

    • PDF: Professional document format suitable for printing and official documentation

    • XLSX: Spreadsheet format for data analysis and integration with financial software

    • Unknown: Default JSON format with base64-encoded data

  • File Naming Convention: account_requisites_{accountId}_{timestamp}.{extension}

  • Data Security:

    • Sensitive banking information is protected

    • Access restricted to authorized users only

    • Secure transmission of financial data

  • Usage Scenarios:

    • Customer account documentation

    • Payment instruction sharing with third parties

    • Compliance and audit requirements

    • Account verification processes

    • International wire transfer setup

Common Use Cases:

  • Providing account details for wire transfers

  • Sharing banking information with business partners

  • Compliance documentation for regulators

  • Customer self-service account information

  • Integration with accounting systems

Format Recommendations:

  • PDF: For official documents and printing

  • XLSX: For data processing and analysis

  • JSON: For API integration and automation

Examples

Real request

Real response

File example:

Requisites sample list

Last updated