Bambora · Payment integration
Charge, refund and void patient payments without leaving the account.
Bambora, now part of Worldline, is a Canadian payment gateway. Clinicmaster uses it for online and stored-card patient payments: a one-off charge, a payment against a card the patient has saved, a refund, or a same-day void — all raised from the invoice and written back to it.
The Bambora integration
Bambora (now part of Worldline) is an online payment-processing provider widely used in Canada. Clinicmaster integrates with its API to take card payments against a patient’s account, store cards as Bambora customer profiles for repeat use, charge those saved cards, and reverse a payment by refund or by void. Card details live with Bambora; Clinicmaster holds the profile reference and the transaction result.
What the Bambora integration does.
The full lifecycle of a card payment — take it, save it, charge it again, reverse it — driven from the patient’s account rather than a separate gateway portal.
Online card payments
Patients pay a balance by card through Clinicmaster and the charge is raised against the invoice it settles, so nothing has to be matched up afterwards.
Cards saved as gateway profiles
A card the patient wants kept on file becomes a Bambora customer profile. Clinicmaster stores the reference, not the card number.
Charge a card already on file
Repeat payments — a program of visits, an outstanding balance — can be taken against the saved profile without asking the patient for the card again.
Card-on-file lookup
Staff can see which card is on the patient’s profile before charging it, so the person paying knows what is about to be used.
Refund or void, whichever applies
A payment can be voided before it settles or refunded after, both raised against the original transaction so the reversal is always traceable.
Gateway credentials held server-side
Merchant credentials are configured per clinic and stored as secrets. There is no key entry in the app and no self-serve activation.
From charge to clean reversal.
Bambora is connected to your clinic.
The payment module is licensed and your Bambora merchant credentials are configured server-side as secrets, per clinic.
The payment is taken from the invoice.
Staff or the patient pay by card, or against a card already saved as a profile. The charge is raised for the amount owing on that account.
Voids and refunds stay linked.
If something needs undoing, Clinicmaster voids the transaction before settlement or refunds it after — always against the original charge, so the account stays coherent.
What this integration does not do
Card details are held by Bambora as a customer profile — Clinicmaster does not store card numbers. Bambora is the card gateway for patient payments; insurer claims and adjudication run separately, covered on Billing & insurance. For tapping a card at the front desk on a physical terminal, see the Clover integration. Merchant onboarding is arranged with Bambora/Worldline.
What Clinicmaster keeps for every Bambora payment.
Every charge keeps what is needed to explain it later and to reverse it correctly — which is the difference between a payment system and a receipt.
Back to all integrations- Amount and currency
- One-off card or saved profile
- Card brand and last four
- Bambora transaction number
- Approval or decline result
- Invoice or account applied to
- Stored profile reference
- Voids raised on the charge
- Refunds raised on the charge
Bambora integration questions.
Scale your Organization with Clinicmaster.
30-minute working session with a solutions engineer. Bring your current numbers — we'll show you the gap.