Dots review

Dots is a hosted payout API and SaaS platform, not a payment library, CLI or self-hosted server. It sits between a business's application and the people it pays: the business uses Dots to onboard recipients, collect payout details, initiate payments and track transfers. The vendor says the platform supports 190+ countries through 300+ payment rails.

The product also includes a dashboard and recipient-facing flows. Dots Onboard can collect payout information, verify identity and screen against sanctions lists. Dots Tax collects and validates tax information and supports filing forms in the US and Canada. White-label options range from a hosted recipient experience to embedded components and wallets, according to the product details. This makes Dots relevant to marketplaces, creator platforms and other services that need to move money to external recipients without building every payout and compliance workflow themselves. The platform is managed by Dots; it is not positioned as infrastructure you run inside your own environment.

The main developer integration surface is the Dots Payouts API. The homepage links to complete API documentation and describes the API as a way to integrate payouts into an application. It also presents payout automation, payment tracking and reporting as platform capabilities. Use the API docs to confirm supported SDKs, languages, authentication, request patterns and any webhook support before choosing an integration approach.

Dots also offers a dashboard, payout links and white-labeled recipient onboarding. The product details describe no-code setup, a one-line embed, drop-in components and white-labeled wallets. Those options can reduce the amount of recipient-facing UI a team must build, while the API supports application-level integration. Dots does not name a CLI or specific programming-language SDKs in its homepage material, so confirm SDK support in the vendor's docs. The key implementation questions are how your system creates and reconciles transfers, handles failed payments and receives status changes; verify the relevant API behavior and examples with Dots before production.

Dots has no listed free plan or free trial. Dots Core starts at $19 per month and includes domestic and international payouts, ID verifications and 1099 tax compliance. Its transaction charges include $2 for domestic payouts and 3.9% + $2 for international payouts. Other listed Core charges include $5 for 1099s, $5 for ID verification and $40 for international wires.

Dots Scale costs $999 per month and adds API access, wallets, a white-labeled experience, an assigned support contact and 24/7 recipient support. Its listed payout charges are $1 for domestic payouts and 2.9% + $1 for international payouts. Push-to-card, crypto, tax and wire fees are separate. Dots Enterprise has no published monthly price; transaction fees are quoted by sales. The pricing page lists monthly plan prices but does not state whether annual billing is available. Model fees against payout volume and rail mix rather than treating the monthly plan price as the full cost.

Dots presents itself as a managed platform accessed through its API and dashboard, not as a self-hosted server or installable library. The vendor does not publish a source-code licence or describe an open-source edition in the product material, so teams should treat Dots as hosted infrastructure unless the vendor confirms otherwise.

The vendor also does not describe data-export formats or a migration path. Ask how to export recipient records, tax data, transfer history and reconciliation reports, and whether those exports remain available after a contract ends. Moving away would likely require replacing the payout integration and reworking recipient onboarding, payment status handling and tax workflows. The difficulty depends on how much of the application is built around Dots-specific flows and data. Keep an internal record of payment states and recipient identifiers where permitted, and confirm contractual access to historical records before relying on the platform.

Dots says it supports 190+ countries and 300+ rails, with automatic routing intended to select a fast, cost-effective rail. That reach does not remove the need to verify which payout methods are available for your recipient countries, currencies and business model. Dots also advertises identity checks, sanctions screening and tax collection, with tax filing in the US and Canada; confirm which checks and filings apply to your use case.

Before launch, ask Dots for API rate limits, retry and idempotency behavior, payment-status guarantees, uptime targets and incident procedures. The public product details do not publish those limits or service targets. Confirm how exchange rates and fees are presented, how failed or returned transfers are handled, and what reporting or data exports your reconciliation process can use. The platform's support offer differs by plan: Scale lists an assigned support contact, a dedicated Slack channel and 24/7 recipient support. Include those operational terms, transaction fees and country coverage in production planning.