---
title: "Verify reference"
method: POST
path: "/api/fma/v1/verify-reference"
tags: ["Managed Custody Mode"]
---

# Verify reference

`POST /api/fma/v1/verify-reference`

Validate a new payment reference for an existing recent contact and get a fresh refId and purposeId to use in the payout submission.

## Headers

- `X-Api-Signature` string, required
- `X-Api-Deadline` string, required
- `X-Api-PublicKey` string, required
- `X-Ur-Id` string
- `X-External-User-Id` string

## Request body

- McVerifyReferenceRequest
  - `reference` string, required — The payment reference to validate.

## Response `200`

Standard envelope. Business errors return HTTP 200 with a non-zero code.

- McVerifyReferenceResponse — Standard UR OpenAPI response envelope. code 0 means success; a non-zero code is a business error described by message.
  - `code` integer, required — 0 on success; non-zero business error code.
  - `message` string, required — Human-readable explanation. May be empty on success.
  - `data` McPayoutRefParams
    - `contactId` string — Contact ID to use in the payout submission.
    - `purposeId` integer — Payment purpose ID.
    - `refId` string — Reference ID. Provide together with purposeId in the payout submission.

---

[API](https://skmtc.net/ur/apis/ur-api.md) · [All operations](https://skmtc.net/ur/apis/ur-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ur/ur-api/revisions/087dcf516ce2/schema)