Transfers addressed to a person of your team

9 November 2026 — The web app can now offer a tax ID transfer to a person of your own team, who opens a new account with the company and pays for it. Such a transfer has no secret, so a recipient_account_id of null no longer means that anyone holding the secret can accept it. The API now says who the transfer is addressed to.

• recipient_member — The transfer returned by GET /v1/accounts/{account}/nif-transfers, POST /v1/accounts/{account}/nif-transfers, POST /v1/accounts/{account}/nif-transfers/accept and POST /v1/accounts/{account}/nif-transfers/{nif_transfer}/revoke includes recipient_member: { "id": … } with the identifier of the person it is addressed to, or null. It is never set together with recipient_account_id. The API does not issue transfers to a person, so the ones you issue always return null. You can revoke a transfer to a person like any other.
• own_account — Accepting a transfer from the account that issued it answers 422 nif_transfer_invalid with error.subcode own_account and error.param secret, and the message asks you to accept it from another account. Every other case of nif_transfer_invalid still comes without a subcode.
• MCP tools — list_nif_transfers, create_nif_transfer, accept_nif_transfer and revoke_nif_transfer return the same field and the same subcode.

The change is additive and your integration keeps working. If you read recipient_account_id: null as «whoever has the secret can accept it», check recipient_member as well. The new options of the app are in Tax ID transfers in the app.