Payment Connect

Pre-Onboarding Questionnaire

This document serves as a checklist to gather all required information before configuring Cloud Maven’s Payment Connect application. Collecting these details ensures the application is properly aligned with the client’s Salesforce processes, payment gateway settings, automation needs, and compliance requirements.

Who should fill this out: Sections 1–2 are best answered together with your Salesforce admin and finance/gateway contact. Sections 3–8 are typically completed by your Salesforce admin, since they involve page layouts, automation, and email configurations. 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. Gateway & Integration Setup

Question

Response

Which payment gateway(s) do you plan to use?

(e.g., Actum, Fiserv, UnityFi, or others)


Which payment methods do your customers need to use?

(e.g., Credit Card, Debit Card, ACH/Pay by Bank)


Do you have an existing account with your chosen gateway, or do you need one set up? (Note: API keys and required credentials must be provided by the client.)


Do you need to support multiple gateways or just one?


3. Source Object Details

Question

Response

Which record type(s) should have the Payment Connect feature?

In Salesforce, this is called the "Source Object" — e.g., Case, Opportunity, Contact, or a custom object.


What is the parent-child relationship structure (for lookup mapping if using custom objects)?


Which apps need the Payment Console or Related Lists visible?

(e.g., "Sales Cloud", "Service Console")


Which page layouts/lightning pages need the Payment Console component visible?


4. Salesforce Site & Domain Details

Question

Response

Do you already have a Salesforce Site configured for public access (used for hosted payment links)?

If not, we will create a new Site. Please confirm the preferred site name and domain.


Please share your company’s branding materials (e.g., logo URL, primary & secondary colors).

This is to customize the hosted payment screen accordingly.


5. Email Configuration

Question

Response

From which Org-Wide Email Address should the payment request links be sent?


Please provide the verbiage or specific layout preferences for the Email Templates used to send Payment Requests and Payment Confirmations.


6. Access & Licensing

Question

Response

Who will be using the Payment Console?

Please provide a list of users or user roles who will require access, so that appropriate permissions and visibility can be granted.


Do you require any role-based restrictions or access controls?

(e.g., limit refund capabilities based on user profile or role)


7. Automation Preferences

Question

Response

Do you want to automatically send payment links or capture a payment upon certain triggers ?

(e.g., Stage = “Closed Won”)


Do you require the ability to schedule future payments or set up recurring payments?


Should there be any automated record updates?

(e.g., update Opportunity status after payment capture)


Are you using any existing flows or processes that need to be integrated with Payment Connect?


8. Notifications & Additional Requirements

Question

Response

Would you like to notify internal users when a payment is made?

(e.g., via email or Salesforce notification)


Should customers receive a confirmation via email upon successful payment?


Do you use any external systems or portals that should integrate with Payment 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.