Skip to main content

​
Bug fixes

​
Thrizer Pay restored for clients who were incorrectly shown Self-Pay

Some clients on Thrizer-Pay-eligible insurance were silently defaulted to Self-Pay at checkout, even though their payer supports Thrizer Pay. We identified the affected accounts and restored their eligibility evaluation. Thrizer Pay availability still depends on all eligibility conditions, including a met deductible and at least one prior successful claim that establishes coverage calibration. Meeting the deductible alone does not make Thrizer Pay immediately available. Who this affects: clients on Thrizer-Pay-eligible payers whose sessions had been charged as Self-Pay in recent weeks. What to do: clinicians — the next time you charge one of these clients, the payment types for which the client is currently eligible should appear automatically. If a client still looks wrong, contact Thrizer support. See Payment types and eligibility.

​
Onboarding no longer stalls for some returning clinicians

A small group of clinicians with older accounts saw the final step of onboarding fail with an unexpected error, leaving them unable to finish setup. Onboarding now completes successfully for these accounts. Who this affects: clinicians who signed up under a referral code and were previously stuck on the last step of onboarding. What to do: if you were blocked earlier, sign in and finish onboarding — no need to contact support. See Getting started as a clinician.

​
Payments page loads again for clinicians with long-lived sessions

Some clinicians hit a “Failed to fetch payments” error when opening the Payments page after being signed in for a long time or across several Thrizer tabs. The Payments hub and client Payments tabs now load reliably in these sessions. Who this affects: clinicians who kept Thrizer open across many tabs or long sessions and saw payments fail to load. What to do: nothing — just reload the page. See Payments, payouts, and refunds.

​
Support ticket attachments are more reliable on mobile

Attaching a photo to a support ticket from a phone sometimes failed after the photo picker returned, and retrying didn’t help. Now, if an attachment can no longer be read, Thrizer asks you to re-add the file and clears the stale attachment. This can happen when the browser cleans up the file after you switch apps. You can then submit successfully on the next try. Genuine network interruptions during upload now show a clear “upload was interrupted” message instead of a generic error. Who this affects: anyone submitting a support ticket with a photo or file attachment, especially from a mobile device. What to do: if you see the “please re-add your file(s)” message, tap the attachment field again to reselect your photo, then submit.