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

# Resolve a customer name

> Resolves the customer name on an electricity meter or cable smartcard
before you take payment. Electricity purchases fail with
`422 NAME_ENQUIRY_REQUIRED` until this has succeeded for the same
meter number and `service_type`. Cable TV does not enforce it, but
you should still run it when the provider requires a validated customer.
Requires a Bills Payment subscription.




## OpenAPI

````yaml /openapi.yaml post /services/bills-payment/name-enquiry
openapi: 3.1.0
info:
  title: Rex Banking-as-a-Service API
  version: 1.0.0
  summary: Embed real bank accounts, transfers, and collections into your product.
  description: |
    The Rex BaaS API lets you provision virtual bank accounts, move money
    between them, accept inbound transfers, collect at merchant terminals, and
    pay bills for your end customers — all under your own brand, backed by a
    real bank ledger.

    This reference covers every endpoint your integration will call. If
    you're just getting started, read **[Getting Started](/introduction)**
    and **[Authentication](/authentication)** first — most integration
    questions are answered there, not in the endpoint list.

    All endpoints are versioned under `/baas/api/v1` and return JSON. See
    **[Errors](/errors)** for the shared error envelope, and
    **[Sandbox vs. Live](/guides/sandbox-vs-live)** for how test and
    production credentials differ.
  contact:
    name: Rex BaaS Support
    email: baas-support@rexmfbank.com
  license:
    name: Proprietary — for approved Rex BaaS partners only
servers:
  - url: https://api.rexmfbank.com/baas/api/v1
    description: Rex BaaS API
security:
  - BearerAuth: []
tags:
  - name: Authentication
    description: Register a partner account, verify it, log in, and manage credentials.
  - name: Onboarding
    description: |
      The one-time KYB (Know Your Business) flow every partner completes
      before going live — business details, a compliance representative,
      supporting documents, and signing the partner agreement.
  - name: Wallet
    description: >-
      Your business's own settlement balance — the account every virtual account
      nets into.
  - name: Virtual Accounts
    description: |
      The core product — dedicated bank account numbers you issue to your
      own end users, with full transfer and transaction capabilities.
  - name: Webhooks
    description: Configure where and how Rex notifies your system of events in real time.
  - name: Partner Settings
    description: >-
      Account security, team members, disputes, and document management for your
      own partner account.
  - name: Services
    description: |
      The catalog of optional products a partner can subscribe to. Virtual
      accounts are not in this list — they are available without a
      subscription. Bills payment is.
  - name: Bills Payment
    description: |
      Buy airtime, data, electricity, and cable TV for your end customers.
      Each purchase debits your own Master account. Requires a Bills Payment
      subscription — see **[Services](/guides/service-subscriptions)**.
paths:
  /services/bills-payment/name-enquiry:
    post:
      tags:
        - Bills Payment
      summary: Resolve a customer name
      description: |
        Resolves the customer name on an electricity meter or cable smartcard
        before you take payment. Electricity purchases fail with
        `422 NAME_ENQUIRY_REQUIRED` until this has succeeded for the same
        meter number and `service_type`. Cable TV does not enforce it, but
        you should still run it when the provider requires a validated customer.
        Requires a Bills Payment subscription.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - account_number
                - service_type
                - type
              properties:
                account_number:
                  type: string
                  minLength: 5
                  maxLength: 50
                  description: Meter number or smartcard number.
                service_type:
                  type: string
                  maxLength: 150
                  description: Provider or disco code
                  for example `IKEDC` or `DSTV`.: null
                type:
                  type: string
                  enum:
                    - electricity
                    - cable
                    - jamb
                    - waec
                    - betting
            example:
              account_number: '1234567890'
              service_type: IKEDC
              type: electricity
      responses:
        '200':
          description: OK
          content:
            application/json:
              example:
                status: success
                message: Name lookup completed successfully.
                data:
                  resolved_name: CUSTOMER NAME
        '403':
          description: '`NOT_SUBSCRIBED`'
        '422':
          description: >-
            `NAME_LOOKUP_FAILED` — details did not resolve; provider payload may
            be in `data`. Or `VALIDATION_FAILED`.
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: sk_live_... / sk_sandbox_...
      description: |
        See **[Authentication](/authentication)** for the full explanation
        of session tokens vs. API keys and when each is used.

````