Keep your EHR.
Simplify payments.
Keep more of what you earn.

ODoF EHR-Connected Payments is an independent browser/desktop extension and local-bridge workflow that connects the payment process to a supported EHR/PMS invoice screen. When staff opens an invoice in an authorized EHR session, the workflow can identify the invoice context, send the payment through ShopConnect, and associate the completed transaction back to the supported EHR workflow.

No, unless expressly stated for a specific platform. “EHR-connected” describes an independent productivity workflow and should not be interpreted as a native, official, or direct API integration. ODoF EHR-Connected Payments and ShopConnect Pro are independent products and are not sponsored, authorized, or endorsed by the third-party EHR/PMS providers referenced in this update.

During an active, authorized EHR/PMS session, the ShopConnect Chrome extension or desktop bridge can identify the relevant invoice and associate the payment activity with that invoice. Once a payment, refund, or void is confirmed through the secure ShopConnect payment gateway, the bridge can automatically write the supported transaction status back to the corresponding invoice or patient ledger while the extension/desktop bridge is running. Exact writeback behavior varies by supported EHR/PMS workflow and final production configuration.

The invoice can remain as an unpaid balance in the EHR/PMS until the patient completes the payment. If payment is made while no live EHR session is open, the transaction is securely processed and recorded in the ShopConnect payment environment with the transaction date, amount, and associated invoice information. When an authorized EHR/PMS session is next opened and the ShopConnect extension or desktop bridge is running, the supported workflow can automatically reconcile the completed payment back to the corresponding invoice/ledger without any user input.

Example: an invoice is sent Friday afternoon, the patient pays Saturday night, and the transaction is recorded in ShopConnect; when staff logs into the EHR Monday morning, the supported workflow can update that patient’s ledger automatically.

ODoF EHR-Connected Payments is designed as a user-installed productivity tool that works inside the practice’s own authorized EHR/PMS session. Staff log in normally with their own credentials, and the extension helps automate payment-related steps they could otherwise perform manually. It does not bypass login controls, independently log into the EHR, or require unrestricted database access.

Recent court decisions support an important distinction between an authorized user using a browser tool and an outside company independently accessing a computer system.

In Amazon.com Services, LLC v. Perplexity AI, Inc. (9th Cir. 2026), the court concluded at the preliminary-injunction stage that the customer—not Perplexity—was accessing Amazon when using Perplexity’s browser assistant.

Van Buren v. United States (U.S. 2021) focused federal computer-access law on whether someone entered areas they were not allowed to access, and Facebook v. Power Ventures (9th Cir. 2016) explained that violating website terms alone is not automatically a federal anti-hacking violation.

In simple terms, our workflow is intended to operate more like a browser extension, AI assistant, password manager, or other user-directed productivity tool within an authorized session—NOT like an outside system breaking into the EHR. These cases do not override private software contracts, so each EHR/PMS agreement should still be reviewed individually, especially if a provider changes its terms, expressly objects, or implements technical restrictions.

Once an EHR/PMS workflow is supported, practice setup is designed to be fast because the solution uses a browser extension or desktop bridge rather than requiring the practice to build a native API integration or write custom code. Timing depends on account approval, hardware, workstation setup, and the specific EHR/PMS. For new EHR compatibility development, each workflow typically takes about two weeks to build and test, subject to final testing and platform changes.

The practice needs an active ODoF/ShopConnect payment-processing account, a supported EHR/PMS workflow, and an authorized staff session. Browser-based workflows use Google Chrome with the ShopConnect extension; certain supported desktop/server workflows may use the ShopConnect desktop bridge. Compatible payment hardware is required for in-person card-present transactions. Mobile apps and non-supported browsers may not provide the same EHR-connected workflow or writeback functionality.

For full EHR integration, all EHR-Connected accounts also require the $20/month Virtual Terminal through ShopConnect Pro. In-person setups use a configured Dejavoo P1, P8, or P8 Dual, subject to the supported EHR/PMS workflow and final practice configuration.

All EHR-Connected accounts require the $20/month Dejavoo Virtual Terminal subscription through ShopConnect Pro for full EHR integration. Access is through your ShopConnect Pro Dashboard. This is an additional virtual-terminal subscription fee; normal payment processing fees still apply.

There is no long-term contract and no hidden integration fee. EHR-connected pricing is 0.30 percentage points above the comparable non-integrated ODoF Interchange Plus tier. Actual effective rates vary based on card mix, transaction behavior, and practice volume. PIN debit is excluded from the additional 0.30% EHR fee and remains 0.05% + 20¢. Hardware purchase or rental costs are separate.

The P1 is a wired countertop terminal with a physical keypad. The P8 adds a portable touchscreen and rechargeable battery. The P8 Dual pairs a merchant touchscreen with a patient-facing display and built-in printer. All three offer printed, SMS, or email receipts.

Our team will confirm compatible hardware, connectivity, and enabled features for your supported EHR workflow. Compare the three terminals above.

Supported workflows can include in-person payments using configured Dejavoo P1, P8, or P8 Dual hardware, keyed payments through the Dejavoo Virtual Terminal, text-to-pay/email payment requests, card-on-file transactions, online invoicing, and recurring payment plans. Available methods may vary by final practice configuration and supported EHR/PMS workflow.

Virtual Terminal access is through the ShopConnect Pro Dashboard and requires the additional $20/month subscription for all EHR-Connected accounts.

Card-on-file portability depends on the current processor, EHR/PMS, tokenization method, contractual permissions, and whether the existing provider supports a secure token/card migration. Some platforms or processors may not permit or support migration. If migration is not available, the practice can securely collect and tokenize cards in the ShopConnect payment environment as patients authorize new card-on-file transactions. Payment credentials remain within the secure processor/tokenization environment rather than being stored directly in the EHR-connected tool.

The current EHR-connected workflow is primarily designed for Chrome/desktop use. A ShopConnect mobile payment application is in development for payment acceptance outside the traditional front-desk workstation. Mobile capabilities and EHR writeback may vary by platform.

The program is designed around minimum-necessary access, tokenized payment processing, and enterprise-level security (SOC 2-oriented) controls. Payment credentials remain in the secure processor/tokenization environment rather than being stored directly in the EHR-connected tool. The extension is intended to automate payment and reconciliation steps that authorized staff would otherwise perform manually. HIPAA, PCI, and BAA obligations depend on the final production architecture, vendor roles, data flows, and practice configuration; a Business Associate Agreement should be used where applicable. Practices should rely on the executed vendor agreements and validated production security controls for their specific deployment.

No unrestricted database access is required by the workflow described in this update. We do NOT require your staff login credentials.

The solution is designed to operate within the practice’s authorized user session and to use only the invoice/payment information needed to initiate and reconcile the supported transaction. Access requirements can vary by EHR/PMS and final production configuration.

While it is generally uncommon for established EHR/PMS platforms to make major changes to their payment or invoice workflows without also affecting their own payment integrations, connected features, or other parts of the software, third-party interfaces, technical behavior, and terms can still change over time.

If that happens, compatibility may require maintenance, modification, retesting, or, in some cases, temporary suspension while the workflow is updated.

Our full-time engineering team is prepared to respond quickly to temporary interruptions by remapping or updating the affected workflow (less than 1 hour). In many cases, a minor interface change can be addressed rapidly, depending on the nature of the update.

During any temporary interruption, your ShopConnect payment gateway will continue to function normally, including in-person payments, text-to-pay, online invoices, virtual terminal payments, card-on-file, and payment plans. The main difference is that the payment may need to be manually posted back into the EHR/PMS until the connection is restored.