> ## Documentation Index > Fetch the complete documentation index at: https://developer.finogates.com/llms.txt > Use this file to discover all available pages before exploring further. # Apply for Virtual Bank Account > Apply for a virtual bank account (a "Virtual Account") for one of your users. A virtual bank account gives the user their own account number and routing number for receiving money. **Before this works** — the request is turned down unless all of these are true: - Your platform has the virtual bank account product (``virtual_account``) switched on. You ask for it during the normal sign-up process, and Finogate's team must approve that request first. - Your platform has completed its own identity and business verification (an approved platform-level KYC and KYB). - The user has passed identity verification (an approved KYC record). - The user has passed business verification (at least one approved KYB record). **What happens next** — the account starts in the ``initiated`` state. Finogate's team reviews every application by hand, marks it ``applied`` once checked, and finally fills in the real account and routing numbers from the banking partner before setting the account to ``approved``. We tell you the result by sending your server an automatic notification — a ``virtual_bank_account.approved`` webhook if it succeeds, or a ``virtual_bank_account.rejected`` webhook if it is declined. That notification is the only sign that the account is ready. **Until the account is ``approved``, it must not be used for any payments, payouts, deposits, or linked to a wallet.** **Avoiding duplicates** — there are two safeguards: - You can include an ``idempotency_key`` — a unique value you choose. If the same request reaches us twice by mistake, the account is only created once. (Reusing the same key with different details is rejected.) - The same user cannot hold two active accounts of the same type on your platform. A repeat attempt is rejected. ## OpenAPI ````yaml POST /v1/platform/virtual-bank-accounts openapi: 3.1.0 info: title: Finogate Platform API v1 version: 0.1.0 servers: - url: https://api-sandbox.finogates.com description: Sandbox - url: https://api.finogates.com description: Production security: [] tags: - name: auth - name: users - name: payees - name: verification - name: bank accounts - name: card processing - name: digital-assets - name: international - name: onboarding - name: pending-applications - name: wallets - name: payments - name: catalog - name: webhooks - name: phone-numbers - name: sms - name: calls - name: listings - name: embed-tokens paths: /v1/platform/virtual-bank-accounts: post: tags: - bank accounts summary: Apply for Virtual Bank Account description: >- Apply for a virtual bank account (a "Virtual Account") for one of your users. A virtual bank account gives the user their own account number and routing number for receiving money. **Before this works** — the request is turned down unless all of these are true: - Your platform has the virtual bank account product (``virtual_account``) switched on. You ask for it during the normal sign-up process, and Finogate's team must approve that request first. - Your platform has completed its own identity and business verification (an approved platform-level KYC and KYB). - The user has passed identity verification (an approved KYC record). - The user has passed business verification (at least one approved KYB record). **What happens next** — the account starts in the ``initiated`` state. Finogate's team reviews every application by hand, marks it ``applied`` once checked, and finally fills in the real account and routing numbers from the banking partner before setting the account to ``approved``. We tell you the result by sending your server an automatic notification — a ``virtual_bank_account.approved`` webhook if it succeeds, or a ``virtual_bank_account.rejected`` webhook if it is declined. That notification is the only sign that the account is ready. **Until the account is ``approved``, it must not be used for any payments, payouts, deposits, or linked to a wallet.** **Avoiding duplicates** — there are two safeguards: - You can include an ``idempotency_key`` — a unique value you choose. If the same request reaches us twice by mistake, the account is only created once. (Reusing the same key with different details is rejected.) - The same user cannot hold two active accounts of the same type on your platform. A repeat attempt is rejected. operationId: create_virtual_bank_account_v1_platform_virtual_bank_accounts_post requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/PlatformVirtualBankAccountCreate' responses: '201': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/CommonResponse' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - _AuthenticatedBearer: [] components: schemas: PlatformVirtualBankAccountCreate: properties: user_id: type: string format: uuid title: User Id description: End user the virtual bank account is opened for. examples: - 0b87f3a8-5a1f-4f5d-9f34-0f1a4c2d7a63 nickname: type: string maxLength: 100 minLength: 1 title: Nickname description: Human-friendly account label. examples: - Primary Business Account account_type: $ref: '#/components/schemas/VirtualBankAccountType' description: Account product to open (BUSINESS / SAVINGS / CHECKING). default: BUSINESS idempotency_key: anyOf: - type: string maxLength: 120 - type: 'null' title: Idempotency Key description: Optional caller-supplied idempotency key. metadata: additionalProperties: true type: object title: Metadata description: Optional integrator-supplied metadata. type: object required: - user_id - nickname title: PlatformVirtualBankAccountCreate description: >- Public platform request shape for ``POST /platform/virtual-bank-accounts``. Field aliases accept both the spec-style camelCase (``userID``) and the canonical snake_case so integrators can use whichever they prefer; documentation should standardise on snake_case. examples: - nickname: Primary Business Account userID: usr_123456 CommonResponse: properties: status_code: type: integer title: Status Code description: HTTP status code for the response. data: title: Data description: Payload or error details. query_generated_time: type: integer title: Query Generated Time description: >- UTC timestamp (milliseconds since epoch) when response was generated. type: object required: - status_code - data - query_generated_time title: CommonResponse description: |- Standard response wrapper for single-object responses and errors. Generic over the payload type. A route that declares ``CommonResponse[SomeModel]`` gets the real ``data`` schema rendered in OpenAPI/Swagger; a bare ``CommonResponse`` leaves ``data`` untyped. HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError VirtualBankAccountType: type: string enum: - BUSINESS - SAVINGS - CHECKING title: VirtualBankAccountType description: |- Account product for virtual bank accounts. Provider-neutral classification of the issued account. KYC + KYB are both mandatory and the account stays gated until both pass. The value is a Finogate-side label — a Checkbook Enhanced Wallet receives ACH/RTP account + routing numbers regardless of this type. ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: _AuthenticatedBearer: type: oauth2 flows: password: scopes: {} tokenUrl: /v1/platform/auth/token ````