# reimbursements.bindRecipient

Bind an existing Wise recipient to an active member after verifying its name, currency and business profile. No bank details are returned.

`POST /api/v1/accounting/reimbursements.bindRecipient`

Permissions: `accounting:read`, `accounting:write`, `accounting:admin` · Roles: admin · Idempotency key required · Send `expectedRevision`

MCP tool: `accounting_reimbursements_bind_recipient`

## Fields

| Field | Type | Required | Notes |
| --- | --- | --- | --- |
| `userId` | string | Yes | The ID of a person in your company. 1–200 characters. |
| `currency` | string | Yes | Three-letter currency code, such as CAD or USD. |
| `recipientId` | string | Yes | The ID of one signer on a document. Matches ^\d{1,30}$. |
| `holderName` | string | Yes | 2–200 characters. |
| `identityMismatchConfirmed` | boolean |  |  |
| `identityMismatchReason` | string |  | 10–1000 characters. |
| `expectedRevision` | integer | Yes | The record's current revision, from the last time you read it. If someone changed the record since, the request is refused with a conflict so you can reload and check before trying again. 0 to 9007199254740991. |
| `idempotencyKey` | string | Yes | Any unique text you generate once per intended change, so a retried request only happens once. Send it as the Idempotency-Key header instead if you prefer; if you send both they must match. 8–200 characters. |

## Example request

```bash
curl https://app.getoatmilk.com/api/v1/accounting/reimbursements.bindRecipient \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "userId": "example",
  "currency": "CAD",
  "recipientId": "1250",
  "holderName": "Synthetic Ventures Inc.",
  "expectedRevision": 3
}'
```

Reference page: https://app.getoatmilk.com/docs/api/reimbursements.bindRecipient