Submit a customer update application
Post-onboarding KYC update. Body shape matches POST /v2/onboarding (partial: send only the fields you want to change). Discover the available fields via GET /v2/onboarding/requirements with the customer’s country; the update flow reuses the CUSTOMER_ONBOARDING rule set.
Authorizations
Headers
Caller-generated unique key that lets the server safely replay this request. The cached response is returned for 5 minutes on any retry with the same key from the same API principal. Required on every state-changing money-moving or resource-creating POST.
1 - 128^[A-Za-z0-9_.:-]{1,128}$Path Parameters
Body
Business-level fields to update (e.g. legalName, tradeName, contactEmail, contactPhone, website, taxId). Inner shape mirrors the onboarding submit shape.
Updated registered business address. Inner shape (e.g. addressLine1, city, state, postalCode, country); country accepts ISO 3166-1 alpha-2 or alpha-3.
Updated operating address. Same shape as registeredAddress.
Updated legal-structure / industry classification. Inner shape resolved at submit by the requirements engine.
Updated operating-activity descriptors.
Updated compliance attestations.
Updated regulatory / adverse-action history.
Updated beneficial-owner / controlling-person disclosure. Sending ownership.persons replaces the full owner set: to edit an existing owner, include its id (from a customer read) plus the fields you want to change; omit id to add a new owner (full identity required); owners not listed are removed.
Updated related-company disclosure.
Updated legal certifications. Same mustEqual: true gating as onboarding.
Customer-level document IDs from POST /v2/documents to attach to this update. Per-person documents go on ownership.persons[i].documentIds[].
1001Optional client-supplied identifier for the resulting customer-update application. Useful for reconciling the submission against an external system. 1-255 characters from A-Za-z, 0-9, underscore, hyphen, colon, and period — no spaces.
^[A-Za-z0-9_\-:.]{1,255}$"ext-update-2026-05-14-001"
Response
The submitted customer-update application
- Option 1
- Option 2
- Option 3
- Option 4
Unique application identifier
^app_[0-9A-Za-z]{22}$Current lifecycle status of the application
pending, processing, approved, rejected, cancelled "pending"
Timestamp when the application was created
"2026-01-15T09:30:00.000Z"
Timestamp when the application was last modified
"2026-01-15T09:30:00.000Z"
customer_onboarding Client-provided identifier for cross-referencing. Omitted when the client did not supply one. 1-255 characters from A-Za-z, 0-9, underscore, hyphen, colon, and period — no spaces.
^[A-Za-z0-9_\-:.]{1,255}$"ext-12345"
Timestamp when the application was submitted for review. Omitted while still in progress.
"2026-01-15T09:30:00.000Z"
Machine-readable failure code on rejected applications. Omitted on non-rejected applications.
rejected_by_ops, compliance_denied Customer-facing failure message accompanying failureCode. Omitted on non-rejected applications.
Customer this onboarding application produced. Omitted while the application is still being reviewed; present after approval persists the customer row.
^cus_[0-9A-Za-z]{22}$People declared on the submission (beneficial owners and controlling persons), in submit order. Omitted before the application carries a submission.