CopperTab

Billing infrastructure for healthcare, built on Stripe. One-time, recurring and payment plans. PHI stays in CopperTab, not your processor. BAA on every plan.

[CopperTab @CopperTab]

Every healthcare payment has two sides: the transaction and the patient billing record.

CopperTab connects them. Stripe processes the payment. Healthcare information stays in CopperTab, out of Stripe.

Keep your Stripe account. BAA included.

[CopperTab @CopperTab]

@kdhrubo @jeff_weinstein @stripe We should chat too!

[CopperTab @CopperTab]

Places PHI quietly ends up in Stripe:

1. Product names
2. Invoice line items
3. Metadata
4. Receipt text
5. Dispute evidence

Most teams catch #1.

Almost nobody thinks about #5.

Full breakdown coming soon.

[CopperTab @CopperTab]

What we've been building:

- One-time, recurring, and payment plan billing
- PHI stays in CopperTab, under our BAA
- Stripe gets payment data, not patient context
- A BAA on every plan, not just enterprise

[CopperTab @CopperTab]

👋 @michaelyared @robert_beene @cball_

[CopperTab @CopperTab]

CopperTab was built by the team at @echobind.

11 years building healthcare and telehealth projects. Heavy billing, patient intake, and virtual care systems XP.

We kept rebuilding the same compliant billing layer for clients, so we decided to make it a product.

[CopperTab @CopperTab]

Hello, world.

We're CopperTab. Billing infrastructure for healthcare, built on Stripe.

Keep your Stripe account. Keep PHI out of it.