Stripe processes the payment. CopperTab holds everything else.

Yes. CopperTab supports one-time invoices as well as recurring payments. The value is connecting the transaction to the patient billing record and keeping sensitive billing context in CopperTab. Installment plans are coming soon.

Yes. A patient might pay a one-time consultation fee, join a monthly membership, and later pay for a separate service. CopperTab connects those payments to the patient’s billing records so each retains its purpose.

An installment plan pays down a defined balance over an agreed schedule. A subscription bills for an ongoing arrangement. Both can sit alongside one-time charges in a patient’s billing history. Installment plans are coming soon.

No. CopperTab connects to your existing Stripe account, so you don't need to create a new one or go through a migration. You keep your current Stripe setup — negotiated rates, payout schedule, reporting, bank account, and payment history — while CopperTab adds the HIPAA-compliant billing layer on top and Stripe keeps handling payment processing the way it does today. That means you can use CopperTab without disrupting your existing payment operations.

No — because you keep your own Stripe account, your Stripe rates, payouts, and reporting stay exactly the same. CopperTab's fee is separate and based on your billing volume.

CopperTab stores and manages the clinical and patient-billing records under its own BAA. Stripe is used only to process consumer payments, and is not provided diagnoses, treatments, service descriptions, clinical notes, appointment data, invoice line items, or patient-record identifiers by CopperTab. All of the billing logic runs inside CopperTab's own HIPAA-aligned environment. When a charge is due, CopperTab sends Stripe only the fields a payment processor needs: the amount and currency, and a statement descriptor showing the provider's business name, the same name that appears when a provider charges a card directly today. Card details are entered by the payer directly into Stripe's hosted fields, so they pass from the payer's browser to Stripe without going through CopperTab. That's what makes the boundary structural rather than a matter of policy: CopperTab is designed and engineered to keep clinical and patient-account content out of Stripe, including its metadata, line items, descriptors, and customer records, enforced through field-level controls and verified before production, not left to configuration or to people remembering what not to send.

Yes. CopperTab is built to bring your existing billing over, not just to start fresh. You can add products, create new subscriptions, or import existing ones along with one-time invoices. We have tooling to handle the migration itself, including importing your customers, their active subscriptions, and where each customer currently sits in their billing cycle — so renewals, billing dates, and payment schedules pick up where they left off instead of resetting. PHI and billing context stay inside CopperTab the whole time, so nothing sensitive is exposed to move your data over. You don't have to run it alone, either: the CopperTab team offers white-glove onboarding and will work alongside you to map your existing data, plan the migration, and confirm everything transferred correctly before you go live.