> ## 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.

# Register a partner account

> Creates your business's Rex BaaS partner account and sends a 6-digit
OTP to the email you provide. Verify it with **Verify Registration OTP**
before logging in — an unverified account cannot log in.




## OpenAPI

````yaml /openapi.yaml post /client/onboarding/register
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, and collect at merchant terminals —
    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: Live
  - url: https://sandbox-api.rexmfbank.com/baas/api/v1
    description: Sandbox
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.
paths:
  /client/onboarding/register:
    post:
      tags:
        - Authentication
      summary: Register a partner account
      description: |
        Creates your business's Rex BaaS partner account and sends a 6-digit
        OTP to the email you provide. Verify it with **Verify Registration OTP**
        before logging in — an unverified account cannot log in.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - business_name
                - email
                - password
                - password_confirmation
              properties:
                business_name:
                  type: string
                  maxLength: 191
                  example: Acme Payments Ltd
                email:
                  type: string
                  format: email
                  example: ops@acmepayments.com
                phone:
                  type: string
                  nullable: true
                  example: '+2348000000000'
                password:
                  type: string
                  minLength: 8
                  example: correct-horse-battery-staple
                password_confirmation:
                  type: string
                  example: correct-horse-battery-staple
      responses:
        '200':
          description: OTP sent
          content:
            application/json:
              example:
                status: success
                message: OTP sent.
                data:
                  company_id: 4821
                  email: ops@acmepayments.com
        '422':
          description: Validation failed, or the email is already registered
          content:
            application/json:
              example:
                status: error
                message: Validation failed.
                error_code: VALIDATION_FAILED
                errors:
                  email:
                    - The email has already been taken.
      security: []
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.

````