Demo Checklist

The following "check list" is designed to help your dev team hit all the markers we are expecting to see during the demo review of your sandbox application.

You will need to demonstrate the following:

Steps 1 - 7: includes new user sign up, the registration flow and linking an account
Steps 8 - 12: includes user log in, transaction flow and disclosures requirement.

Learn more about the registration and transaction flows here.

  • NOTE: Videos are required to be submitted with audio as someone needs to talk though what they are clicking on, what endpoint is being invoked and verbalize the requirements indicated.

Step 1. Sign up page

This section should show how a "new end user signs up" including but not limited to:

📘

REQUIRED DEMONSTRATION - Sign up page:

  1. You will need to demonstrate how an end user agrees to your Terms of Service & Privacy Policy by checking the box before being able to submit signup information.
  2. You will need to demonstrate how an end user can click on the separate hyperlinks for the terms of service and the privacy policy to view them individually.

Step 2. /register for Individuals

This section should show how a new individual end user enters applicable KYC meta data:

If you are onboarding a business and/or business members skip to step 6

📘

REQUIRED DEMONSTRATION - Register:

  1. Tell us how/where your private keys are generated and stored.
  2. Tell us all of the KYC Levels your app makes use of: eg. "We will be using KYC-LITE in addition to DOC_KYC" or " We are only using KYC-LITE", etc.

For DOC-KYC:
You will need to demonstrate a new end user entering applicable KYC-DOC
meta data.

  1. Show where the end user sees the “Introduction Screen required language”
  2. Show where the end user sees the “Name/Address/DOB required language”
  3. Show where the end user sees the “SSN required language”

Refer to the Customer Application Demo Requirements for required KYC language

For KYC-LITE:

If you are approved by Sila to use KYC-LITE skip to step 4
IMPORTANT: Not all use case qualify to use KYC-LITE and KYC-LITE will not work in Production without approval.

You will need to demonstrate a new end user entering applicable KYC-LITE
meta data.

  • The following is recommended but not required for KYC-LITE:
  1. Show where the end user sees the “Introduction Screen required language”
  2. Show where the end user sees the “Name/Address/DOB required language”

Follow directions provided in the Demo Requirements for /register specific requirements and information.

Step 3. through Step 5. KYC

The following steps are use case specific, if applicable you will need to demonstrate the transition from one KYC level to the next highest KYC level.
Please follow the directions below that indicate which steps to skip based on your use case and/or approved access.

This section should show how a new end user requests and passes KYC/KYB verification:

Step 3. /request_kyc for (DOC_KYC)

If you are approved by Sila to use KYC-LITE skip to step 4
IMPORTANT: Not all use case qualify to use KYC-LITE and KYC-LITE will not work in Production without approval.

a. The unhappy KYC path must show where users fail their KYC evaluation and are subsequently asked to update meta data and/or send in verifying documents.
This step includes:

  • /request_kyc
  • /check_kyc
  • /update<registration_data>
  • /documents

Follow directions provided in the Demo Requirements for /request_kyc specific requirements and information including how to mock and triage KYC failures in the sandbox.

📘

REQUIRED DEMONSTRATION - /request_kyc for DOC_KYC:

You will need to demonstrate the unhappy KYC path for individuals.

  1. Show what happens when the end users fail KYC
  2. Show how an end user knows what to do next.
  3. Show how an end user updates registration meta data.
  4. Show how an end user uploads applicable verifying documents via the /documents endpoint.
  5. You will need to demonstrate an end user passing KYC

If you are NOT using KYC-LITE skip to step 7.

Step 4. /request_kyc for (KYC-LITE)

IMPORTANT: Not all use case qualify to use KYC-LITE and KYC-LITE will not work in Production without approval.

a. The KYC-LITE path takes in user meta data and returns a passed response.

This step includes:

  • /request_kyc
  • /check_kyc

📘

REQUIRED DEMONSTRATION - /request_kyc for KYC-LITE:

  1. Show how the user submits meta data and knows they have passed KYC-LITE.

b. to continue to Step 5.

If you are approved to use KYC-LITE and are NEVER using DOC_KYC or INSTANT ACH skip to step 7

Step 5. /request_kyc for KYC-LITE to DOC_KYC

a. You will need to demonstrate how an end user adds required meta data and passes DOC_KYC after having previously passing KYC-LITE.

This step includes:

  • /request_kyc
  • /check_kyc
  • /add<registration_data>
  • /documents

📘

REQUIRED DEMONSTRATION - /request_kyc for KYC-LITE to DOC_KYC:

  1. Show how a user adds registration meta data with the /add<registration_data> endpoint.
  2. Show where the end user sees the “SSN required language”

You will need to demonstrate the unhappy KYC path for individuals

  1. Show what happens when the end users fail KYC
  2. Show how an end user knows what to do next.
  3. Show how an end user uploads applicable verifying documents via the /documents endpoint.
  4. You will need to demonstrate an end user passing KYC

b. If you are NOT onboarding businesses skip to step 7

Step 6. KYB

If applicable you will need to demonstrate business onboarding:

Review specific requirements and information provided in the Demo Requirements for KYB.

Step 6a. /register for KYB

This section should show how a new business and its business members enters applicable KYB meta data:

📘

REQUIRED DEMONSTRATION - /register for KYB:

You will need to demonstrate how a business member enters applicable meta data (administrator, controlling officer and beneficial owners).

  1. Show where the end user sees the “Introduction Screen required language”
  2. Show where the end user sees the “Name/Address/DOB required language”
  3. Show where the end user sees the “SSN required language”

Step 6b. /request_ KYC for KYB

The unhappy KYB path must show where businesses or their members fail their KYB evaluation and are subsequently asked to update meta data and/or send in verifying documents.

This step includes:

  • /request_kyc
  • /check_kyc
  • /update<registration_data>
  • /documents

📘

REQUIRED DEMONSTRATION - /request_kyc for KYB:

You will need to demonstrate the unhappy KYB path for businesses and their members.

  1. Show what happens when the business fails KYB
  2. Show what happens when a business member/s fails KYB
  3. Show how an end user knows what to do next.
  4. Show how the business or business member/s updates their registration meta data.
  5. Show how the business or business member/s upload applicable verifying documents via the /documents endpoint.
  6. Demonstrate a business passing KYB
  7. When applicable: show how the onboarding admin certifies beneficial owner/s.
  8. When applicable: show how the onboarding admin certifies the business.

Step 7. /link_account

This section should show how a new end user links a bank account:

Review specific requirements and information provided in the Demo Requirements for /link_account.

📘

REQUIRED DEMONSTRATION - /link_account:

  1. You will need to demonstrate how an end user uses the Plaid modal to link an account.
  2. Confirm your use of link_token_type: processor_token
  3. Demonstrate your understanding of account_name

Receive-Only

If applicable and you were pre-approved by Sila’s Compliance team to use receive-only entities:

  1. You will need to demonstrate how the entity has their account linked with Plaid.
  2. If direct account linking is used for receive-only entities, then you will need to show how documents are submitted and vetted to prove account ownership.

Step 8. /issue_sila

This section should show how an end user issues Sila from their bank account to the end users wallet (associated crypto_address):

Review specific requirements and information provided in the Demo Requirements for /issue_sila

📘

REQUIRED DEMONSTRATION - /issue_sila

  1. Show how an end user logs in
  2. Show how an end user initiates an ACH Debit transaction which includes:
  • specified bank account
  • specified user wallet
  • transaction amount
  1. Show where the end user sees the “Transaction Authorization Screen” which includes:
  • transaction amount
  • bank account information (last four digits of the account number)
  • any recurrence information
  1. Before submitting the end user needs to confirms the transaction information on the Transaction Authorization Screen and have the option to:
  • cancel the transaction request
  • makes changes to the transaction request
  • submit the transaction request
  1. Show where the end user sees the “Confirmation Screen” that tells the transaction request has been accepted and is being processed.

Step 9. /transfer_sila

This section should show the movement of Sila tokens, specifically how an an end user initiates a transfer of a requested amount of tokens and sends that amount to the specified destination handle:

  • If this step is not applicable to your use case please tell us why and skip to step 10.

📘

REQUIRED DEMONSTRATION - /transfer_sila

Show how an end user initiates a transfer from their specified user wallet (associated crypto_address) to a specified destination handle:

  1. Show where the end user sees the “Transaction Authorization Screen” which includes:
  • Transaction amount
  • Where the tokens are going (specified destination handle).
  • Where the tokens are coming from (specified handle for the user wallet).
  • Any applicable service fees
  1. Before submitting the end user need to confirm the transaction information on the Transaction Authorization Screen and have the option to:
  • cancel the transaction request
  • makes changes to the transaction request
  • submit the transaction request
  1. Show where the end user sees the “Confirmation Screen” that tells the transaction request has been accepted and is being processed.

Step 10. /redeem_sila

This section should show how an end user moves tokens from the their wallet (associated crypto_address) and starts the process of initiating an ACH Credit transaction to the end users linked bank account.

Review specific requirements and information provided in the Demo Requirements for /redeem_sila.

📘

REQUIRED DEMONSTRATION - /redeem_sila

Show how an end user moves tokens from the their wallet (associated crypto_address) and starts the process of initiating an ACH Credit transaction to the end users linked bank account.

  1. Indicate where the end user sees the “Transaction Authorization Screen” which includes:
  • transaction amount
  • bank account information (last four digits of the account number)
  • any recurrence information
  • any applicable service fees
  1. Before submitting the end user need to confirm the transaction information on the Transaction Authorization Screen and have the option to:
  • cancel the transaction request
  • makes changes to the transaction request
  • submit the transaction request
  1. Show where the end user sees the “Confirmation Screen” that tells the transaction request has been accepted and is being processed.

Step 11. Disclosures

Sila requires that users have hyperlink access to both the Terms of Service & Privacy Policy at any time from within the app or via a link to the website.

Review specific requirements and information provided in the Demo Requirements for Disclosures.

📘

REQUIRED DEMONSTRATION - Disclosures

  1. Show how an end user can access the Terms of Service from within the app.
  2. Show how an end user can access the Privacy Policy from within the app.

Ready for a Demo Review?

🚧

Double Check - Requirements before submitting!

Make sure you have not missed anything by double checking that you hit all the markers on this Check List and the endpoint specific requirement outline on the Customer Application Demo Requirements.

Head to the Demo Overview page see FAQ and to learn how to submit your sandbox application for a demo review.

Once received and added to the queue Demo Reviews can take up to 5 business days. Feedback will be sent to you via email from your Sila Onboarding Specialist.


Did this page help you?