The Xama integration in Socket is a helpful addition if you’re using Xama for AML — and this is just the beginning. We’re continuing to build on it with more features coming soon.

With this integration you’ll be able to:

Gain Quick access to Xama: When first setting up the integration, Socket will try to match your existing clients in Xama with those already in your Socket account and automatically link them. Once linked, you can jump straight from a client’s page in Socket to their profile in Xama.

Use Xama clients in proposals: Once linked, your Xama clients will appear when creating proposals in your ‘Existing Clients’ list. This makes it easy to pull in existing client details without extra data entry - as long as you don’t have another CRM integration.

AML tab in Socket: Linked clients will have an AML tab on their Client Details page in Socket. From there, you can view their full risk assessment history and click through to their Xama profile.

Identity verification in Forms: Add an Identity verification field to a Socket form and it links to the client’s Xama integration, so their ID check runs through Xama. See the section below for more.

Once your clients have synced, click on 'External links' and then on the Xama client and this will take you directly to the Xama record.

When creating a new proposal, any Xama clients will be listed with 'Xama' next to the record.

Click into the client's record to see a new AML tab displayed. Here we will show the details of any risk assessments.

Once the integration is connected, you can include identity verification inside a Socket form. Add the Identity verification field when building a form and it links to the client’s Xama integration, so the ID check runs through Xama and the result is read only in Socket. There is more on adding fields in our Building your form guide.

Adding the field to your form is not the only step. The Identity verification step only appears to a client when there is an outstanding onboarding request for them in Socket. If there is no request, the step is hidden and the client can complete and submit the rest of the form as normal. This is deliberate, so your clients are never shown an empty verification step.

To create the onboarding request, open the client's record, go to their AML tab, and start an onboarding request, choosing which people (for example, the directors) need an ID check. Socket doesn't select people automatically, this is always your decision.

The recommended order is:

Forms are live, so if the client already has the form open or received it earlier, creating the onboarding request makes the verification step appear without you needing to resend anything.

💡 Testing tip: the step will not appear when testing with a made-up company, because there is no real onboarding request behind it. To see it working, use a client with an outstanding onboarding request and preview the form link.

If you need to know who the directors and significant shareholders (over 25%) are before you can run your checks, a two-form approach works well: