The Xama integration links your Socket clients to Xama for AML. With it connected you can:
Open Xama from Socket: when first setting up the integration, Socket tries to match your existing clients in Xama with those already in your Socket account and links them. Once linked, you can go straight from a client's page in Socket to their profile in Xama.
Use Xama clients in proposals: once linked, your Xama clients appear in your Existing Clients list when creating proposals, where you don't have another CRM integration.
See AML in Socket: clients and prospects have an AML tab on their Client Details page. From there, you can view their full risk assessment history, manage who needs checking, and open their Xama profile.
Verify identity 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.
Getting started with the Xama integration
In Socket, go to Integrations > Xama.
You need to enter three separate keys to connect your account.
You can find these keys by selecting the XAMA Open API Hub link on the integration page, or by going to Xama's Open API settings. This takes you to your Xama account to retrieve the keys.
Copy each key and paste them into the relevant fields in Socket.
If your Xama connection is lost
If Xama rejects the nightly sync, Socket shows a connection lost notice on Integrations and tells you. Your keys stay filled in on Integrations > Xama, so open the form and select Save to reconnect. You only need to paste new keys if you've changed them in Xama. While disconnected, creating a client in Xama from the AML tab is refused with a message pointing you back to Integrations.
Opening a client in Xama
Once your clients have synced, select External links and then the Xama client. This takes you directly to the Xama record.
Xama clients in proposals
When creating a new proposal, any Xama clients are listed with Xama next to the record.
Pushing clients to Xama automatically
On the Xama integration you'll find an Automatically push new clients to Xama toggle. With it on, when a prospect becomes an active client in Socket a matching Xama account is created for them.
If Socket spots what looks like a duplicate in Xama, it skips creating anything and tells you, so you can link the existing record.
AML tab
Open the client's record to see the AML tab. It shows the details of any risk assessments, and it's where you manage who needs checking.
The AML tab is available on prospects as well as active clients, so you can start someone's AML before they've signed anything.
Key People
Underneath the risk assessments you'll find Key People, the list of individuals connected to that client. Each row shows where they've got to: their status, whether an onboarding request or AML check is outstanding, whether monitoring is on, and whether documents are in.
Three buttons sit above the list:
New, to add someone yourself.
Sync People, to bring through the officers listed at Companies House, where the company has a company number.
Bulk Actions, for doing the same thing to several people at once. Tick the people you want using the checkboxes on their rows, then choose what to do with them.
Adding people here creates their records in Xama but doesn't start anything. Nothing is sent to your client and no check begins until an onboarding request is live and they complete the verification.
You can also create an onboarding request from here at any time, and email the client from here if you'd rather do it that way than through a form. Sync latest risk assessments pulls the current position back from Xama if you've been working over there.
Onboarding Automation
Socket can create onboarding requests for you. On the Xama integration, select Onboarding Automation.
When a proposal is won and the client is pushed to Xama, Socket creates the onboarding requests at the same time, so the ID checks are already in your onboarding form before the client opens it.
Requests are only ever created, never emailed. Sending stays with you, whether that's through a form or an email you send yourself.
Automatically create onboarding requests
There are three ways to run this.
Don't create anything. You add the people and create the requests yourself, in your own time. With no request in place when the proposal is signed, an Identity verification step on a form attached to that proposal has nothing to show yet. Create the request and the step appears.
For existing contacts only. Socket creates requests when the proposal is won, but only for the people already on the client's record. Add the client as a prospect, add just the individuals you want checked, and leave it. When the proposal is won, requests go live for exactly those people and nobody else.
For all company directors and existing contacts. When the proposal is won, Socket creates the Xama record if there isn't one, brings through every officer listed at Companies House, and creates the requests. If the client is already in Xama it adds any directors who aren't there yet and leaves the ones that are. Anyone you'd added yourself who isn't a director is included too.
With the all-directors option and a form with an Identity verification field attached to the proposal, everyone's verification step is waiting the moment the client signs.
Onboarding level for auto-created requests
Underneath, choose which onboarding level auto-created requests should use. These come from your own Xama account, so the options you see are the ones your practice has set up there. How thorough each level is is set in Xama.
Overrides and manual requests
You can override the setting on an individual proposal from its Customise step.
Whichever setting you choose, you can still create requests by hand. The setting decides what Socket creates on its own when a proposal is won. If anything can't be created, Socket notifies you.
Nothing is sent when a request is created, so if someone comes through who you don't need to check, archive them on the AML tab before your client reaches the form.
Identity verification in Forms
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 Building your form.
When the Identity verification step appears
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. Clients are never shown an empty verification step.
How the request gets there depends on your Onboarding Automation setting. Either Socket creates it when the proposal is won, or you create it yourself from the client's AML tab, choosing which people need an ID check.
If you're doing it by hand, the order is:
The client accepts your proposal.
You create the onboarding request from their AML tab, selecting who needs checking.
The client completes the onboarding form, and the Identity verification step now appears for the people you selected.
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: the step does 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.
Collecting director and shareholder details first
If you need to know who the directors and significant shareholders (over 25%) are before you can run your checks, you can use two forms:
Form 1, a short form attached to your proposal, collecting director names, shareholdings, and email addresses. The Table field captures directors and their shareholdings in one grid.
Form 2, your full onboarding form sent afterwards, with the tax references you need and the Identity verification field. Once you've created the onboarding request for the people identified in Form 1, the verification step appears here.
If your practice checks all directors, Sync People and the all-directors automation option do much of this for you, since the Companies House officers come through on their own.







