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

# Get merchant balance

> Returns the balances on **your own** merchant wallet, as opposed to `GET /v1/wallet`, which answers for one of your customers.

This is the account Payluk settles your earnings into: your share of every escrow fee, and any delivery fee you charged a buyer. Your customers' balances are their own and are never included here.

Must **not** carry a `customer-id` header. Sending one is rejected rather than silently answered for that customer.



## OpenAPI

````yaml openapi.json GET /v1/merchant/balance
openapi: 3.0.3
info:
  title: Payluk ThirdParty API
  version: 1.0.0
  description: >-
    Merchant / Business API for the Payluk escrow and payments platform.


    All routes are mounted under `/v1` and authenticated with a secret key.
    Every response uses the standard envelope `{ status, message, data }`.
  contact:
    name: Payluk Developer Support
    email: support@payluk.ng
    url: https://payluk.ng
servers:
  - url: https://staging.api.payluk.ng
    description: 'Staging: use sk_test_ keys here for safe testing'
  - url: https://api.payluk.ng
    description: 'Production: use sk_live_ keys'
security:
  - bearerAuth: []
tags:
  - name: Escrow
    description: Create and manage standard escrow payment links.
  - name: Milestone Escrow
    description: Escrows that release funds in parts as milestones are confirmed.
  - name: Vault Escrow
    description: >-
      Merchant-only pooled-stake escrows: customers stake from their wallets and
      the merchant declares the winner.
  - name: Categories
    description: Organise escrows into merchant-defined categories.
  - name: Merchant Customers
    description: Manage the buyers and sellers that transact under your merchant account.
  - name: Merchant Account
    description: Your own balance and ledger, as distinct from your customers’.
  - name: Disputes
    description: Confirm deliveries, raise disputes and resolve them.
  - name: Payments
    description: Fund wallets and escrows, verify references and manage payout details.
  - name: Debit Cards
    description: List and remove customers' saved debit cards.
  - name: Crypto Whitelist
    description: Manage whitelisted crypto withdrawal addresses.
  - name: Misc
    description: Supporting reference data.
paths:
  /v1/merchant/balance:
    get:
      tags:
        - Merchant Account
      summary: Get merchant balance
      description: >-
        Returns the balances on **your own** merchant wallet, as opposed to `GET
        /v1/wallet`, which answers for one of your customers.


        This is the account Payluk settles your earnings into: your share of
        every escrow fee, and any delivery fee you charged a buyer. Your
        customers' balances are their own and are never included here.


        Must **not** carry a `customer-id` header. Sending one is rejected
        rather than silently answered for that customer.
      operationId: getMerchantBalance
      responses:
        '200':
          description: Merchant balance fetched.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WalletResponse'
              example:
                status: 200
                message: Merchant balance fetched successfully
                data:
                  id: 6a19b580fa797d3af379ca30
                  mainBalance: 250000
                  escrowBalance: 0
                  currency: NG
                  createdAt: '2026-01-14T09:12:03.041Z'
                  updatedAt: '2026-08-22T18:04:55.219Z'
        '400':
          description: >-
            A `customer-id` header was supplied. This endpoint answers only for
            the merchant.
          content:
            application/json:
              example:
                status: 400
                message: customer-id is not allowed in request header
                data: null
components:
  schemas:
    WalletResponse:
      type: object
      properties:
        status:
          type: integer
          example: 200
        message:
          type: string
          example: Wallet fetched successfully
        data:
          type: object
          properties:
            mainBalance:
              type: integer
              example: 50000
            escrowBalance:
              type: integer
              example: 1000000
            currency:
              type: string
              example: NGN
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Your secret key as a Bearer token. The key prefix selects the
        environment: `sk_test_...` (test) or `sk_live_...` (live).

````