API Documentation

Demo Checklist

Suggest Edits

👍

Demo Checklist + Endpoint Specific Requirements

Please utilize both this page and the Endpoint Specific Requirements page as you build your demo. This page is a high-level overview checklist of everything, whereas the Endpoint Specific Requirements page goes into more detail on what specifically to demo for each of the endpoints listed below.

You will need to demonstrate the following:

  • Disclosure requirements
  • End user onboarding flow, including registration and KYC
  • Account linking
  • Transacting
  • 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.

Authentication

Newly onboarding customers are required to use our OAuth2 authentication method. Please disregard the ECDSA method.

OAuth2 documentation can be found here.

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:

  • Terms of Service
  • Privacy Policy
  • Disclosure and Consent (if relevant)

Please reach out to your Onboarding Specialist for more information and documents needed.

📘

REQUIRED DEMONSTRATION - Sign up page:

See sign up page examples here. These must be displayed before you collect end user PII in the below /register step.

Terms of Service, Privacy Policy, and Disclosure and Consent

  1. Demonstrate these are conspicuously displayed to the end user.
  2. Demonstrate that a user must check the box or boxes to agree before being able to submit the signup information.
  3. Point out where a user has access to these documents both on the signup page, and somewhere else in the app/on your website where they can be accessed after signup.

NOTE: The naming of these documents must be consistent throughout your website/application.

WARNING

You are prohibited from using Sila's name, policies, and terms in any public materials until after approval. Therefore, the required language provided to you by Sila MAY NOT be on any live or public facing site prior approval and Production access to being granted.

Step 2. /register

For both an individual and business entity, demo the below:

If you are not utilizing business entities, skip registering a business in your demo.

  1. Show where the end user enters their PII to register
  2. Show the end user entering PII and successfully registering
  3. Show where the end user sees required KYC language - examples found in Endpoint Specific Requirements.

Helpful links:

Step 3. KYC/KYB

🚧

Advanced KYC

Newly onboarding customers are required to use Advanced KYC. Please disregard the Classic KYC system.

For both an individual and business entity, demo the below.

If you are not utilizing business entities, skip all KYB, business entity, and business member steps.

  1. Show an entity that has successfully registered passing KYC
  2. Show both a business and individual entity that have successfully registered requiring further verification (see endpoint specific page for test triggers) and passing KYC after that further verification
    1. This includes the opportunity for the end user to update PII as well as upload documentation
    2. For individual entities, you will need to show them being able to upload documentation to pass KYC
    3. Business entity: No documentation can be uploaded for business entities on Advanced KYC - instead you'll update the business's PII to pass KYB
  3. For KYB, demonstrate linking business members and, if applicable, certification (both beneficial owners and business).

Helpful links:

Step 4. /link_account

  1. Show a bank account getting successfully linked via Plaid or MX.
    • It does not matter which you use, but you will need a contract with one or the other.

Helpful links:

Step 5. ACH Pull Transaction (bank account > Sila wallet)

🚧

Recommendation: use /transact

/issue, /redeem, and /transfer will, in the long-term, be deprecated in favor of our /transact endpoint. We have no current date set for that deprecation, and we will continue supporting existing use of these endpoints until all customers can implement /transact.

Use /issue_sila for this step if you are not implementing /transact.

  1. Show how an end user initiates this transaction.
  2. Show where the end user sees a “Transaction Authorization Screen” where the end user confirms their choice to begin the transaction request, to cancel, or to make changes.
  3. Show where the end user sees a confirmation screen showing the transaction request has been accepted and is being processed.

Helpful links:

Step 6. Internal Transfer Transaction (Sila wallet > Sila wallet)

If this step is not applicable to your use case skip this step.

🚧

Recommendation: use /transact

/issue, /redeem, and /transfer will, in the long-term, be deprecated in favor of our /transact endpoint. We have no current date set for that deprecation, and we will continue supporting existing use of these endpoints until all customers can implement /transact.

Use /transfer_sila for this step if you are not implementing /transact.

Show how an end user initiates a transfer from their Sila wallet to a specified destination wallet:

  1. Show how the end user initiates the transaction.
  2. Show where the end user sees a “Transaction Authorization Screen.” Here the end user should have the option to confirm the transaction information and submit, cancel, or make changes.
  3. Show where the end user sees a confirmation screen showing the transaction request has been accepted and is being processed.

Helpful links:

Step 7. ACH Push (Sila wallet > bank account)

🚧

Recommendation: use /transact

/issue, /redeem, and /transfer will, in the long-term, be deprecated in favor of our /transact endpoint. We have no current date set for that deprecation, and we will continue supporting existing use of these endpoints until all customers can implement /transact.

Use /redeem_sila for this step if you are not implementing /transact.

  1. Show how an end user initiates this transaction which includes.
  2. Indicate where the end user sees a “Transaction Authorization Screen” where they can confirm the transaction information, make changes, or cancel.
  3. Show where the end user sees a confirmation screen showing the transaction request has been accepted and is being processed.

Helpful links:

Ready to submit?

  • Post your demo videos in your Slack channel
  • Your onboarding specialist will be in touch with you on feedback and expected turnaround time for completing the demo review.

Updated 20 days ago