Accept crypto payments at your senior care home

Why a senior care home collects from someone who has never seen the building

Most businesses are paid by the person they serve. A restaurant serves the diner who pays. A dental clinic treats the patient who settles the bill at reception. A senior care home is different, and the difference runs through every part of its finances: the person receiving the service is rarely the person paying for it.

The resident is 87. The payer is her son, 54, who moved abroad twenty years ago, works in another currency, and has taken on the monthly fee as a permanent line in his own budget. Sometimes the payer is three people — siblings in three countries who agreed on shares in a difficult conversation and have been transferring their portions separately ever since. Sometimes it is a niece who handles everything because nobody else could. Sometimes it is a court-appointed representative or a family lawyer.

What none of them is, is standing at your front desk on the first of the month.

Layer on top of that the demographic backdrop, which is the reason this vertical keeps growing and keeps globalising at the same time. The World Health Organization's own figures on ageing and health describe a world where the share of people over 60 is climbing everywhere, fastest in low- and middle-income countries. The children of those older people are, statistically, the most mobile generation in history. A residence in Buenos Aires, Bogotá, Lisbon, Manila or Guadalajara is increasingly staffed locally, occupied locally, and financed from abroad.

Three revenue streams that behave nothing alike

A residence does not have one bill. It has three, and they fail in different ways.

The monthly fee. The base rate for the room plus the care level — and the care level changes, which means the amount changes. This is the business. It is recurring, it is due on a fixed day, it is the same next month, and it will be the same for an average length of stay that is measured in years. It is also the single most fragile recurring charge in any consumer-facing industry, because the instrument behind it usually belongs to someone in a different banking system.

The extras. Hairdresser, podiatry, physiotherapy sessions beyond the included ones, incontinence supplies, a private companion for hospital appointments, transport to the specialist, pharmacy items, a phone line, an outing. Small, variable, billed monthly on top — or paid at the desk by whoever visits on Sunday. Individually trivial; collectively, a real slice of margin and an enormous share of the administrative work.

The one-offs. The admission fee or first-month deposit at move-in, a respite stay of two weeks while a family travels, a day-centre package, the room reservation held while the family decides. High-emotion, time-critical, and almost always agreed by phone with someone in another country.

Three billing shapes. One finance office, usually one person, often the owner. And the payment tools available to them were designed for a shop counter with a customer standing in front of it.

What the wrong rail costs a residence every single month

The transfer fee is regressive and it never stops. Sending money across a border is priced per transaction — a flat handling fee at origin, whatever the correspondent banks deduct along the way, and an exchange-rate spread that is quietly the largest component. The World Bank tracks this globally in its cost of sending remittances series, and the structural point matters more than any single number: the cost does not scale down with the amount. A family sending a modest monthly fee pays roughly what a family sending a large one pays. Multiply by twelve, then by the number of years a resident stays, and the amount that evaporated between the son's account and the residence's account is a meaningful sum — usually more than a year of the physiotherapy the family declined because it was an extra.

The month that arrives short. The son transfers the full fee. The residence receives less. Nobody is lying: a correspondent deducted, or the receiving bank applied its own charge, or the rate on the day of crediting was not the rate on the day of sending. Now the residence's administrator has to open a conversation that begins "your mother's account is short" with a family that is already stressed, already stretched, and already suspicious that they are being nickel-and-dimed. That conversation is expensive in a way no spreadsheet captures.

Arrears you cannot act on. This is the fact that makes this vertical unlike every other subscription business. When a gym member's card fails, the gym cancels the membership. When a resident's fee fails, the residence keeps feeding her, medicating her, changing her bed, and staffing her floor around the clock — because that is what a care home is, and because the alternative is legally, contractually and morally unavailable. Staffing is the dominant cost in this sector and it is a 24-hour cost. Your revenue can pause; your costs cannot. Every day between "the payment failed" and "the payment cleared" is financed by the residence.

The silent recurring failure. If the monthly fee is billed to a card, it is billed to a card that expires, gets reissued after a breach at an unrelated retailer, or trips an authentication step-up sent to a phone number in a country the payer left. The charge fails. Nobody cancelled anything. Your dunning email goes to an address the son checks weekly. You discover it when the month-end report shows a bed occupied and unpaid — the exact failure mode described in crypto subscriptions without chargebacks, except that here you cannot switch the service off.

The disputed month after a hospitalisation or a death. A resident is admitted to hospital on the 6th and dies on the 24th. Six weeks later a family member, grieving and looking at a statement, disputes the month with their issuer: "she wasn't even there." Whether your contract entitles you to that month — and in most residences, with a notice period and a held room, it does — is not a question the issuer is well equipped to answer. Card dispute windows documented in network materials such as the Visa Core Rules give months for that reversal to arrive, and it arrives against a service you already delivered, with staff you already paid.

The three-way split with no reference. Three siblings, three transfers, three different amounts, three different days, three different sending banks, and a description field that says "TRF 4471". Your administrator is now doing forensic reconciliation to work out whether Mrs. Álvarez's March is fully covered, and the answer is often "almost". Partial months are the single largest source of accounts-receivable noise in this vertical.

The informal channel. Where cards fail and transfers are expensive or restricted, families improvise: cash carried by a cousin who is flying home, a friend of a friend who "handles it", a parallel exchange rate agreed over WhatsApp. The residence ends up receiving cash from a stranger against a resident's account, with all the reconciliation, security and record-keeping problems that implies — and with no clean audit trail for either side.

The acquirer's read on you. Recurring billing, cross-border payers, an intangible service, high average tickets, occasional disputes tied to bereavement. That profile is not what a conservative acquirer wants to underwrite. The answers are familiar: a higher rate, a ceiling, delayed settlement, or a rolling reserve that holds back your cash precisely while payroll, food supply and utilities fall due on fixed dates.

The payout side, which nobody budgets for. Night cover carers, weekend agency shifts, the physiotherapist who comes twice a week, the podiatrist once a month, the visiting hairdresser, the gardener, the freelance activities coordinator. It is a long list of small, frequent, individually-transferred payments — and it is exactly the pattern targeted by payee-impersonation fraud. The FBI's Internet Crime Complaint Center has documented for years that business email compromise is among the costliest categories of cyber-enabled crime, and "my bank details changed" arriving the day before the payout run is the classic vector. Verifying payee details out of band is the control that matters on any rail.

Why cards, wires and remittance apps each break on a care fee

None of these rails is badly built. Each was designed around an assumption that a senior care home violates.

Cards assume a domestic, stable credential. Recurring card billing is excellent when the cardholder lives in the same market as the merchant and keeps the same card for years. It is at its worst when the payer is a foreign cardholder making a repeated, card-not-present, cross-border charge to a category the issuer's risk model has never seen from that customer before. Declines here are not fraud; they are a model being cautious about an unusual pattern. But the residence experiences them as unpaid months.

Cards assume a merchant who can prove delivery. The dispute framework was designed around goods: tracking numbers, delivery confirmations, signatures. What a residence delivers is 720 hours of continuous care to a person. Your evidence is a care plan, a medication log and a signed admission contract. That is real evidence and it is far better than nothing — but it is being evaluated inside a process built around parcels, months after the fact, by someone who never read the contract.

Wires assume banking hours and a large amount. An international transfer has a cut-off time, a value date, a chain of intermediaries and a fee structure that makes sense on a shipment of machinery. On a recurring monthly care fee, it is an expensive, slow and opaque instrument used twelve times a year, forever.

Remittance apps assume a person, not an invoice. They are built to move money from a worker abroad to a relative's hands or local account — priced for that, designed for that, and paid out in local currency at a rate the sender does not control. Some families use them to pay a residence anyway. What arrives is a local-currency amount with no reference, no invoice number and no resident name your accounting system can match, and the FX difference between what was sent and what the fee costs lands on whoever is least able to argue.

And all of them assume the payer's country lets money out easily. A large share of the families financing care in Latin America live with currency controls, transfer quotas, cards blocked for foreign recurring charges, or an official rate nobody transacts at. For those families, a dollar-denominated stablecoin is not an exotic instrument — it is what they already hold, because it is the only savings vehicle that survived the last decade. We wrote the general version of this in getting paid from abroad without a bank account; in senior care it is not an edge case, it is the median customer.

How Payzum lets a senior care home accept crypto payments — from abroad, at reception and on the payout run

Payzum is a non-custodial, crypto-only payment processor. Both halves matter here.

Non-custodial means the money never sits in a Payzum balance. It goes from the payer straight to wallets your residence controls. There is no processor float, no settlement delay, no reserve, and nothing for a third party to hold back while payroll falls due on the 30th. The settlement is the payment.

Crypto-only means the rail is on-chain and the payment is final once confirmed — roughly 0.4 seconds on Solana, around two seconds on Base and Polygon. A son in Madrid can pay at 23:40 on a Sunday and the administrator in Buenos Aires can see the month settled before Monday's handover meeting. And because you can auto-convert to USDC or USDT, "crypto" does not have to mean price movement; see USDT vs USDC for payments for the difference between the two.

The instruments, mapped to how a residence actually bills

• Recurring subscriptions — the monthly fee. This is the flagship for this vertical. The base rate plus care level, billed monthly, with nothing behind it that can expire, be reissued, or trip an authentication step-up on a phone in another country. A plan ends when the family ends it or the resident's stay ends — not because a bank in a different hemisphere sent out new plastic.
• Invoices with an expiry, a resident reference and overpayment detection. The second flagship, and the answer to the three-siblings problem. Each invoice carries the resident code and the period, so a payment reconciles itself instead of arriving as an unlabelled transfer. Overpayment detection catches the sibling who rounds up, the family that pays two months in one go, or the payer who adds the extras to the base fee without telling anyone. The expiry is set to the date that actually matters — your billing cut-off, not an arbitrary one.
• No-code payment links. For everything that is not monthly: the admission fee or first-month deposit agreed on the phone before the move-in, the respite fortnight booked by a daughter before she travels, a room held while the family visits, an unusual extra like a private companion for a three-day hospital stay. Sent by email or WhatsApp to whichever relative is handling it, in whichever country they are in.
• Hosted checkout and a drop-in plugin. Behind the family portal or the "pay this month" button on your site, so a payer who wants to handle it themselves at midnight can, without emailing your administrator.
• POS with a fresh QR per sale and PIN cashiers. At reception, for the family that visits on Sunday and settles the hairdresser, the podiatry session and the pharmacy items on the spot. One PIN per staff member on the desk, with analytics per cashier — which is how a residence gets a clean record of the extras without a petty-cash tin. The mechanics are the same ones described in turning a phone into a crypto POS and crypto POS with PIN cashiers.
• CSV mass payouts and EVM stablecoin payouts. One file for the night cover carers, the weekend agency shifts, the visiting physiotherapist, the podiatrist, the hairdresser and the activities coordinator — on Polygon, Arbitrum, Optimism, Base, BNB Chain or Avalanche, plus BTC/LTC/DOGE batches. The format is walked through in bulk crypto payments by CSV.
• REST API with signed webhooks. Your residence management software learns the month is settled the second the payment confirms: the account is marked current, the dunning sequence stops, the family portal updates, and nobody re-keys anything.

What actually happens on the first of the month

The subscription charges, or the invoice for Mrs. Álvarez's March goes out with her resident code as the reference. The son opens it wherever he is, pays from the stablecoin balance he already holds, and it confirms in seconds. Your administrator sees the month settled, attributed to the right resident, with the reference attached. The funds are in the residence's wallet — not in a processor's account, not in a batch that settles Tuesday, not in a reserve.

If two siblings each pay a share, both payments land against the same reference and the shortfall or the surplus is visible immediately rather than at month-end. If someone overpays, you know, and you can credit it or return it deliberately instead of discovering it in a reconciliation three weeks later.

The change is not primarily about speed. It is that the month is settled and stays settled — and your administrator spends the morning on care admin instead of on payment archaeology.

Honest scope: finality cuts both ways, and in this vertical that deserves a paragraph

On-chain finality removes chargebacks. It also removes your ability to reverse a payment that was made in error. Those are the same property viewed from two sides, and a residence should understand it before switching anything on.

In practice it means three things. First, overpayment detection and a written refund policy do real work here — when a family pays twice, or pays a month that a deceased resident's contract does not owe, the credit or the refund is a payment your residence initiates, from your wallet, on your books, on your timeline. That is more control than a card rail gives you and it is also more responsibility. Second, your admission contract's provisions on notice periods, held rooms, fee changes and what happens on hospitalisation or death should be clear before you use a rail that does not permit third-party reversals, because the contract is now the whole agreement — nobody is going to arbitrate it for you.

Third, and most important: a payment method for a care home is a safeguarding question, not just a finance question. The payer should be the responsible person named on the admission contract — the family member, representative or legal guardian who agreed to the fees — not the resident being handed a phone. No member of your staff should ever assist a resident to make an irreversible payment from a wallet, and no wallet should ever be set up on a resident's device by the residence. Any organisation selling crypto payments into elder care without saying that out loud is not thinking about your risk. We are: the rail is for collecting your fees from the people contractually responsible for them, full stop.

Where this fits — and where it does not

This is a private-pay tool. It fits residences and care homes whose fees are paid by families, and it fits the private extras billed alongside a place that is otherwise funded. It does not fit the parts of your revenue that come from a public authority, a long-term-care benefit, a social-security programme or a health insurer. Those payers have their own mandated payment processes, their own timetables and their own reporting, and none of them are going to pay a stablecoin invoice. If most of your beds are publicly funded or insurer-paid, be honest with yourself: this is a tool for the private minority of your revenue, and the value is proportional to that share.

It also has nothing to do with residents' personal money. Many jurisdictions regulate resident personal-fund or trust accounts — the small balances a residence may administer for a resident's own spending — with strict segregation, record-keeping and accounting duties. Payzum holds nothing and is not a trust account, so those obligations are unchanged and those funds should stay exactly where your regulator expects them. Use this rail for the residence's own fees and extras, and keep resident money separate, as you already do.

What else this rail does not do

Payzum is a payment rail. It is not your operating licence, not your inspection regime, not your staffing ratios, not your care standards, not your insurance, not an escrow agent, not a payroll bureau or employer of record, not a debt collector, and not a tax engine. Admission contracts, fee-increase notice rules, consumer protections for older people and their families, data protection over health information, employment classification for your carers and every reporting duty you have all remain exactly where they were: with you.

And one thing worth saying plainly, because it is the honest limit of what a payment rail can do: no rail makes a family pay. Arrears are a credit and relationship problem, and they will still be one. What this removes is the money arriving late, arriving short, arriving unlabelled, or being pulled back months after the care was delivered.

Volatility is a setting, not a risk

The objection every operator raises first: "I run a care home on thin margins — I cannot hold something that moves." You do not have to. Accept whatever the family holds and auto-convert to a dollar-denominated stablecoin — USDC or USDT — so what lands in the residence's wallet is a dollar amount against a dollar-denominated fee. The chain is the transport; the stablecoin is the unit of account. Many residences in high-inflation markets already price the private fee in dollars precisely because their families do.

How it works, step by step

1. Connect your wallets. Create the Payzum account and point it at wallets the residence already controls — most operators run two: one for fees and one for extras and the reception desk. Turn on auto-convert to USDC or USDT, and enable 2FA. Nothing sits with Payzum at any point.
2. Set up the monthly fee as a subscription per resident. Base rate plus care level, on your billing day. When the care level changes after an assessment, you change the plan — there is no stored card to re-authorise and no bank to re-approve a new amount.
3. Give every invoice a resident reference. Resident code plus period, with an expiry on your billing cut-off and overpayment detection on. This is what turns the three-siblings split from a monthly puzzle into a line that reconciles itself.
4. Create links for the one-offs. Admission fee and first-month deposit, respite stays, day-centre packages, room reservations, unusual extras. Sent to whichever relative is handling it, wherever they are, closed the same day instead of waiting three days for a wire.
5. Put a PIN cashier on the front desk. Reception collects the visiting-day extras with a fresh QR per sale, under their own PIN, with per-cashier analytics — a clean record of the hairdresser, the podiatry and the pharmacy items without a cash tin.
6. Connect the residence software. REST API and signed webhooks, so a confirmed payment marks the month settled, stops the dunning sequence and updates the family portal automatically.
7. Run the payouts from one file. Night cover, agency shifts, visiting professionals and freelancers in a single CSV — verifying any changed payee details out of band before you send it. Same rail, opposite direction.

Use cases at a senior care home

Four situations that happen in every residence with international families, and what each looks like on this rail.

• The son abroad who pays every month, forever. His mother has been with you for three years. Today he sends a transfer that costs him a fixed fee plus a spread, arrives in two or three days, sometimes short, and carries a reference nobody can read. On a subscription, the fee is charged on your billing day, confirms in seconds, and lands as the exact amount, in a dollar-denominated stablecoin, attributed to his mother's account — twelve times a year, without a phone call.
• Three siblings, three shares, one March. One in Miami, one in Madrid, one who stayed. Each pays a portion of the same invoice, which carries the resident code and the period. Your administrator sees, in real time, how much of March is covered and by whom, and overpayment detection flags the sibling who paid the full amount because he had not seen the group chat. No forensic reconciliation, no awkward "your mother's account is short" email.
• The respite fortnight, booked from another country in an afternoon. A daughter abroad needs two weeks of respite care for her father starting on the 12th, and she needs the place confirmed today. You send a payment link, she pays from wherever she is, it confirms in seconds, and the bed is committed with the money already received — instead of holding a room against a promised wire that may or may not clear before the weekend.
• Sunday visiting day at the front desk. A family visits, and settles the month's hairdresser, two podiatry sessions and the pharmacy items on a QR generated for that sale, under the receptionist's PIN. The extras stop being a notebook and a tin, and start being a per-cashier report the owner can read on a phone.
• The Friday payout run. Night cover carers, two weekend agency shifts, the physiotherapist, the podiatrist and the hairdresser — one CSV, one batch, settled the same day, with payee details verified out of band beforehand. The same file every week, and no stack of individual transfers with individual fees.

Payzum vs international transfers and cards for a senior care home

Common objections, answered

"Our residents are in their eighties. They will never use crypto."

They will not, and they should not have to. In this vertical the resident is almost never the payer. The person you are asking to pay is their son or daughter — typically between 40 and 60, living abroad, working in another currency, and in many corridors already holding dollar-denominated stablecoins because that is how their savings survived. The payment happens on a phone four thousand kilometres from your building. Nothing about it lands on the resident, and nothing about it should.

"Isn't this an odd thing for a care home to be doing?"

What a care home is doing is collecting a recurring fee from a payer abroad. That has always been a cross-border payments problem wearing a healthcare uniform. Families in this position are already using whatever works — international transfers, cards that decline, remittance apps, and sometimes cash in a cousin's suitcase. Offering a rail that arrives in seconds, in a dollar-denominated unit, with a resident reference attached, is the least improvised option on that list, not the most.

"We already accept international transfers. What changes?"

Three things. The amount you receive equals the amount that was sent, so nobody has to explain a deduction. The money is settled in seconds instead of days, so a respite booking or an admission is confirmed while the family is still on the phone. And it cannot be reversed six weeks later against care you already delivered. If your families are all domestic and pay by direct debit without incident, you do not need this. If any meaningful share of your fees crosses a border, you do.

"What about our accountant?"

A fee collected in USDC is revenue, recorded on the day it is received, at the value of the day, against the resident's account — the same as any other payment. Your invoice, your fee schedule, your ledger and your tax obligations are unchanged. What changes is that the receipt reconciles cleanly to an invoice reference instead of to a partial transfer with an unreadable description. Confirm the treatment in your jurisdiction with your own accountant; we are a payment rail, not your adviser.