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

# Verify payment

> **Submits a previously created payment intent for processing.** Payment uses a deliberate two-step flow for security: [Create payment intent](/api-reference/payments/create-payment-intent) only stages the transaction (no money moves), and this endpoint is what actually executes it: debiting the wallet and carrying out the withdrawal, crypto transfer, card charge, or wallet transfer.

Pass the single `reference` returned when the intent was created. If the transaction requires confirmation (e.g. an SMS OTP / transaction PIN), include it as `otp`. Requires the `customer-id` header.



## OpenAPI

````yaml openapi.json POST /v1/payment/verify
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: 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/payment/verify:
    post:
      tags:
        - Payments
      summary: Verify payment
      description: >-
        **Submits a previously created payment intent for processing.** Payment
        uses a deliberate two-step flow for security: [Create payment
        intent](/api-reference/payments/create-payment-intent) only stages the
        transaction (no money moves), and this endpoint is what actually
        executes it: debiting the wallet and carrying out the withdrawal, crypto
        transfer, card charge, or wallet transfer.


        Pass the single `reference` returned when the intent was created. If the
        transaction requires confirmation (e.g. an SMS OTP / transaction PIN),
        include it as `otp`. Requires the `customer-id` header.
      operationId: verifyPayment
      parameters:
        - $ref: '#/components/parameters/CustomerIdHeader'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - reference
              properties:
                reference:
                  type: string
                  description: >-
                    The reference of the payment intent to submit for
                    processing.
                  example: '99999533334'
                otp:
                  type: string
                  description: >-
                    Confirmation OTP / transaction PIN. Required only when the
                    transaction needs confirmation.
                  example: '123456'
      responses:
        '200':
          description: Payment intent submitted and processed.
          content:
            application/json:
              example:
                status: 200
                message: Payment intent verified successfully
                data:
                  id: 6a3cea83734e96016b227460
                  amount: 1000
                  reference: t53gtryhtyut
                  fee: 0
                  transactionType: wallet_transfer
                  currency: NGN
                  transferDetails: null
                  cardId: null
                  walletDetails:
                    phone: '09022334422'
                    name: King David
                    narration: test
                  blockchainDetails: null
                  withdrawalDetails: null
                  escrowDetails: null
                  metadata: null
                  status: success
                  creditType: debit
                  createdAt: '2026-06-25T08:44:51.817Z'
                  updatedAt: '2026-06-25T08:46:39.479Z'
        '400':
          $ref: '#/components/responses/ValidationError'
components:
  parameters:
    CustomerIdHeader:
      name: customer-id
      in: header
      required: true
      description: The merchant customer this request acts on behalf of.
      schema:
        type: string
      example: 665f1b2c9a1e4d0012ab3c01
  responses:
    ValidationError:
      description: Validation error.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
          example:
            status: 400
            message: amount is required
            data: {}
  schemas:
    ApiError:
      type: object
      description: Standard error envelope.
      properties:
        status:
          type: integer
          example: 400
        message:
          type: string
          example: Action not allowed
        data:
          type: object
          example: {}
  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).

````