Billing
AutoPay
AutoPay charges a card the patient saved through Stripe for each instalment of a portal payment plan. It is built, and it needs Stripe: the deployment's Stripe keys and the practice's own connected Stripe account. Stripe is not configured on the hosted service today, so AutoPay cannot be turned on there yet.
Written for: Billing and RCM teams · Evaluators
Current state
| Field or control | What it means |
|---|---|
| Which plans | Portal payment plans only (the plans a patient sets up in the portal). Enrolment itself refuses AutoPay: the patient creates the plan first, then turns AutoPay on. |
| Saving a card | The card goes from the browser to Stripe's form on the practice's connected account; ArkCloud keeps Stripe's ids, the brand, last four digits and expiry, and the patient's consent to the card-on-file wording (version, time, who and from where). |
| Portal | In the portal's saved cards and AutoPay panel the patient saves a card, accepts the AutoPay terms and turns AutoPay on, or cancels it. |
| Staff screens | On the AR account's Payments tab, staff with process_payments (Agent, Supervisor, Admin) can save a card with the patient's consent; turning AutoPay on or off needs modify_payment_plans (Supervisor or Admin) and confirmation that the patient accepted the AutoPay terms. |
| Charging | A daily job at 06:00 (while the background worker is running) charges due instalments. A failed charge is retried after 1 day and then 3 days (3 attempts in all); after the last the instalment is missed, and two missed instalments default the plan. Successful charges send a receipt. |
| Stopping | Cancelling AutoPay stops future charges but keeps the plan. Removing the saved card also cancels AutoPay that used it. |
| Without Stripe | The panels say card payments are not set up and nothing is saved, and the daily job skips everything. |