Assisted Living and Senior Care Payment Processing in 2026: Private-Pay Billing, Family Guarantors, and Long-Term Care Insurance

Call 866-305-6454 now to review payment processing for assisted living, memory care, and senior care facilities.

Senior care billing is not a simple monthly subscription. The resident, family member, fiduciary, insurer, and public-benefit program may all be involved in the same care month. A facility needs a payment record that identifies who paid, what they paid, and which charges the payment covered.

The right workflow begins with a payer map. It then connects the residency agreement, itemized ledger, insurance claim activity, payment authorization, and reconciliation process. Keep those records together, but keep each payer and payment type distinct.

This article addresses residential care facility billing. It does not replace legal, tax, insurance, or compliance advice. Facility agreements and collection practices should be reviewed for the states where the facility operates.

Why senior care billing is a relationship problem, not a subscription problem

A recurring charge may look like a subscription in the payment system. The underlying obligation is different. The monthly amount can include room, meals, care services, medication management, transportation, supplies, and other charges under the residency agreement.

Several people may have different roles. The resident receives care. A family member may help pay. A fiduciary may manage funds. A long-term care insurance carrier may reimburse eligible expenses. A public program may pay for specific covered services. Those roles do not automatically make each person responsible for the full balance.

The ledger must connect each payment to the right payer and period. Record the resident account, responsible party, source of funds, payment date, amount, invoice period, and any allocation to individual charges. Keep insurer payments and adjustments separate from the amount collected from a resident or family member.

Do not rely on a payment processor’s transaction history as the facility ledger. A transaction record shows that money moved. It does not show whether the payment covered a room charge, care-level adjustment, insurer-pending balance, or a prior-period amount.

A clear monthly statement helps the resident and authorized contacts understand what remains due. It also helps staff resolve questions without treating every concern as a card dispute or collection issue.

The payer map

Create separate records for each role:

• Private-pay resident: The resident may pay from personal funds using a card, ACH, check, or another permitted method.
• Adult child or family guarantor: A relative may pay voluntarily or may have signed a separate guaranty. Helping with paperwork or providing a card does not, by itself, establish personal liability for the resident’s full bill.
• Trustee, agent, or other fiduciary: A person may have authority to act for the resident or manage a specific account. Confirm the authority and its limits. A power of attorney, trust document, and residency agreement serve different purposes.
• Long-term care insurance carrier: The carrier may reimburse the claimant or pay a provider if the policy and assignment arrangement permit it. Do not treat an expected claim as collected cash.
• Medicaid: Medicaid is a public-program payment stream. It is not ordinary card-processing volume. Program eligibility, covered services, resident responsibility, and facility participation rules must be handled in the relevant program workflow.
• VA benefits: A resident may receive VA benefits. Do not assume that a benefit is assigned to the facility or paid directly to it. Verify the payment arrangement and the resident’s authority to direct funds.

Keep private-pay card and ACH payments separate in reports from Medicaid, VA, insurance, and other public or third-party payments. Use distinct ledger codes and reconciliation steps. That separation makes it easier to identify processor deposits, explain patient responsibility, and avoid counting an anticipated public or insurance payment as a private-pay collection.

Private-pay billing models

Facilities use different pricing structures. A monthly rate may cover a defined package of housing, meals, and services. Care-level charges may change when an assessment or service plan changes. Some communities also charge entrance or community fees, deposits, or other amounts under a written agreement.

The payment record should mirror the contract. State the charge category, period covered, rate basis, effective date, credits, and payment allocation. Do not combine an entrance fee, recurring monthly amount, and incidental charge into a single unexplained balance.

Rate increases and notice periods can depend on the residency agreement and state law. Avoid presenting one nationwide notice period as universal. Build a change-control process: identify the contractual basis, obtain the required review, send the notice through the proper channel, record delivery, and update the next invoice only when the effective date arrives.

When care level changes mid-month, preserve the old and new service periods.

Show the effective date of the change, the applicable rate for each period, the calculation method, and any credit or supplemental amount. If the agreement uses daily proration, retain the actual method and arithmetic in the account record. If it does not, do not invent a calculation rule after the dispute arises.

A resident should be able to see how the billed amount connects to the service plan and agreement, without needing a staff member to reconstruct the month from separate systems.

The family guarantor problem

Identify the account holder before setting up recurring ACH. The resident may be the person receiving care while an adult child pays from a personal checking account. The contract, guaranty, and debit authorization should make those roles clear.

Regulation E defines a consumer account as a checking, savings, or other consumer asset account established primarily for personal, family, or household purposes. It also excludes an account held by a financial institution under a bona fide trust agreement from that definition. The applicable treatment depends on the account and payment structure. Do not assume a trust account is covered or exempt without reviewing the actual arrangement.

For preauthorized electronic transfers from a consumer account, Regulation E §1005.10 requires authorization by a writing signed or similarly authenticated by the consumer, and the person obtaining the authorization must provide a copy to the consumer. The rule says the account-holding institution or payee cannot substitute its own signature for the consumer’s authorization based only on an oral authorization.

That means a resident agreement signed by a family member is not automatically an ACH authorization for that family member’s account. Obtain a separate authorization from the actual account holder. If someone seeks to authorize a debit from the resident’s account as a representative, verify authority under applicable law and facility procedures. Obtain legal and banking review where that authority is unclear.

A debit can be allowed under a contract and still be returned or disputed. The bank may receive a revocation or stop-payment request. The payer may not recognize the descriptor. The amount may differ from the authorization. Keep the contract, payment authorization, notices, and transaction record as distinct evidence.

Long-term care insurance coordination

Treat long-term care insurance as a claims and reconciliation workflow, not a guaranteed payment source. Policies differ. Confirm the covered care, claim documentation, benefit triggers, elimination period, payment method, and any rules for assigning benefits. Do not assume that a policy reimburses every facility charge or that the insurer pays the facility directly.

The Federal Long Term Care Insurance Program provider EFT form explains that its claims payments are made directly to providers when a claimant has assigned benefits to the provider. Without an assignment, its form says claims payments are made directly to the claimant. That is an example of one program’s process, not a universal rule for every insurer or policy.

Build the facility’s workflow around the actual policy and claim. Retain the assignment or payment direction where applicable. Submit invoices and care documentation required by the carrier. Track claim status, remittance details, denials, appeals, and received funds. Apply carrier payments to the exact resident charges and service period they cover.

Do not mark an invoice paid based on a claim submission or estimate. Keep the pending insurance amount separate from the resident or guarantor balance. When the carrier pays the claimant rather than the facility, reconcile the reimbursement with the account before applying credits or requesting payment again.

The goal is to avoid collecting twice for the same care month.

The ledger should show gross charges, insurer payments, resident responsibility, prior payments, credits, and the remaining balance, with a clear audit trail for each adjustment.

Rate changes and mid-month transitions

Move-in, move-out, transfer between care levels, hospitalization, and death can change the billing period. The facility’s contract and applicable law determine what may be charged and what notice or refund obligations apply. Do not use a single automatic rule for every event.

For a move-in, document the agreement date, service start date, payment source, deposit or other initial amount, and the period covered. For a move-out, document the notice, actual departure, access to services, keys or room status where relevant, and the contract terms used to calculate the final account. Keep charges for services already delivered separate from any disputed future charge.

For a care-level transfer, preserve the assessment or service-plan change record, effective date, rate basis, and notice. If the change happens during the month, keep the period breakdown visible.

After a resident’s death, pause future recurring charges while the facility verifies the account, payment authority, and applicable estate or contract process. Do not continue debiting a deceased resident’s account merely because a stored credential remains on file. Reconcile the final period, identify any refund or balance due, and communicate through the appropriate authorized contact.

A dispute-ready record includes the signed agreement, current rate schedule, notice delivery evidence, dated service-period details, itemized ledger, payment authorization, processor receipt, refund decisions, and staff notes limited to relevant billing facts.

ACH for monthly care billing

ACH can support regular monthly billing when the payer prefers bank-account payments. Select the ACH entry class based on the account type and how authorization was obtained. Nacha’s ACH Guide for Developers describes common SEC codes: PPD for eligible consumer payments authorized in writing, WEB for consumer debits authorized through the internet or wireless network, and TEL for consumer debits authorized orally by telephone. Business-account arrangements may use a different code, such as CCD. Confirm the specific transaction with the facility’s ODFI or processor.

Regulation E §1005.10(d) requires written notice of the amount and date at least 10 days before a preauthorized debit from a consumer account when it varies from the previous transfer under the same authorization or from the preauthorized amount. The consumer must be informed of the right to notice of all varying transfers. The rule permits an option for notice only when a transfer falls outside a specified range or differs by more than an agreed amount. The acceptable range should be reasonably anticipated, not an open-ended authorization.

Create a workflow for changes caused by care-level adjustments, rate updates, insurer credits, and additional services. Hold a debit until the amount and applicable notice are checked. Give the payer a copy of the authorization and a practical way to revoke it.

Monitor return codes and stop repeat attempts when authorization has been revoked. Nacha describes R07 as authorization revoked, R10 as the receiver reporting an unknown or unauthorized originator, and R11 as an entry that does not follow the authorization terms. See Nacha’s return-code explanation. Investigate the reason before any corrected submission. An R11 indicates a terms problem; R07 or R10 requires a different response. Ask the ODFI or processor before reinitiating.

For more on channel selection and reconciliation, review ACH payment processing for small business.

Card-on-file for recurring charges

A family member may store a card for monthly billing. Record the cardholder’s consent, the facility name, the resident account, the purpose of future charges, the schedule or amount-determination method, and how changes or cancellation will be handled.

Card-network stored-credential requirements are separate from ACH authorization rules. Visa’s credentialed transactions documentation describes customer-initiated transactions and later merchant-initiated transactions. It states that merchants offering stored credentials must disclose how credentials will be used, obtain consent to store them, notify customers when terms change, and identify transactions using stored credentials. Keep the original transaction identifier associated with the billing agreement, as required by the processor’s implementation.

Do not treat permission to store a card as unlimited permission to charge any future balance. If the amount or terms change, use the documented agreement and required notice process. A saved card may be a credit card or a debit card. Regulation E treatment can differ based on the account and transaction. Confirm the payment type rather than assuming all cards follow the same rules.

Use a hosted collection page or gateway token where suitable. Do not store card numbers or security codes in the facility management system, email, spreadsheets, or staff notes. Review card-on-file stored credential rules before configuring recurring payments.

Dispute patterns unique to senior care

Disputes often begin with a mismatch between the account record and the payer’s understanding. Build evidence around the specific issue.

• Charge after move-out: Provide the agreement, notice, departure date, final statement, and calculation method.
• Care-level rate dispute: Provide the applicable agreement, service-plan change, effective date, notice, and period-specific calculation.
• Family disagreement about payment: Identify the account holder, the person who authorized the payment, the signed guaranty if one exists, and the authority for any representative.
• Charge after death: Show the final service period, recurring-payment stop date, authority record, final ledger, and any refund or estate communication.
• Charge on a deceased resident’s card: Review cardholder identity and authorization. Do not assume a resident’s permission to use the card extends after death or applies to a different account holder.
• Insurance reimbursement mismatch: Provide the claim, carrier remittance, payment posting, contractual patient responsibility, and explanation of any unapplied amount.

A contract may support a charge without preventing a bank return, card dispute, or complaint. Respond with the evidence that addresses the actual concern. Avoid sending clinical records when the billing agreement, itemized invoice, and payment authorization are sufficient.

Sensitive handling: descriptors, statements, and conversations

A recognizable payment descriptor helps a family member identify the facility charge. Use a facility or operator name that matches the information provided during enrollment. Test statements and receipts from the perspective of the person who pays but does not live at the facility.

Protect resident privacy. Avoid placing diagnoses, care details, or unnecessary personal information in a card descriptor, invoice subject line, email notification, or transaction note. Use account references that staff can reconcile without exposing sensitive information on a payer’s bank statement.

Staff should confirm who they are speaking with before discussing balances. A person may be a family contact without authority to receive account details. Follow facility privacy and authorization procedures.

When a resident has cognitive impairment, do not pressure the resident to provide payment credentials or sign documents without following the facility’s process for capacity, consent, and legal authority. Provide a private, accessible way for an authorized representative to handle payment questions. Train staff to route uncertainty to the designated administrator rather than improvising a financial conversation.

The billing record should capture necessary facts: who contacted the facility, the role they claimed, what was discussed, what documents were reviewed, and what action followed. Do not include unrelated care notes in payment records.

PCI DSS scope for terminals, portals, and phone payments

Facilities may accept cards at a front desk, through a family portal, by phone, or through recurring payments. Each channel has a different data flow. Map where card data enters, which systems receive it, and which vendors can access it.

The PCI Security Standards Council’s PCI DSS document library lists PCI DSS v4.0.1 and its guidance for Requirements 6.4.3 and 11.6.1. Those requirements address payment-page script management and detection of unauthorized changes to payment pages. Facilities that operate or influence a payment page should review the standard and the relevant guidance with their acquirer or qualified assessor.

For a family portal, identify scripts that can affect payment-page security and monitor for unauthorized changes as applicable. A hosted page may reduce exposure, but it does not automatically remove the facility’s responsibility to understand its PCI scope.

For front-desk terminals, restrict access, maintain device inventory, and use approved equipment. For phone payments, keep card details out of call recordings, email, and free-text notes. For recurring charges, use a tokenized credential through the payment provider where appropriate.

A payment gateway integration should fit the facility’s resident-management, accounting, and billing workflows. Confirm the provider’s responsibilities, the facility’s responsibilities, and the applicable validation process. Review merchant account features and compare transparent credit card processing pricing before choosing a payment setup.

Underwriting documentation for a facility or multi-site operator

Describe the operating model accurately to the processor and acquiring bank. A facility may have multiple locations, legal entities, care types, payment channels, and payer relationships. Incomplete or inconsistent information can delay underwriting or lead to account terms that do not fit actual operations.

Prepare documents that explain:

• Legal entity, ownership, and facility locations.
• Services provided and the resident admission process.
• Residency agreement, rate schedule, refund terms, and cancellation process.
• Expected private-pay card and ACH activity.
• Payment channels, including front desk, phone, family portal, and recurring billing.
• Who receives funds and how payments are allocated across resident accounts.
• Insurance claim and assignment workflows, where applicable.
• Public-program payment streams and how they are kept separate from private-pay volume.
• Refund, dispute, return, and resident-death procedures.
• Payment gateway, resident-management, accounting, and other software integrations.
• Historical processing statements and business bank information, as requested.

For multi-site operators, show which entity contracts with residents, which entity processes payments, and where funds settle. Use consistent facility descriptors and location identifiers. Do not combine separate entities under one account unless the acquiring bank has approved the structure.

If the business has complex payment flows or elevated card-not-present activity, discuss a high risk merchant account with an underwriter who understands the model. For related healthcare payment considerations, see medical billing payment processing. Residential care facility billing remains a distinct operating model.

Launch checklist

Before launching a new payment workflow, confirm that staff can answer these questions:

• Who is the resident, payer, account holder, guarantor, and authorized representative?
• Does a separate signed guaranty establish any family member’s personal obligation?
• Does the payment authorization identify the actual account holder and permitted charges?
• Are recurring ACH amounts fixed, or does the workflow handle varying amounts and required notices?
• Are card-on-file consent and transaction records linked to the correct resident account?
• Can every invoice show its service period, rate basis, credits, insurance activity, and payment allocation?
• Are Medicaid, VA, insurer, and private-pay records kept in distinct reporting streams?
• Is there a procedure for rate changes, care-level changes, move-out, and resident death?
• Can staff stop future payments promptly when authorization is revoked?
• Are descriptors recognizable without exposing sensitive care information?
• Are front-desk, portal, and phone payment data flows documented?
• Has the facility reviewed PCI DSS scope and vendor responsibilities?
• Can the team retrieve the agreement, authorization, invoice, notice, payment receipt, and ledger evidence without searching multiple disconnected systems?

Use this review to identify gaps before the first recurring billing cycle. Then test the process with facility staff, finance, the processor, and the software vendor. Update the workflow when the agreement, payer, location, or payment channel changes.

Call 866-305-6454 now to review assisted living and senior care payment processing, ACH, recurring billing, gateway integration, and merchant account options.

This article is for informational purposes only. It is not legal, tax, insurance, or compliance advice. Regulation E, Nacha Rules, card-network requirements, state laws, facility agreements, and insurance terms may apply differently to each payment arrangement. Consult qualified counsel, your processor, and the relevant insurer or program administrator before implementing billing changes.