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 value 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 configured account type and inquiry template 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 values you map are written to the right Corsa client values. Values without an explicit mapping are still kept as custom fields or client attachments, depending on their type.

​
Account type and value mapping

Corsa uses Persona account type to decide whether an account becomes an individual or corporate client. This is the default mapping model for Persona integrations.
  • Account type mapping - Map each Persona account type to a Corsa client type: Individual or Corporate.
  • Inquiry template mapping - Map values from Persona inquiry templates to Corsa client values.
Inquiry templates do not define the Corsa client type. They control how inquiry-specific fields are mapped into the Corsa client.

​
Account type mapping

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 by using a sample account from 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 values to Corsa client values.
When Persona sends an account whose type is not configured, Corsa can either skip those events or use a fallback mapping from another account type you select.

​
Inquiry template mapping

Inquiry template mapping lets you configure how Corsa writes inquiry-specific Persona values. For each Persona inquiry template, you choose:
  • The Persona values to write to Corsa client values.
Configure account type mappings first. Inquiry template mappings add more field detail, but account type remains the source of truth for client type.

​
Inquiry value mapping behavior

Mapped inquiry values update the synced Corsa client after the base account is created or updated.
  • Persona values mapped to Corsa client values update those values directly.
  • Unmapped non-file values are stored as custom fields on the client profile.
  • Unmapped file values are uploaded as client attachments.

​
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.
  • Persona inquiry templates configured for each onboarding flow where you want template-specific value mapping.
  • 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: Configure account type mapping

In Account Type Mapping, configure how Corsa should resolve client type:
  1. Add one row per Persona account type you want to support.
  2. Enter each Account Type ID from your Persona dashboard.
  3. Select the Corsa client type for that account type: Individual or Corporate.
  4. After Corsa discovers fields, map each Persona value to the appropriate Corsa client value. Values without a mapping are still kept as custom fields or client attachments, depending on their type.
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 value mapping from a fallback account type you select.
Save your changes so webhook instructions stay in sync with your configuration.

​
Step 5: Configure inquiry template value mappings

If you need template-specific value mapping, add inquiry template mappings:
  1. Add one row per Persona inquiry template you want to support.
  2. Corsa loads the inquiry fields for that template.
  3. Map each Persona value to the appropriate Corsa client value. Values without a mapping are still kept as custom fields or client attachments, depending on their type.

​
Step 6: 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 7: Complete setup in Corsa

In Complete Setup, paste the webhook secret from Persona. Until the secret is saved and account type mappings have enough configuration to resolve client type, 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 value mapping you configured. Exact matching rules depend on your mapped values 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 the new account fields. Inquiry template fields load when you add the template mapping. Both actions require a valid Persona 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.