RapidBridge

What every one of them gets

• The same baseline on all of them

  Automatic detection of the record number, amount and customer, then collection by payment link, secure card window or saved card — plus partial and full refunds with over-refund protection.

• Tier A means deep-tested

  The 15 marked A carry the widest test coverage. The rest are certified against at least three page layouts each, including a redesigned one.

• Write-back marks the record paid

  The 6 marked WRITE-BACK can update the record in the merchant's own software after the payment settles. It ships switched off and is enabled per software.

How every pack is certified

• Three layouts minimum, redesign included

  Every pack is certified against at least three distinct layouts of the application, one of them a redesigned version, before it enters the catalogue. That is what keeps a vendor's interface update from taking detection down with it: the pack was never pinned to a single screenshot.

• No amount is ever guessed

  Detection is built to stay silent rather than be wrong. A page that does not read cleanly shows no amount, never an approximate one, and the merchant confirms every amount before a card is charged. Above $1,000,000 the amount is keyed by hand by design.

• Desktop-installed software runs through the connector

  Dentrix classic, ABELDent, ClearDent classic, Practice Perfect and Tracker have no web page to read, so they are served by the RapidCents connector rather than the extension. The payment, the vault and the settlement records are identical either way.

• Software off this list works too

  “Let RapidBridge figure it out” proposes the fields automatically on any billing page, Teach mode lets a merchant point at the invoice number and amount once, and “Ask RapidCents AI” suggests the mapping where the gateway has it enabled. The catalogue makes setup faster; it is not what makes it possible.

What crosses the wire

• Where it sits

  Between the application your team already works in and RapidCents. It carries the amount and the context out of that workflow and brings the result back, so the operator never retypes a total or a confirmation number.

• What it needs from the software

  A place in the workflow where a payment belongs and a way to reach it. What that looks like depends on the application, which is why scoping starts with the specific system and version rather than with a code sample.

• What comes back

  The same payment record every other channel produces, on the same account, readable and refundable through the APIs, and visible in the same reporting as terminal and online sales.

When to use it

• The software cannot be changed

  Because it is vendor-supplied, because the source is gone, or because the customisation budget would exceed what the payment integration is worth.

• Staff take payments inside another tool

  Phone orders keyed from a CRM record, deposits taken against a booking, invoices settled inside an ERP: each of those is a place where a second screen creates rekeying errors.

• You want one account, not two

  A separate payment tool means a second set of reports, a second reconciliation and a second refund process. Bringing the capture into the workflow avoids all three.

Using RapidBridge

What fails, and how you find out

• Scoping from a screenshot

  Two deployments of the same product can differ by version, by customisation and by what the vendor allows. The scoping conversation is about your installation, not the product name.

• The operator never sees the result

  If the payment succeeds but the workflow does not display it, staff retype anyway and the rekeying you were removing comes back. The return path matters as much as the capture.

• Refunds left outside the workflow

  A capture inside the software and a refund in a different tool splits the audit trail. Plan the refund path in the same scope as the payment path.

• Assuming it replaces the API

  RapidBridge covers the case where an application cannot be changed. Where you can change the software, calling the APIs directly gives you more control and fewer moving parts.