How to share externally verified data

Learn how to share with Cable that you verified customer’s details using a third-party

If you are using Cable to perform Automated Assurance, you might have already come across checks of the type:

  • All account owners have provided names; or
  • All companies have provided addresses

This is the first information a financial institution gets when onboarding a new customer.

It is important to verify that this data is correct. Cable offers checks with a similar name but an important change:

  • All account owners have either verified dates of birth or verified addresses; or
  • All customers have verified names

Notice the highlighted word verified - it indicates that the information was verified by a third party. When integrating with Cable, developers need to take this into consideration, to correctly send the required data.

Take some time to get familiar with the IDV endpoint.

When integrating with Cable, developers usually fall into one of two traps:

  1. Not using the externally_verified_data block of the API, present in the IDV endpoint

  1. Difficulty breaking down the data to get enough resolution.
    • i.e. the customer might validate that multiple pieces of information match with a person to get an identity check. They can’t say if the name matched with 100% certainty, they can only say that the information as a whole did.

To be able to run these checks, send the data making sure to:

  1. Be very specific when defining the payload.verification_type and set it as the name of the test run.

    • For example: “Customer name verified”; with payload.verfication_outcome as the correct value, one of True/False/None

  2. Integrate the externally_verified_data block into your payload, giving us exact details about which type of field was sent to the external service, and whether it was validated or not

Let’s show some examples of good payloads to send to Cable:

IDV endpoint examples