eCBSV FAQs

Thank you for your interest in the electronic Consent Based Social Security Number Verification (eCBSV) service. We are reviewing questions received and will be posting responses here periodically. Please check this page frequently for updates. You may submit technical and general questions by visiting our contact page.

1. Agreements

The eCBSV User Agreement provides all of the requirements related to written consent.

2. Application

3. Consent

Can the electronic signature piece of the eCBSV consent process fit into existing E-Sign Act practices?

Yes, SSA designed its electronic signature requirements in accordance with the E-Sign Act.

4. Costs

5. Current CBSV Customers

As a current CBSV enrolled company and a company who qualifies as a permitted entity, may we begin to accept electronic signatures now?

No, as a currently enrolled company in CBSV, you are not enrolled in eCBSV and are not permitted to accept electronically signed consents at this time. You must continue to adhere to all requirements in the CBSV User Agreement.

As a current CBSV enrolled company and a company who qualifies as a permitted entity, does our enrollment in the current CBSV program affect our application for eCBSV?

No, your status as a CBSV company and a company who qualifies as a permitted entity, does not affect your application for eCBSV. SSA will consider all permitted entities for eCBSV enrollment in accordance with the process set forth in the Federal Register Notice. You must follow the instructions as provided in the Federal Register Notice to apply for eCBSV during the upcoming enrollment period. Companies that do not qualify as permitted entities cannot currently enroll for eCBSV.

We are a service provider for a handful of customers that provide SSA verifications today. Could you explain to me the difference between this new service and the existing service that we use today? Today it's an API where we pass the SSN, DOB, and name and get a yes/no/deceased response which seems to be identical to this new system. Is this new system a replacement for the one we are currently using or is there some other feature that i'm not seeing? I did not see on the site where this new service differs in any way except for new security measures.

The substantial difference between CBSV and eCBSV is that the Economic Growth, Regulatory Relief, and Consumer Protection Act, Section 215, Reducing Identity Fraud, requires SSA to confirm (or not confirm) to a "permitted entity" the validity of fraud protection data (specific information about an individual, including SSN verification) based on the individual's written consent, including by electronic signature. An SSN verification is verification that a name, SSN, and date of birth combination matches (or does not match) our records. The legislation requires SSA to improve our current verification system to accommodate the much larger anticipated volume of users and verifications as a result of now allowing consumer consent to be received electronically. In addition, the Act defines permitted entities use of eCBSV for specific uses as outlined in the Act. Therefore, for entities that do not qualify as a permitted entity, or entities who use the SSN verification for purposes outside of the Act will continue to obtain a number holder’s wet signature on the consent forms and use the current CBSV at this time.

6. Enrollment

What happens if the number of queries exceed the specified limits established for any given permitted entity? How will limits be calculated/enforced? Will it be daily, weekly, monthly, or some other specified time horizon?

The eCBSV system will monitor transactions in real time, and provide an alert when a permitted entity nears their tier level transaction limit. If no action is taken by the permitted entity to establish a new tier level and user agreement, no transactions will be processed over their tier level.

If I am a company that supports financial institutions with decision management solutions, that includes the opening of new accounts, and determine that I qualify as a permitted entity, do I need to apply for eCBSV? Do I need to apply if I am not requesting the SSN verification directly from SSA?

You should apply for eCBSV if you wish to obtain SSN verifications directly from SSA. Each SSN verification request submitted to SSA must be supported by an individual consent, including electronic consent. If you are supporting financial institutions by obtaining information from another service provider who is already an eCBSV customer, please be aware that the other service provider may not share with you the results of its SSN verification request.

7. Initial Rollout

8. Other

If a consumer disputes SSA’s verification response, what action should he or she take?

If the eCBSV User ensures that the data submitted to SSA matches the information provided by the consumer on the consent form, and the consumer verifies the accuracy of the consent data provided, then the eCBSV User can direct the consumer to his or her local SSA Field Office to determine the nature of the problem.

Will financial institutions’ service providers, subsidiaries, affiliates, agents, subcontractors, or assignees be able to pool and/or allocate queries across multiple financial institutions they service?

Yes, financial institutions’ service providers, subsidiaries, affiliates, agents, subcontractors, or assignees may allocate transactions any way they like. SSA will only track the number of transactions at the eCBSV User (who enters into the User Agreement with SSA) level.

Who determines if I am a permitted entity?

You must determine if you are a permitted entity. Review all of the requirements as provided in PL 115-174, 215(b)(4), and provide a certification statement to SSA at least every two years as required by PL 115-174. See the Eligibility tab for more details.

As a permitted entity service provider, will we be allowed to provide the eCBSV to all of our clients or just the financial institutions?

As a permitted entity, you may only use eCBSV with electronically signed consents for your approved activities as a permitted entity and for other permitted entities approved activities under PL 115-174. You may not submit verification requests for entities that are not permitted under the definition.

Can permitted entities change their annual transaction estimates from one year to the next, or do they have to stay in the same tier or higher forever?

A permitted entity should estimate their annual transactions based on how many they anticipate requesting in the first year (365 day usage). Every year after that, the permitted entity has the option to stay at the same tier, or go up or down in tier levels. The only limitation imposed on a permitted entity tier level is when an entity exhausts all transactions within their year (365-day period). In that situation, SSA requires that the permitted entity move to the next higher tier level.

Can you clarify what the "annual number of transactions" is based on? Some of us in the bank believe that it may be implying projected use of this service (number of inquiries) while others believe that it may be implying all banking activities such as deposits, withdrawals, and others.

The annual number of transactions refers to the number of requests for verification that a permitted entity plans to send to SSA annually.

What is the difference between the services provided by the eCBSV and the TIN matching program provided by the IRS? The IRS TIN matching program as outlined in Publication 2108A seems to provide similar services for TIN matching, so I am trying to determine what differences (if any) exist between the SSA and IRS services.

SSA is unable to provide you with any information regarding the IRS TIN Matching program. We can tell you that SSA is the authoritative source for the Social Security Number (SSN). eCBSV will provide SSN verifications to enrolled permitted entities. An SSN verification is verification that a name, SSN, and date of birth combination matches (or does not match) our records.

9. Technical

eCBSV Frequently Asked Questions