Describe your new, replacement, or additional debit card process. Makeform creates a structured application with account details, card preferences, disclosures, and acknowledgment.
Route applications to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting point, tailor it, or send it to the builder. Edit every example for your institution's process.
Audience
Existing checking-account customers requesting their first card
Format
Guided application with delivery choice
Prompt size
258 chars
Example form structure
Guided application with delivery choice
Customer name and contact details
Member or account reference
Which checking account should be linked?
Mail delivery or branch pickup?
I acknowledge the debit card disclosures
Suggested routing tags
New card
Replacement
Needs review
Separate new-card, replacement-card, and additional-card requests early so applicants only see the fields relevant to their request.
Step 1
Request
customer chooses card request type
Step 2
Identify
account and applicant details collected
Step 3
Review
staff checks eligibility and exceptions
Step 4
Route
decision and fulfillment follow-up assigned
A cleaner intake
A purpose-built debit card application form sorts requests, captures consistent details, and makes the next owner clear.
Show relevant paths for first cards, replacements, additional cardholders, and business cards.
Required fields keep account references, card names, and delivery choices predictable.
Tag loss reports, name changes, pickup, and business requests for the right queue.
Common card journeys
Choose the closest workflow, then insert your institution's options, disclosures, and review steps.
Gather linked account, card name, design, delivery choice, and acknowledgment.
Ask when the card was last seen and show your urgent contact instructions.
Capture requester, proposed cardholder, relationship, and required acknowledgments.
Collect business context, cardholder role, access choices, and review owner.
Build the workflow
Describe your card program, refine the generated fields, and connect each submission to the team that handles review and customer follow-up.
Name eligible accounts, request reasons, delivery choices, disclosures, and routing rules.
Insert your options and show loss, business, or joint-owner fields only when relevant.
Exclude PINs, passwords, CVVs, and full card numbers. Use your approved identity process.
Share the form and notify the team responsible for review and follow-up.
Choose an intake method
The right method depends on your process, but structured online intake gives staff a consistent record while preserving a clear review step.
Field guide
Use these six sections as a practical checklist, then align every field and disclosure with your bank or credit union's approved card-issuance process.
Applicant
Collect enough information to locate and contact the applicant. Distinguish the requester from an additional cardholder or business user.
Request type
Use one early choice to control later fields. New, damaged, lost, stolen, name-change, and additional-card requests need different routing.
Account
Ask only for your approved account reference and eligible account type. Avoid fields that invite credentials or card data.
Card setup
Offer only card options your staff can fulfill, such as printed name, available design, delivery method, or pickup branch.
Acknowledgment
Show approved disclosures before acknowledgment. Recording a response should not imply that submission means approval or issuance.
Internal review
Use tags, status fields, and notifications to separate standard requests from loss reports, identity changes, and business cards.
Related tools
Connect debit card requests with account opening, identity intake, payment authorization, and other customer-service forms.
Create structured intake for customers starting a new account relationship.
Open toolBuild a separate application flow for customers seeking a credit card product.
Open toolCollect institution-defined customer information for an identity-review workflow.
Open toolCreate a first-step registration form for new customer intake.
Open toolStructure requests for identification cards in a separate administrative workflow.
Open toolBuild an authorization intake flow around your institution's approved payment process.
Open toolFAQ
Practical answers for operations, digital banking, and branch teams creating a consistent request experience.
It collects a customer's card request, applicant and account references, card preferences, delivery choice, disclosures, and acknowledgment for staff review.
Include contact details, approved account reference, request type, card name, available options, delivery choice, and disclosure acknowledgment. Add conditional fields where needed.
Yes. Offer reasons such as damaged, expiring, lost, stolen, or name change. For missing cards, ask when last seen and show your contact instructions.
Do not ask for a PIN, banking password, CVV, or unnecessary full card details. Use only identity and account references approved for your workflow.
No. State that the request enters review. Explain the next step without promising approval, issuance, timing, or another outcome.
Yes. Conditional answers can tag and notify different queues, separating loss reports from requests that need business-account review.
Yes. Makeform includes unlimited free forms and responses, so you can generate, edit, publish, and collect applications without a response cap. A paid tier is available to remove the Makeform badge.
Yes. Place approved disclosures before a required checkbox, and add a signature when your process calls for one. The response stays with the submission.
Replace scattered card requests with structured intake.
