Replace Beneficiary PII
Replaces the PII stored in Basis Theory for this beneficiary. The entire PII blob is replaced — partial updates are not supported, because tokens are immutable.
Supply the detail block matching the beneficiary’s type (individual or
business). The display_name on the beneficiary record is automatically
re-derived from the new PII.
PII is write-only for machine credentials. Your system is the source of the data, so you can deposit and replace it — but there is no companion GET on this surface: detokenized PII readback exists only in the merchant dashboard, restricted to admin users, with every access recorded in the audit log (PCI DSS 10.2.1). A leaked API credential therefore cannot harvest beneficiary identities.
Authorizations
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
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.
255Path Parameters
^ben_[a-zA-Z0-9]+$Body
Replacement PII. Provide the detail block matching the beneficiary's type. The entire PII blob is replaced — partial updates are not supported.
Response
Beneficiary PII replaced. Returns the updated beneficiary record.
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.