Transaction-level status (your integration)
Dollr does not replace per-payment polling with a single global “API up” flag for your checkout flow. Use the Status API for each transaction:
Guide: Transaction Status · API Reference
Two status models — Execution status (funds movement) and source status (
IDLE → PAID on invoices/orders) are different. Do not treat PROCESSING on an execution as a failed invoice.
Realtime updates (optional)
For active checkout sessions, generate a Realtime Key to subscribe to push events instead of polling. Keys are short-lived; refresh per session.Platform & API availability
If Dollr publishes a public status page for the API platform, it will be linked from the dashboard and Help Center. Subscribe there for incident start/resolution notifications.
What to do during an incident
- Confirm scope — Is the failure isolated to one
method/market or all API calls? - Check auth — Rule out expired tokens (
401) before assuming platform outage. - Stop blind retries — Use existing
reference_idand status endpoints before re-executing. - Capture evidence — Timestamp (UTC), endpoint,
reference_id, response bodies. - Contact support — Email dev@heydollr.app with the checklist in Error catalog.
Post-incident
After recovery, reconcile any payments left inPROCESSING by polling status with the original reference_id. Do not issue duplicate executions for the same customer charge without verifying the first attempt failed.