> ## Documentation Index > Fetch the complete documentation index at: https://guides.saber.money/llms.txt > Use this file to discover all available pages before exploring further. # Get Beneficiary Details (v1) > API allows you to retrieve beneficiary information required for processing payments. The API supports multiple payment methods, which can be specified in the **path parameter "payment_method"** If the payment method is set to "**upi_transfer**," the API will provide the UPI details of the beneficiary. Additionally, a unique verification code will be included, which the user needs to add while making the payment. This verification code is important for reconciling the payment on the system's end, ensuring accurate tracking and processing. If the payment method is set to "**bank_transfer**," the API will return the bank details of the beneficiary. These details can be used to initiate a bank transfer payment. ## OpenAPI ````yaml /openapi-v1.json get /api/v1/wallet/conversion/fiat/methods/bank_transfer/beneficiary openapi: 3.1.0 info: title: Saber Money API (v1) version: v1 description: >- ## Authentication There is no standalone API-key auth — every request must be **signed**. An API key by itself authenticates nothing. Each call requires four headers together: `X-Api-Key` (your key), `X-Signature` (HMAC-SHA256 of `apiKey + timestamp` — or `apiKey + timestamp + userId` when `X-User-Id` is required — keyed with your API secret), `X-Timestamp` (unix seconds), and `X-Request-Id` (any unique string per request). The signature must be computed by a client script; there is no way to derive it by hand. Use the HMAC Generator flow to compute valid values for manual testing. ## Common Authentication Errors - **Invalid Client ID**: {"error_code":6092,"message":"X-Client-Id invalid","success":false} - **Invalid Secret**: {"error_code":6090,"message":"invalid secret","success":false} - **Timestamp (Older than 10 secs)**: {"errors":{"error_code":6093,"text":"timestamp expired"},"success":false} servers: - url: https://api.saber.money security: [] paths: /api/v1/wallet/conversion/fiat/methods/bank_transfer/beneficiary: get: tags: - Onramp summary: Get Beneficiary Details (v1) description: > API allows you to retrieve beneficiary information required for processing payments. The API supports multiple payment methods, which can be specified in the **path parameter "payment_method"** If the payment method is set to "**upi_transfer**," the API will provide the UPI details of the beneficiary. Additionally, a unique verification code will be included, which the user needs to add while making the payment. This verification code is important for reconciling the payment on the system's end, ensuring accurate tracking and processing. If the payment method is set to "**bank_transfer**," the API will return the bank details of the beneficiary. These details can be used to initiate a bank transfer payment. operationId: get-beneficiary-details-v1 parameters: - name: type in: query required: true description: The type parameter schema: type: string description: The type parameter - name: fiat in: query required: true description: The fiat parameter schema: type: string description: The fiat parameter - name: crypto in: query required: true description: The crypto parameter schema: type: string description: The crypto parameter - name: X-Api-Key in: header required: true description: Your API key (configured in credentials) schema: type: string - name: X-Signature in: header required: true description: >- HMAC-SHA256 signature (auto-generated) To test manually: HMAC-SHA256 of `apiKey + timestamp` (or `apiKey + timestamp + userId` when X-User-Id is required), keyed with your API secret. The HMAC Generator flow computes this for you. schema: type: string - name: X-Timestamp in: header required: true description: >- Unix timestamp in seconds (auto-generated) Unix seconds, e.g. `Math.floor(Date.now() / 1000)`. Must match the timestamp used in the X-Signature computation. schema: type: string - name: X-Request-Id in: header required: true description: >- Unique request identifier (auto-generated) Any unique string per request, e.g. a UUID. schema: type: string responses: '200': description: Successful response content: application/json: schema: type: object properties: success: type: boolean data: type: object properties: id: type: string aggregator_id: type: string bank_name: type: string ifsc_code: type: string account_number: type: string name: type: string account_type: type: - string - 'null' payment_method_id: type: - string - 'null' upi: type: - string - 'null' account_name: type: string example: success: true data: id: 15adbb9b-3593-45d8-964e-debbc3474b22 aggregator_id: b4427086-4940-4c8f-a800-98319f3277e8 bank_name: RPFAS TECHNOLOGIES PRIVATE LIMITED ifsc_code: HDFC0001234 account_number: '1234567890' name: RPFAS TECHNOLOGIES PRIVATE LIMITED account_type: CURRENT ```` ## Related topics - [Get Transaction Details (v1)](/api-reference/offramp/get-transaction-details-v1.md) - [Get User Details (v1)](/api-reference/user-operations/get-user-details-v1.md) - [Get Buy Transaction Details (v1)](/api-reference/onramp/get-buy-transaction-details-v1.md) - [Get Sell Transaction Details (v1)](/api-reference/offramp/get-sell-transaction-details-v1.md) - [Get Crypto Deposit Transaction Details (v1)](/api-reference/wallet-operations/get-crypto-deposit-transaction-details-v1.md)