Skip to main content
The Persona integration connects your Persona account directly to the Corsa platform. Inquiry lifecycle events and account field updates are delivered to Corsa via signed webhooks, and verification data is mapped onto client profiles using configurable per-account-type field rules. This gives your compliance team a single place to monitor Persona inquiries alongside the rest of your Corsa data.

​
How It Works

  1. Secure connection — Link Persona to Corsa with an API key and fully encrypted credential storage. Corsa discovers each configured account type’s fields from your Persona environment.
  2. Real-time syncing — Corsa receives webhook notifications when accounts and inquiries are created or updated, including completions, failures, and review states.
  3. Automation and mapping — Optional alerts fire when verifications fail or require action. Persona fields you map are written to the right Corsa client fields; unmapped fields are stored as custom data on the client profile.

​
Account types and schema discovery

Each account type you add in Corsa corresponds to a Persona Account Type ID. On setup, Corsa calls Persona’s API to discover the fields defined for that type (using a sample account of that type in your Persona workspace).
  • You can configure up to 20 account types per integration.
  • Discovery requires at least one existing Persona account for each account type ID you enter. If there are no accounts for that type, setup cannot load the field schema for that type.
For each account type, you map discovered Persona fields to Corsa client attributes (individual or business, depending on your workflow).

​
Unmapped account types

When Persona sends an account whose type is not one you configured, Corsa can either skip those events or use a fallback mapping from another account type you select. You choose this behavior in the integration settings.

​
Prerequisites

  • A Persona account with permission to create API keys and configure webhooks.
  • At least one Persona account per account type you plan to connect (for schema discovery).
  • Owner access to the Corsa application.

​
Setting Up the Persona Integration

​
Step 1: Configure automation (optional)

  1. Log in to Corsa.
  2. Go to Developers Hub → Integrations.
  3. Click Configure on the Persona card.
In Automation Settings, you can optionally enable:
  • Create alert on verification failure — Creates an alert when an inquiry fails; set the alert priority.
  • Create alert when verification requires action — Creates an alert when an inquiry is marked for review; set the alert priority.
Alerts are not created instantly. A short delay is applied after status changes so transient states are less likely to generate false alerts.

​
Step 2: Authentication

In Authentication, provide your Persona API key. The key is encrypted and stored securely. If you rotate the key later, update it here; leave the field empty on save if you are only changing other settings and want to keep the existing key.

​
Step 3: Account types and field mapping

In Account Types:
  1. Add one row per Persona account type you want to support.
  2. Enter each Account Type ID from your Persona dashboard.
  3. After Corsa discovers fields, map each Persona field to the appropriate Corsa client field (or leave unmapped — unmapped values are still kept as custom fields on the client).
Persona Account Type ID is not the same as display name. Copy the ID from Persona’s configuration for that account type.

​
Step 4: Unmapped account types

In Unmapped Account Types, choose what happens when an account arrives with a type you did not configure:
  • Skip — Ignore events for unsupported types (default).
  • Use fallback — Apply the field mapping from a fallback account type you select.
Save your changes so webhook instructions stay in sync with your configuration.

​
Step 5: Create the webhook in Persona

After saving, Corsa shows third-party setup details including the webhook URL, API version, key inflection, and the event types to enable. In the Persona dashboard, create a webhook and:
  1. Paste the webhook URL from Corsa.
  2. Set API version to the value shown in Corsa (for example, 2025-12-08).
  3. Set key inflection to camel (or the value Corsa displays).
  4. Enable at least these event types (match the list shown in the integration UI):
    • account.created
    • account.updated-fields
    • inquiry.created
    • inquiry.started
    • inquiry.completed
    • inquiry.failed
    • inquiry.expired
    • inquiry.approved
    • inquiry.marked-for-review
    • inquiry.declined
  5. Save the webhook. Persona will reveal a webhook signing secret.
Treat the webhook secret like a password. Store it only in Corsa.

​
Step 6: Complete setup in Corsa

In Complete Setup, paste the webhook secret from Persona. Until the secret is saved and every configured account type has a complete client-type mapping, the integration remains in pending setup and webhooks may not be accepted.

​
Full sync

Trigger Full Sync is available only after setup is complete. Use it when you want to bring existing Persona data into Corsa— for example, inquiries that were created before you finished connecting webhooks. Day-to-day updates still come from webhooks. The sync only includes Persona accounts that have at least one inquiry. Accounts with no inquiries are not synced.

​
Automatic client matching

When inquiry and account events are processed, Corsa associates data with clients using Persona identifiers and the field mapping you configured. Exact matching rules depend on your mapped fields and whether the client already exists in Corsa.
If you add a new account type after initial setup, save the integration so Corsa can reconcile and discover fields for the new type (requires a valid API key).
Corsa offers native integrations with leading compliance, blockchain analytics, and custody providers. See all integrations or schedule a demo to see how Corsa fits into your stack.