Documentation Index
Fetch the complete documentation index at: https://docs.veridianhp.com/llms.txt
Use this file to discover all available pages before exploring further.
Quickstart
This walk-through takes you from an empty Veridian account to a completed sandbox ACH payment in about 15 minutes. No production credentials, no real money, no real PHI.Get your sandbox API key
After your account is provisioned, sign in to the
Veridian dashboard and create a sandbox
API key from Settings → API keys.Sandbox keys look like:Sandbox keys never touch live money and are safe to use in development.
Keep them out of public repos anyway.
Create a payment session
A session represents one patient invoice that’s ready to be paid.
Create one from your server:You’ll get back a
sessionId and a hostedUrl. The hosted URL is what
you send to the patient.Open the hosted payment page
Open the
hostedUrl from the previous step in a browser. You’ll see the
Veridian Bridge — a branded, mobile-friendly page showing the patient
what they owe and inviting them to pay.In sandbox, you can use the test bank credentials provided in the
Veridian dashboard to simulate a successful or failed bank connection.Listen for the webhook
When the payment completes, Veridian sends a signed webhook to the URL
you configured in Settings → Webhooks.A successful payment looks like:Verify the signature using the secret shown in the webhook settings page.
See Webhooks for the verification recipe.
You’re done
You just ran the same path a real patient would: create session → patient pays → webhook fires → status updates. The only differences in production are the API host, your live API key, and that the money actually moves.What’s next
Production integration
Move from sandbox to live with confidence — checklist included.
Webhook patterns
Retries, idempotency, signature verification, replay protection.
