## Set Up eCBSV Verification

Before you start, make sure your organization qualifies as a Permitted Entity and meets the SSA’s requirements for registration, consent, and security.

This guide covers what to expect and what steps to take - so you know exactly what’s coming and how to prepare.

---

## 1. Register with the SSA

You’ll first need to register your organization with the SSA as a Permitted Entity.

### What you’ll need

Before starting the form, collect:

- Institution name
- Headquarters address
- Contact email
- Employer Identification Number (EIN)
- Name and title of authorized signatory (This is usually the vendor relationship manager.)

### Steps to register

1. Open the [SSA Financial Institution Registration form](https://www.ssa.gov/dataexchange/eCBSV/institution_registration.html)
2. Complete all required fields
3. Provide your primary contact information
4. Review the Permitted Entity Certification
5. Click **Sign Certification** to submit
6. Download your signed certification PDF

> 💡  
> ### Want to preview what the form looks like before submitting? [View a sample screenshot](https://developer.socure.com/img/screenshots/ecbsv_financial_institution_registration.png)

---

## 2. Submit Required Evidence to Socure

Once registration is complete, you’ll provide Socure with the following documents to support SSA audit prep.

- A PDF copy of your signed Permitted Entity Certification
- A screenshot of your consumer consent experience, showing intent to sign
- A copy of the **first page** of your SOC 2 Type 2 report or similar security audit

Your Solutions Consultant (CS) will review this to confirm compliance and readiness.

---

## 3. Sign Service Agreement Addendum + Confirm Consent Language

Your Socure Account Manager (AM) will initiate two final compliance steps:

### Service Agreement Addendum

- Socure will send you an addendum with updated pricing, usage terms, and SSA-required flow-down language
- Sign and return the addendum to finalize provisioning

### SSA-Required Consent Language

- You must capture consumer consent explicitly, along with a signal of intent to electronically sign
- For example: a checkbox plus "I agree" button is acceptable
- [See full consent language requirements →](https://help.socure.com/riskos/docs/ecbsv-consent-requirements)

---

## 4. Get Provisioned for eCBSV Access

Once your documents and agreement are complete, your AM will:

- Provision your organization for eCBSV access
- Share API credentials and environment details securely

No additional action is needed on your part here.

---

## 5. Integrate and Test

Now you’re ready to wire up the API.

See [RiskOS™ Setup →](https://help.socure.com/riskos/docs/ecbsv-integration-guide) for more details.

---

## What Could Block Approval?

A few common issues can slow down provisioning:

- Missing or unsigned certification
- Consent flow lacks intent-to-sign evidence
- SOC 2 report is incomplete or outdated
- Agreement addendum not signed

If any of these are flagged, your AM will work with you to resolve them.

---

## Quick Checklist

Here’s everything you need to go live with eCBSV:

- [ ]  Register your institution with the SSA
- [ ]  Download and save your signed certification
- [ ]  Send certification, consent screenshot, and SOC 2 page to Socure
- [ ]  Sign the service agreement addendum
- [ ]  Confirm SSA-compliant consent language in your app
- [ ]  Receive credentials from Socure
- [ ]  Complete integration and test transactions

Updated 3 months ago

---