Moving to Stearns

This doc is meant to outline the basic flow for transitioning from Evolve to Stearns. Please use our API specific documentation for more detailed information on interacting with the Sila API's.

Links to Helpful Documentation

Get Started with SDK Integration

Required Privacy Disclosures

Best Practices

Session Key Design Guide

Integrate Sardine SDK

Please use Sardine's documentation to get started with the Risk SDK:

Getting Started

🚧

Please Note

Sila is handling both Auth and Webhook setup, so do not worry about those.

You will also see documentation on Devices and Signals, which are not relevant to the Sila integration.

Setup:

  1. Generate Sardine Sandbox credentials

  2. Choose the SDK you need

  3. Use Integration Guides to install the SDK

Change KYC Level

πŸ‘

KYC API Calls

Please see our /request_kyc documentation for code samples demonstrating the Sardine KYC Levels.

The KYC Level names for Sardine's KYC are different, so you will need to update your code to match.

  • KYC
KYC LevelDetails
KYC-SARDINE-STRICTRequires name, address, phone, email, birthdate, SSN

Comparable to Sila's KYC-STANDARD.
  • KYB

KYB requires no level to be submitted. Please leave out when calling /request_kyc for a business entity.

Adjust Doc Verification Flow

  1. Make a call to this endpoint: /sardine_doc_verification_link
  2. This will retrieve a URL you can direct the end user to, and Sardine will handle the rest.
  3. You will receive a webhook updating the IDV status.

Sardine Session Key

Some calls will require a customer-generated session key. Please use Sardine's session key design guide for guidance.

πŸ“˜

Use 24-hour Expiry

While the docs recommend 30 minutes, a longer expiry is better for the Sila/Stearns integration.

Sila API Calls Requiring Sardine Session Key
/register
/add
/update
/delete
/issue_sila
/redeem_sila

πŸ‘

Session Key API Call Code Samples

Please see the individual doc pages linked in the above table for code samples including the Sardine session key.