Overview
When your practice enables a paid add-on module, you must select a payment card to bill. If none of the cards already on file should be used, you can add a new one without leaving the Subscribe dialog.
When to Use This Feature
Use this flow when:
Your practice has no payment card on file yet and needs to subscribe to a module for the first time.
You want to bill a module to a different card than the ones currently saved.
Prerequisites
You must have an organization administrator role.
You must be in the process of subscribing to a module from Administration > Practices subscriptions.
Fields reference
Field | Required | Notes |
Card details | Yes | Card number, expiration date, and CVC are entered together in a single secure card field. |
Cardholder name | Yes | Name as it appears on the card. |
Billing address | Yes | Can be entered manually, or reused from the practice's shipping address if one is on file and valid. |
How to Add a New Card
Go to Administration > Practices subscriptions.
Select Subscribe on the module you want to enable.
If no cards are on file, the dialog shows "No practice payment methods on file". Either way, select Add Credit Card below the payment method list.
The Subscribe dialog is replaced in place by the Credit Card form — enter your card details in the secure card field, then the Cardholder name.
Enter the billing address, or check the option to reuse the practice's shipping address if it applies and is valid.
Select Save.
You are returned to the Subscribe dialog with the new card available for selection. Confirm the plan summary and select Subscribe · $[price]/mo to complete enabling the module.
Result: The new card is saved to the practice's payment methods and becomes available to bill this and future module subscriptions.
Best practices
Use a card that will remain valid for the foreseeable future to avoid a failed renewal charge.
Prefer a practice-level operating card over a personal card, since module subscriptions bill the whole organization.
Keep the billing address accurate — an invalid or mismatched address can trigger address verification warnings.