Skip to main content
PUT
Replace beneficiary PII

Authorizations

DPoP
string
header
required

Per-request DPoP proof JWT (RFC 9449). MUST accompany the Authorization: DPoP <access_token> header on every protected operation. The proof is signed by the merchant's private DPoP key and carries htm, htu, iat, jti, and ath claims.

Headers

Idempotency-Key
string
required

Unique key identifying this operation. Sending the same key twice returns the original response instead of creating a duplicate. Keys are retained for 24 hours.

Maximum string length: 255

Path Parameters

id
string
required
Pattern: ^ben_[a-zA-Z0-9]+$

Body

application/json

Replacement PII. Provide the detail block matching the beneficiary's type. The entire PII blob is replaced — partial updates are not supported.

individual
object

PII for an individual beneficiary. Tokenized on creation.

business
object

PII for a business beneficiary. Tokenized on creation.

end_user_ip
string

Response

Beneficiary PII replaced. Returns the updated beneficiary record.

data
object
required

A person or business you pay. PII is tokenized in Basis Theory on creation — raw identifiers are never returned in this response. Use GET /v1/beneficiaries/{id}/pii to retrieve detokenized PII for a beneficiary you own.

Example: