Payment Details Update Form — shared by the community

Who this template is for

Payment Details Update Form is built for small teams who need a reliable intake process who need to collect the same complete information from everyone.

• Small teams who need a reliable intake process working in banking & identity.
• Teams who need to collect the same complete information from everyone without writing code or paying for a custom build.
• Anyone replacing chasing missing details over email with one structured record per enquiry.
• Respondents are the people you send it to — the form asks them 25 questions across 4 screens.

Why this form is useful

It removes the cost of chasing missing details over email and turns each submission into a record your team can act on immediately.

• 18 questions are required, so submissions arrive complete instead of needing a follow-up email.
• It collects a verified email address so replies and confirmations land.
• It captures a phone number for urgent follow-up.
• It accepts a document or photo upload as evidence.
• It records a signature you can keep as proof of agreement.
• It pins the request to a specific date.
• Conditional logic hides 3 questions until they are relevant — shorter forms convert better than long ones.
• Splitting the form across 4 pages keeps each screen short and shows respondents how much is left.

How to use this template

From copy to live form is a few minutes of work, and every step is reversible.

1. 1Press “Use this template” — a fresh copy of Payment Details Update Form lands in your workspace, ready to edit.
2. 2Rename or delete any question, and change what is required. Nothing here is fixed.
3. 3Open Notifications and add the email addresses that should be alerted on each submission; add an auto-reply to the respondent if the form collects an email address.
4. 4Check the upload limits on the file question so respondents can attach what you actually need.
5. 5Publish it, then either share the link directly or paste the embed snippet into your site — the embedded form resizes to fit and loads no marketing or advertising trackers.
6. 6Watch responses land in Submissions, where you can filter, label and export them to CSV or PDF.

Logic and conditions blueprint

Exactly how this form behaves as it is answered — 3 conditional rules ship with it.

• Features conditional validation: if “Are payments made in a different currency or country?” is Yes, “SWIFT or BIC code” becomes mandatory before the form can be sent.
• Features conditional validation: if “Reason for the change” is Other, “Explain the reason for the change” becomes mandatory before the form can be sent.
• Features advanced show logic: if “Has a verification call been completed?” is Yes, the form dynamically exposes “Who confirmed the change and when”. Otherwise that question never appears.
• All 3 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.