A practical preparation checklist for software companies and the merchants their platforms serve.
Start with the right application
Use this checklist to prepare a conversation, then follow the chosen provider's exact requirements. An ISV collecting its own software fees and a merchant accepting payments through that software may need separate reviews. Completing this list does not establish eligibility or guarantee approval.
1. Explain the business
Prepare the legal company name, website, entity type, operating address, ownership information requested by the provider, and a short description of the product. Identify whether you develop software, resell licenses, provide support, or collect for third parties. Include the locations of the business, merchants, and buyers.
2. Show the customer journey
Gather your product demonstration, price and plan pages, checkout disclosures, receipt, recognizable billing descriptor, refund policy, and cancellation instructions. Include affiliate or advertising examples if those channels materially drive sales. Make sure the application and live website describe the same activity.
3. Explain the payment pattern
Estimate monthly volume, average and largest ticket, billing interval, service-delivery timing, and expected growth. Bring requested processing statements if available. Explain any previous account closure, disputes, or large refund events, including the steps taken to address them. Do not invent a processing history for a new business.
4. Agree on the secure next step
Ask which documents are required, where to submit them securely, and who owns questions during review. Confirm proposed settlement terms, reserves if applicable, fees, and supported activity in writing. Send sensitive identity and banking information only through the approved secure channel.
Bring the checklist to MIDsource
Start with your software type, industry served, current provider, customer count, and approximate volume. MIDsource can use that context to discuss suitable processing relationships and specialized placement needs. Keep a named owner for the follow-up items so the application does not stall between teams.
Tell us about your software, your customers, and your current payment setup.
Discuss your ISV payment optionsSources and further reading
Provider examples illustrate specific policies and implementation patterns; confirm the requirements of your selected provider.