Create a connected account with type 'custom' via POST /v1/accounts; include the controller object to specify who owns loss liability, fees, and requirement collection.
Set controller.fees.payer and controller.losses.payments to 'application' if the platform bears fees and losses, or 'stripe' if Stripe does.
Collect KYC information directly by POSTing individual, business_type, business_profile, and tos_acceptance fields to the account object.
Upload identity documents via POST /v1/files with purpose 'identity_document', then attach the file IDs to the account's individual.verification.document fields.
Retrieve requirements.currently_due periodically and continue collecting and submitting fields until the list is empty.
Enable required capabilities by setting each to {requested: true} in a POST /v1/accounts/{id} update; monitor their status transitions.
Known gotchas
Custom accounts put full KYC collection responsibility on the platform; you must meet Stripe's data requirements and handle all verification edge cases yourself.
Some fields are immutable after initial submission (e.g., business_type); validate inputs carefully before writing.
controller settings cannot be changed after account creation — choose them correctly at account creation time.
Give your agent this knowledge — and 16,300+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?