# bindro — CME providers

> Bindro takes registrations for accredited CME activities, collects the licence details and financial disclosure your accreditation obliges you to hold, scans participants in per session, and issues one serialised credit certificate per participant from that verified attendance — a no-show who paid gets nothing. Departments can be billed on a purchase order and society members priced against your own roster. It reports nothing to PARS or ACCME; you do that, with its records. It costs 2.5% + $0.99 per paid registration.

Canonical page: https://bindro.io/vertical/cme-registration/
Reviewed: 2026-08-09

## Facts
- Inventory model: multi day agenda.
- Pricing models: member nonmember, tiered, early bird, group rate.
- Fees: 2.5% + $0.99 per paid registration; free activities cost nothing.
- Payouts: one payout per event, released 2 days after that event's LAST session has ended (medium risk tier, 4.5% reserve). Never before delivery, and an activity sold as a run of dates pays out once, after the final date.
- Check-in: badge, works offline. Visitors can come back in: a scan after they were admitted reads as a re-entry rather than a used code, at whichever entrance they come back to, and says when they first arrived. A second scan within a few minutes of the first is still read as the same code presented twice, so a screenshot passed down the queue does not get anybody in. A scan at a later point on the route counts as progress along it, not as a return. The visit is counted once however often it is scanned.
- Joining: free, alone, in minutes. No contract, no monthly fee and no card at signup. A payout destination is verified before the first payout, never before the first sale.
- Booking fee default: the participant pays it. A provider can absorb it or split it per activity; the fee itself does not change with the choice, only which side of the sale it comes from.
- Overselling is structurally impossible: inventory moves only under a row lock inside the transaction that confirms the order, with a database constraint behind that as a backstop rather than as the mechanism.
- The number this vertical is run on: Credit hours delivered. Also tracked: sponsor revenue per attendee, session attendance depth, disclosure completion. The console computes the north-star figure and prints the arithmetic under it, beside this provider's own funnel with the drop-off at each stage, where the traffic came from, refund, transfer, turnout, no-show, add-on and repeat rates each shown with its numerator and denominator, gross, fees and refunds per activity, live remaining capacity during the activity, and CSV exports of orders and participants. A step the platform cannot observe says so rather than reporting a zero.
- Data export: orders and participants as CSV from the console at any time, behind a fresh one-time code. No export fee, no notice period, no lock-in.
- Acknowledged at checkout but NOT enforced — the box is optional and an order completes without it: ACCME accreditation record.

## Not supported for this vertical
- Reporting activities or credit to PARS — nothing in the engine transmits anything to ACCME, to a specialty board or to any other accreditor. Bindro produces the attendance evidence and the per-session hours behind a submission; the provider makes the submission, exactly as they do today.
- Credit types — a credit record carries hours, a serial and the session it came from. AMA PRA Category 1, MOC points, nursing and pharmacy hours are not modelled as separate kinds, so any split between them has to come from how you structure the sessions.
- Reviewing, scoring or mitigating a disclosure — the disclosure is captured as the participant wrote it and stored against their registration. Nobody at bindro reads it, no rule blocks a registration on its content, and the relevant-financial-relationship review the ACCME Standards require of you happens where it does today.
- Faculty management — planners, presenters and reviewers are not modelled as a separate population with their own disclosure and mitigation workflow. Everyone on the roster is a participant, and faculty records live wherever they live now.
- Collecting commercial support or exhibitor money — sponsor packages and sales are recorded on the roster only. No money moves through bindro for them: no charge is taken, no ledger entry is written, no fee is charged and nothing is paid out. You invoice the supporter off-platform, as the separation of commercial support requires anyway.
- Selling exhibit-hall booths as bookable inventory — booth booking is not declared for CME providers, so there is no floor plan and no pitch to sell; a sponsor package is a record of an agreement you made elsewhere.
- Building an agenda across a multi-day activity in the hosted checkout — the hosted flow sells one session per order today. Multi-session orders ship on the public JSON API, so a conference sold session-by-session through the hosted page needs that route or one order per session.
- Enduring materials, on-demand and journal CME — bindro sells the registration and admits at the door. It hosts no content and keeps no learner record, and a credit here comes from a scan at a live session.
- Annual all-access CME subscriptions — payouts settle per delivered activity, so subscription revenue could be taken and never paid out. It is refused on purpose.
- Paying a registration in instalments, deferring a place to a later run, or adding sales tax — all three are optional for this vertical and none are enabled.
- Handing a registration to a colleague, or a waitlist on a closed activity — neither ticket transfer nor waitlists are declared for CME providers, so a place is refused rather than quietly reassigned, and closed means closed.

## Questions the landing page answers
- What does an accredited activity look like from open registration to certificate?
- Does bindro report my activity to PARS, and can software be ACCME compliant?
- What can you answer when an accreditor asks about an activity from three years ago?
- What should a CME office check before moving a conference across?
  https://bindro.io/vertical/cme-registration/

## Pages
- FAQ (22 questions): https://bindro.io/vertical/cme-registration/faq/
- bindro vs EthosCE: https://bindro.io/vertical/cme-registration/compare/ethosce/ (reviewed 2026-08-09)
- bindro vs CloudCME: https://bindro.io/vertical/cme-registration/compare/cloudcme/ (reviewed 2026-08-09)
- bindro vs Cvent: https://bindro.io/vertical/cme-registration/compare/cvent/ (reviewed 2026-08-09)
- bindro vs CE-Go: https://bindro.io/vertical/cme-registration/compare/ce-go/ (reviewed 2026-08-09)
- Issuing CME credit from the scan, not the sale: https://bindro.io/vertical/cme-registration/blog/issuing-cme-credit-from-the-scan-not-the-sale/ (reviewed 2026-08-09)
- Collecting licences and disclosures before anyone pays: https://bindro.io/vertical/cme-registration/blog/collecting-licences-and-disclosures-before-anyone-pays/ (reviewed 2026-08-09)
- Running a multi-day CME conference on bindro: https://bindro.io/vertical/cme-registration/blog/running-a-multi-day-cme-conference/ (reviewed 2026-08-09)
- Billing departments, societies and members: https://bindro.io/vertical/cme-registration/blog/billing-departments-societies-and-members/ (reviewed 2026-08-09)