🖋️ Associated Person Signature (UBO Cédula)

Overview

For business users, Mexican regulation (art. 95 Bis LGOAAC) requires every Ultimate Beneficial Owner (UBO) — anyone with significant ownership or control over the business — to sign a cédula, a beneficial-owner declaration. Capa generates this document, hosts the digital signature session, and tracks its status per owner. This applies specifically to cross-ramp transactions in MXN: a business user cannot create a cross-ramp transaction involving MXN until every UBO on record has signed their cédula.

This requirement is rolled out per environment. If your account doesn’t yet require it, Request Beneficial Owner Signatures and Get Beneficial Owner Signature Status still work — signatures collected ahead of time are honored once enforcement is turned on for your account.

When Is It Required?

A cross-ramp transaction is blocked until every UBO has signed when all of the following hold:

The user is of type BUSINESS.
The cross-ramp involves MXN as either the source or target currency.

If the currency isn’t MXN, or the user is an INDIVIDUAL, this requirement doesn’t apply and cross-ramp creation proceeds normally.

Integration Flow

Create the business user and complete KYB

Create User with type: "BUSINESS", then complete KYB verification for country: "MX"

Make sure every UBO is on record as an associated person with UBO included in roles and a valid email set

Request the cédula signatures

Request Beneficial Owner Signatures with country: "MX". Capa returns a signingUrl per owner.

Deliver each signingUrl to its owner

Capa does not email the owners — share each signingUrl with the corresponding UBO through your own channel (email, SMS, in-app).

Track completion

Poll Get Beneficial Owner Signature Status, or listen for the DOCUMENT_SIGNED webhook, until every UBO shows SIGNED

Create the cross-ramp

Create Cross-Ramp now succeeds for MXN

Beneficial Owners (Associated Persons)

A UBO is any associated person recorded for the business whose roles includes UBO. Only people with this role are asked to sign a cédula — other roles (LEGAL_REP, SIGNER, CONTROL_PERSON, RESOURCE_PROVIDER) are not.

Every UBO must have an email set — Capa’s signature provider uses it to identify the signer, and there is no fallback to a shared business email. Whether someone counts as a UBO is entirely determined by whether UBO is included in their roles; there is no ownership-percentage threshold enforced by the API.

Requesting Signatures

Call Request Beneficial Owner Signatures to generate a cédula signing link for every UBO-role associated person who doesn’t already have one:

POST /api/partner/v2/users/{userId}/associated-persons/signatures

{
  "country": "MX"
}

Key behavior:

MX only. country must be MX.
Idempotent. An owner with an already-PENDING or SIGNED cédula is left alone — calling this again never issues a second link for the same person. This makes it safe to call after adding a new UBO: only the new owner gets a fresh link.
Per-owner failures don’t block the batch. A business must have at least one UBO on record (and no more than 25 in a single call); beyond that, an individual owner missing an email shows up as an error in the response rather than failing the whole request.
The business must already be KYB-verified for MX.
Capa sends no email or SMS. Your integration is responsible for delivering each signingUrl to its owner, and for treating it as sensitive — whoever holds the link can sign as that person.

Checking Signature Status

Poll Get Beneficial Owner Signature Status to check progress:

GET /api/partner/v2/users/{userId}/associated-persons/signatures

The response lists every UBO-role associated person on record — including any who were never sent a cédula, whose entry simply carries no status. This keeps a “short list” from being mistaken for completion after a new owner is added.

`status`	Meaning
(absent)	No cédula has been requested yet for this owner, or the request failed (see `error`/`errorCode`)
`PENDING`	Requested — the owner has not yet signed. `signingUrl` is included.
`SIGNED`	Complete. `signingUrl` is withheld once signed.

The cross-ramp requirement is satisfied once every UBO on record reports SIGNED.

Enforcement on Cross-Ramp

Create Cross-Ramp rejects the request if any UBO signature is still outstanding for an MXN cross-ramp:

HTTP Status	Code	Message
403	`SIGNATURE_REQUIREMENT_NOT_MET`	”User is not allowed to perform the operation because a required signature is outstanding for BENEFICIAL_OWNER.”

If you see this error, call Get Beneficial Owner Signature Status to see which owner(s) are still pending, and make sure they’ve received their signingUrl.

Webhook Notification

When a UBO signs their cédula, Capa sends a webhook notification once the signature is confirmed:

JSON

{
  "type": "SIGNATURE",
  "event": "DOCUMENT_SIGNED",
  "userId": "8374f327-38bd-4b0b-b8a7-2524599eb903",
  "externalUserId": "customer_1753744084024",
  "partnerId": "b1f2c3d4-5678-4abc-8def-1234567890ab",
  "subject": "BENEFICIAL_OWNER",
  "templateKey": "CEDULA",
  "signature": {
    "associatedPersonId": "a1b2c3d4-5678-4abc-8def-1234567890ab",
    "status": "SIGNED",
    "result": "SUCCESS",
    "country": "MX",
    "signedAt": "2026-09-08T14:32:00.000Z"
  }
}

Field	Description
`subject`	`BENEFICIAL_OWNER` for a UBO cédula. (The same event/`type` combination is also used when a business’s own agreement is signed, with `subject: "USER"` — filter on `subject`, not on a separate event name.)
`signature.result`	`SUCCESS` or `PENDING_REVIEW`. Treat both as signed — `PENDING_REVIEW` means only Capa’s internal compliance review is still outstanding, not that the owner needs to do anything further.
`signature.signedAt`	May be absent in rare cases where the signing provider’s webhook couldn’t be fully parsed.

This event fires once per signature — a redelivered or duplicate provider webhook onto an already-SIGNED record does not re-fire it. As with all Capa webhooks, ensure your Webhook Settings are configured to receive it, and treat Get Beneficial Owner Signature Status as the source of truth if a webhook is ever missed — see How Our Webhooks Work.

Documentation

🖋️ Associated Person Signature (UBO Cédula)

Overview

When Is It Required?

Integration Flow

Beneficial Owners (Associated Persons)

Requesting Signatures

Checking Signature Status

Enforcement on Cross-Ramp

Webhook Notification

What’s Next

​Overview

​When Is It Required?

​Integration Flow

​Beneficial Owners (Associated Persons)

​Requesting Signatures

​Checking Signature Status

​Enforcement on Cross-Ramp

​Webhook Notification

​What’s Next

Overview

When Is It Required?

Integration Flow

Beneficial Owners (Associated Persons)

Requesting Signatures

Checking Signature Status

Enforcement on Cross-Ramp

Webhook Notification

What’s Next