This document serves as a checklist to gather all required information before configuring Cloud Maven's Bank Connect application. Collecting these details ensures the application is properly aligned with the client's Salesforce processes, Plaid account settings, automation needs, and compliance requirements.
Who should fill this out: Sections 1–3 are best answered together with your Salesforce admin and finance/Plaid contact. Sections 4–10 are typically completed by your Salesforce admin, since they involve page layouts, automation, and email configuration. If you're not sure who owns a section, just leave it blank and flag it — we'll walk through it on the kickoff call.
1. Onboarding & Contacts
|
Question |
Response |
|---|---|
|
Primary implementation contact (name, email, role) |
|
|
Expected go-live date |
|
|
Target environment for initial setup |
|
2. Pre-Installation Prerequisites
|
Question |
Response |
|---|---|
|
Is Salesforce Sites enabled? Used to generate and share bank-verification links with customers. If not enabled, confirm your preferred Site domain and we'll assist with setup. |
|
|
Is Email Deliverability set to "All Emails"? Required if you plan to send verification emails. |
|
|
Have you installed the latest Bank Verification package from AppExchange? If not, contact us at Customer Success for the installation link. |
|
|
Which Org-Wide Email Address should be used for outgoing bank-verification emails? (Optional — messages can instead be sent from the logged-in user.) |
|
3. Plaid Account Setup
Complete this section only if you are not an existing Plaid customer — Cloud Maven will use it to create your Plaid account.
|
Question |
Response |
|---|---|
|
Client company name |
|
|
Company address |
|
|
Website link |
|
|
Primary use case |
|
|
Which Plaid products need to be enabled? |
|
Note: API keys, client secrets, and other required credentials must be provided by the client if you are an existing Plaid customer. These are necessary to enable authentication and communicate with banking institutions.
4. Source Object Details
|
Question |
Response |
|---|---|
|
Which Salesforce standard or custom objects will Bank Verification be used on? |
|
|
Which record type(s) should have the Bank Connect feature? In Salesforce, this is called the "Source Object" — e.g., Case, Opportunity, Patient Record, Contact. |
|
|
Which page layouts should include the "Bank Verification Request" action? This helps us ensure proper component placement for end users. |
|
|
Which apps need the Verification Request button or Related List list visible? Example: "Service Console." |
|
5. Products Enablement
Please indicate which Plaid products you'd like enabled, along with default data retrieval preferences.
|
Product |
Configuration Details / Response |
|---|---|
|
Auth |
Questions related to Processor Token Feature. if the feature needs to be enabled. |
|
Balance |
N/A |
|
Liabilities |
N/A |
|
Assets |
|
|
Transactions |
Default transaction look-back period? |
|
Investments |
Default look-back period for investment transaction history? |
|
Statements |
Default statement retrieval period after verification? |
|
Identity Verification |
Client will connect with our team to configure the Identity Verification Template and generate a template ID for each environment (Sandbox/Production). Setup guide: Identity Template Setup Guide |
|
Income Verification |
Enable Bank Income or Payroll Income? If Payroll: allow document upload, or connect only through payroll providers? |
6. Salesforce Site & Domain Details
|
Question |
Response |
|---|---|
|
Do you already have a Salesforce Site enabled for public access? If yes, provide Site details. If no, confirm your preferred Site name and domain — we'll help create one. |
|
7. Access & Licensing
|
Question |
Response |
|---|---|
|
Who will be using the Bank Verification Request? Please list users or user roles who require access, so appropriate permissions and visibility can be granted. |
|
|
Do you require any role-based restrictions or access controls? (e.g., limit certain functionality based on user profile or role) |
|
8. Email Preferences
|
Question |
Response |
|---|---|
|
Email Subject and Content: This email template will be used to send an email to the recipient when a Bank Verification Request is created |
|
9. Automation Preferences
|
Question |
Response |
|---|---|
|
Do you want to automatically generate a verification link upon certain triggers? (e.g., when an Account is created) |
|
|
Should there be any automated record updates? (e.g., update Opportunity status after verification is complete) |
|
|
Do you want to enable Sequencing? (When one or more products can be requested using a single request?) |
|
|
Would you like to allow customers to authenticate with multiple banks within the same request? |
|
10. Sequencing
|
Question |
Response |
|---|---|
|
Do you want to enable Sequencing? |
|
|
If yes to above , please provide the details on sequencing? You can use the below documentation to get more idea on Sequencing and provide us with the relevant information |
|
10. Multiple Bank Authentication
|
Question |
Response |
|---|---|
|
Do you want to allow customers to connect to multiple Bank Accounts in the same request? |
|
11. Notifications
|
Question |
Response |
|---|---|
|
Would you like to notify internal users when a request is complete? (e.g., via email or Salesforce notification) |
|
12. Additional Requirements
|
Question |
Response |
|---|---|
|
Do you use any external systems or portals that should integrate with Bank Connect? |
|
Thank you for completing this questionnaire. Please return it to your Cloud Maven implementation contact — we'll follow up to confirm details and schedule your kickoff call.