Skip to main content
Use Cursor, Claude Code, Codex, or any coding agent to integrate Dollr faster without skipping auth, idempotency, or market-specific payment rules.

Start here

Environment, context files, and IDE setup.

Prompt library

Copy-ready prompts for collect, payout, debug, and review.

AI & MCP

llms.txt, documentation MCP, and agent checklist.

Quick Start

Human-readable first collection walkthrough.

​
Rules every session should follow

  1. Server-side only — DOLLR_CLIENT_SECRET never in browsers, mobile apps, or public repos.
  2. Attach context — llms.txt plus the relevant stack guide or Quick Start.
  3. One flow per task — collect or payout or checkout; not the entire API at once.
  4. Idempotency — UUID v4 reference_id before POST /v1/executions/*; poll status before retrying.
  5. Two status models — execution status vs invoice/order status; MoMo may stay PROCESSING for minutes.
  6. Markets — use Payments by market; predict MoMo operator from phone when possible.
Documentation MCP (https://docs.heydollr.app/mcp) helps AI read these docs. It does not execute payments. API calls go to https://api.heydollr.app.

​
When to use prompts vs guides

UseWhen
Prompt libraryYou want the model to generate or refactor integration code
Integrate by stackYou want step-by-step reference while coding
API ReferenceYou need exact request/response fields
Last modified on May 22, 2026