What must a founder confirm with a payment processor?

Get acceptance for the specific model

Describe the entities involved, the services sold, the products involved where applicable, the fulfillment path and the party receiving customer payments. Do not apply as a generic online shop if the business operates a different model. Ask the processor to identify required documentation, restrictions and approval conditions in writing before paid traffic begins.

Stripe, as one documented example, lists telemedicine and telehealth among restricted businesses requiring additional due diligence. Its policy says approval is specific to a service offering and may be modified or revoked. That is not a finding that every telehealth company is prohibited or accepted. Your entity, offering, jurisdiction and processor agreement need their own assessment.

Source context: Stripe: Prohibited and restricted businesses

Map who owns the merchant account and the funds

List the legal entity contracted with the processor, bank account receiving funds, platform account structure and people with administrative access. Ask whether the founder operates a standalone merchant account, a connected account under a platform or another arrangement. Document who can export transactions, change bank details, issue refunds and respond to notices.

Draw the funds path from the customer to each recipient. If clinical and nonclinical entities are involved, have qualified advisers review who charges for which services and the permitted arrangement. Processor acceptance does not answer corporate, clinical or privacy responsibilities. Use the responsibility matrix to name the people accountable for those separate reviews.

Turn settlement and reserve terms into cash assumptions

Ask for initial and ongoing settlement timing, payout frequency, bank timing, reserve or holdback terms, limits and circumstances that change them. Record whether delays use calendar or business days. Stripe distinguishes settlement timing from payout schedules, so a daily payout setting does not by itself determine when a transaction becomes available.

Request a worked example for a new account and a higher-volume month. If a reserve applies, ask what is retained, how it is calculated and what permits release. These questions do not imply that a particular holdback applies to your account. Put confirmed restrictions into the runway worksheet and keep unconfirmed terms labeled unknown.

Source context: Stripe: Payouts and settlement timing

Price reversals and assign dispute work

Confirm transaction fees, refund fees, retained fees, dispute fees and any costs of responding. Stripe states that original processing fees are not returned on refunds and that refunds draw on its available balance. It also documents debiting disputed amounts and a dispute fee. These examples show why the current rate card and account agreement matter.

Name who receives notices, gathers evidence, approves refunds and checks deadlines. Test partial refunds, duplicate payments, declined payments and cancellations without using patient information in a demonstration. Agree what support staff can promise and how billing concerns reach the appropriate clinical or operations team. A provider's dispute tool does not replace an owner for the workflow.

Source context: Stripe: Refund and cancel payments, Stripe: How disputes work

Review the checkout, security and transition together

Ask the implementation owner to document the payment integration and applicable card-security validation. Stripe's security guide describes PCI compliance as a shared responsibility between Stripe and the business. Using a processor therefore does not settle the merchant's entire security task. Confirm requirements for the chosen integration with the processor or a qualified specialist.

Also review customer-facing price, recurring billing, cancellation and refund disclosures with qualified advisers. Confirm statement descriptors, receipts, reconciliation exports and restricted access. Before launch, walk through a transaction, reversal and failed renewal in the approved test environment. Before signing, ask how tokens, records and open disputes are handled if you change providers. Unknown portability belongs in the platform exit plan, not in a promised future migration.

Source context: Stripe: Integration security guide

Before you move forward

• Confirm acceptance for the precise offering before sending paid traffic.
• Document merchant ownership, access and funds recipients.
• Model only confirmed payout and reserve terms as facts.
• Test reversals and give dispute notices a named owner.
• Resolve security, billing disclosures and migration questions with the appropriate advisers.