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.

🚧

New Evolve Requirements as Oct 2022

This page contains new requirements established by Sila's banking partner. All customer who have not been approved by Evolve must include these new requirements in your demo submission. Failing to do so will result in a delay in the approval process.

Customer's whose demo submission has already been reviewed and approved by Sila's Integration team only need to resubmit videos for Step 1 and Step 11.

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.

  • 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" and demonstrates a new user agreeing to the following:

  • Term of Service
  • Privacy Policy
  • End User Account Agreement
    • Customer Account Agreement (for consumers, as applicable)
    • Business Account Agreement (for businesses, as applicable)
  • Disclosure and Consent to the applicable End User Account Agreement

📘

REQUIRED DEMONSTRATION - Sign up page:

Review the specific requirements for required details about the Agreement & Disclosures when an End User signs up. https://docs.silamoney.com/docs/agreement_and_disclosures_requirements

Terms of Service & Privacy Policy

  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.

End User Customer Account Agreement (for consumers)

Only applicable if you are onboarding individual consumer users.

  1. You will need to demonstrate how an (individual entity) End User either:
  • A: Initiates a download of a screen-readable PDF version of the Evolve Customer Account Agreement that was supplied by Sila; or
  • B: Clicks on a hyperlink that takes them to a dedicated page on the website associated with the App that displays the Evolve Customer Account Agreement (with the required formatting).

End User Business Account Agreement (for businesses)

Only applicable if you are onboarding business users.

  1. You will need to demonstrate how a (business entity) End User either:
  • Initiates a download of a screen-readable PDF version of the Evolve Business Account Agreement that was supplied by Sila; or
  • Clicks on a hyperlink that takes them to a dedicated page on the website associated with the App that displays the Evolve Business Account Agreement (with the required formatting).

Disclosure and Consent to the End User Account Agreement

  1. You will need to demonstrate how the Agreement Disclosure and Consent is conspicuously displayed to the End User (e.g., pop up).
  2. You will need to demonstrate how the End User can view the applicable Account Agreement by any of the following means:
  • An operable hyperlink in the disclosure and consent to redirect the End User to the applicable Account Agreement; or
  • Other way for the End User to easily access, read, and retain an unmodified copy of the applicable Account Agreement prior to consenting (i.e., scroll, download, etc.)
  1. You will need to point out where in the Disclosure and Consent you have working hyperlinks to Sila’s terms and policies.
  2. You will need to demonstrate how an End User agrees to the applicable Account Agreement and Sila’s terms and policies by checking a consent box before being able to submit signup information.
  3. Demonstrate where you are capturing required fields of the Electronic Signature data showing that the End User is consenting to the Disclosure, the applicable Account Agreement, and Sila's terms and policies.

    You must point out each required field.

Additional Required Disclosures

  1. You will need to demonstrate where an End User accesses any Additional Required Disclosures before being able to submit signup information.

REMINDER: Your Demo application and any associated links must be hosted in a DEV environment.

See the WARNING call out on the Agreement & Disclosures specific requirements page for details

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:

Review the specific /register endpoint requirements for required details. https://docs.silamoney.com/docs/requirements-customer-application-demo#register-specific-requirements).

  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 /register specific 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”

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

📘

REQUIRED DEMONSTRATION - /request_kyc for DOC_KYC:

Review the specific /request_kyc endpoint requirements for required details. https://docs.silamoney.com/docs/customer-application-demo-requirements#request_kyc-for-individuals

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:

Review the specific /request_kyc endpoint requirements for required details. https://docs.silamoney.com/docs/customer-application-demo-requirements#request_kyc-for-individuals

  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:

Review the specific /request_kyc endpoint requirements for required details. https://docs.silamoney.com/docs/customer-application-demo-requirements#request_kyc-for-individuals

  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:

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:

Review the specific KYB and /request_kyc endpoint requirements for required details. https://docs.silamoney.com/docs/customer-application-demo-requirements#request_kyc-for-businesses

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:

Review the specific KYB and /request_kyc endpoint requirements for required details. https://docs.silamoney.com/docs/customer-application-demo-requirements#request_kyc-for-businesses

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:

📘

REQUIRED DEMONSTRATION - /link_account:

Review specific /link_account requirements for required details.
https://docs.silamoney.com/docs/customer-application-demo-requirements#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.

🚧

Virtual Accounts - Demo

If you are approved to use the virtual accounts product you will be required to submit an additional and separate virtual account specific demo.

Refer to the Virtual Account Demo Checklist for those requirements.
https://docs.silamoney.com/docs/vaccounts-demo-checklist

📘

Transaction Demo and Funds Flow

The following section of the Demo pertains to the movement of funds within you application. This demonstration MUST match the Compliance approved funds flow you completed with your onboarding specialist.

Your demo submission will be rejected if:

  1. You have not completed a funds flow
  2. Your funds flow has not been approved by Compliance
  3. Your demo does not reflect the approved funds flow

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):

📘

REQUIRED DEMONSTRATION - /issue_sila

Review specific /issue_sila requirements for required details.
https://docs.silamoney.com/docs/customer-application-demo-requirements#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:

📘

REQUIRED DEMONSTRATION - /transfer_sila

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

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.

📘

REQUIRED DEMONSTRATION - /redeem_sila

Review specific /redeem_sila requirements for required details.
https://docs.silamoney.com/docs/customer-application-demo-requirements#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. Continued Access to Agreement & Disclosures

Sila requires you to provide End Users with access to the applicable End User Account Agreement and any Additional Required Disclosures at any time from within the app or via a link to the website.

Review the specific requirements for required details about continued access to the Agreement & Disclosures.
https://docs.silamoney.com/docs/agreement_and_disclosures_requirements

📘

REQUIRED DEMONSTRATION - Disclosures

Terms of Service & Privacy Policy

  1. You will need to demonstrate an end user can access the Terms of Service from within the app or on the website.
  2. You will need to demonstrate how an end user can access the Privacy Policy from within the app or on the website.

End User Account Agreement

  1. You will need to demonstrate how an end can access the applicable End User Account Agreement (that was supplied by Sila) from within the App or on the website, and you will need to host the Account Agreement on the website at a URL associated with the title of the applicable Account Agreement for continued access and monitoring by Sila and Evolve.

Disclosure and Consent to the End User Account Agreement

  1. You will need to demonstrate how an End User can access the Account Agreement Disclosure and Consent from within the App or on the website.

Additional Required Disclosures

  1. You will need to demonstrate how you have provided the End User with reasonably visible notice within the user interface (i.e., footer, blip, scroll, page, or popup) capturing the Additional Required Disclosures, as outlined in the Sign Up Page & Disclosures specific requirements.

REMINDER: Your Demo application and any associated links must be hosted in a DEV environment.

See the WARNING call out on the Agreement & Disclosures specific requirements page for details

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.