> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useduro.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Resolve an account name

> Returns the account holder name for a bank code + 10-digit account number. Live mode uses a real bank lookup; test mode returns a deterministic mock name.



## OpenAPI

````yaml /openapi.json post /v1/payouts/banks/resolve
openapi: 3.1.0
info:
  title: Duro API
  version: 1.0.0
  description: >-
    Recovery-first subscription billing. Authenticate with a secret key
    (sk_test_ / sk_live_) as a bearer token. Amounts are in integer minor units
    (kobo).
servers:
  - url: https://api.useduro.com
    description: >-
      One base URL for both modes. The key prefix selects the mode: sk_test_… is
      test, sk_live_… is live. You never switch hosts or pass a mode parameter.
security:
  - bearerAuth: []
tags:
  - name: Plans
  - name: Promo Codes
  - name: Payment Links
  - name: Customers
  - name: Transactions
  - name: Subscriptions
  - name: Invoices
  - name: Recovery
  - name: Settings
  - name: Analytics
  - name: Checkout
  - name: Events
  - name: Merchant Balance
  - name: Payouts
  - name: VAS
  - name: OAuth
paths:
  /v1/payouts/banks/resolve:
    post:
      tags:
        - Payouts
      summary: Resolve an account name
      description: >-
        Returns the account holder name for a bank code + 10-digit account
        number. Live mode uses a real bank lookup; test mode returns a
        deterministic mock name.
      operationId: resolvePayoutAccount
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - bankCode
                - accountNumber
              properties:
                bankCode:
                  type: string
                accountNumber:
                  type: string
                  pattern: ^\d{10}$
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
                properties:
                  accountName:
                    type: string
        '400':
          $ref: '#/components/responses/Validation'
components:
  responses:
    Validation:
      description: Validation error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
            details:
              type: array
              items:
                type: object
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Paste your secret key as the bearer token: sk_test_… (test) or sk_live_…
        (live). That is all a normal API call needs. OAuth access tokens from
        POST /v1/oauth/token also work, but a client id/secret is only for
        platforms acting on another tenant's behalf, not for your own
        integration.

````