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:
| Operation | Poll execution status |
|---|
| Collection | GET /v1/status/collection/{reference_id} |
| Payout | GET /v1/status/payout/{reference_id} |
| Transfer | GET /v1/status/transfer/{reference_id} |
| Refund | GET /v1/status/refund/{reference_id} |
| Invoice / order document | GET /v1/status/source (source lifecycle) |
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.
| Channel | Use for |
|---|
| Merchant Dashboard | Account alerts, maintenance notices, support tickets |
| Help Center | Known issues, integration FAQs, procedural updates |
| dev@heydollr.app | Confirmed outages, prolonged 5xx, or data discrepancies |
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_id and 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 in PROCESSING by polling status with the original reference_id. Do not issue duplicate executions for the same customer charge without verifying the first attempt failed.
Last modified on May 22, 2026
