POST https://withpersona.com/api/v1/transactions with header Persona-Version: 2023-01-05 and body {data:{type:'transaction', attributes:{transaction_type_id:'YOUR_TXN_TYPE_ID', reference_id:'your-ref', fields:{}}}}
Populate fields with business data: business name, EIN, registered address, and an associated_people array containing name and email for each beneficial owner to be verified
Choose flow mode: 'DB Only' to run silent database verification on all owners, or 'Inquiry only' to email owners a Persona-hosted verification link
Listen on POST /webhooks for event type 'transaction/status-updated'; parse attributes.status values 'created', 'processing', 'passed', 'failed', 'needs_review'
Fetch full transaction via GET https://withpersona.com/api/v1/transactions/{transaction-id} to retrieve sub-verification results for each associated person
Use the Cases API to view consolidated results and trigger manual Approve/Decline decisions for 'needs_review' outcomes
Known gotchas
transaction_type_id is environment-specific and must be created in the Persona dashboard before the first API call; using a production ID in sandbox will return a 422 error
Persona sends webhooks with Svix-Signature headers; validate the signature using your webhook signing secret before processing any payload
KYB flows may require additional configuration for non-US entities; jurisdiction support outside the US must be explicitly enabled per transaction type
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp