01Accept
Charges and payment links
Create a charge against a customer wallet, or a hosted payment link for a fixed or open amount, and receive the result on a webhook.
Paydoly DeveloperIn development
Build financialexperienceson Paydoly.
One API over the same ledger the apps use: accept payments, issue payouts, read movements, and reach the agent cash network programmatically. Currently in private beta with selected partners.
01
Status, stated plainly
The Paydoly API exists and runs the products on this site. What is not yet open is self-serve external access: documentation, keys and sandbox provisioning are being prepared for public release.
Until then we onboard partners individually. If you have a concrete integration in mind — a platform paying out to sellers, a biller collecting recurring payments, a marketplace settling in two currencies — write to developers@paydoly.com describing the flow and the volume you expect.
We will not publish a reference before the platform behind it is stable. When external access opens, the documentation and the platform ship together.
02
What the API covers
The surface available to beta partners today.
02Pay out
Transfers and cash payouts
Send funds to a Paydoly wallet, a bank destination, or an agent counter for cash collection with a reference the recipient presents.
03Read
Balances and movements
Query balances per currency, list movements with settlement state, and reconcile against your own ledger with stable identifiers.
04Exchange
Quotes and conversion
Request a DOP/USD quote, accept it within its validity window, and convert — the same quote mechanic the apps use.
05Invoices
One-off and recurring
Issue invoices with a pay page, schedule recurring cycles, and track paid, overdue and cancelled states.
06Webhooks
Signed, replayable events
Every state change emits a signed event. Events are retried with backoff and can be replayed from the dashboard for a rolling window.
03
Integration path
What a beta onboarding actually looks like.
- 01Describe the flowA short note on what money does in your product: who pays, who gets paid, in which currency, and how fast it needs to settle.
- 02Sandbox accessWe provision a sandbox with test wallets, test merchants and simulated agent counters, plus keys scoped to it.
- 03Build against webhooksIntegrate the two or three endpoints your flow needs, and handle the events. We review your reconciliation approach before you go live.
- 04Compliance review and launchEntity verification, a look at your own onboarding and refund handling, then production keys with limits that rise as volume proves out.
04
Technical shape
Enough detail to tell whether it fits your stack.
- Protocol
- HTTPS REST with JSON bodies, idempotency keys on every mutating call, and cursor pagination on collections.
- Authentication
- Per-environment secret keys with scoped permissions, rotated on demand. Webhook payloads are signed; verify the signature before acting.
- Currencies
- DOP and USD, always with an explicit currency on every amount. Amounts are integer minor units.
- Environments
- Sandbox and production, fully separated, with test agent counters in sandbox so cash flows can be exercised end to end.
- Rate limits
- Published per endpoint class, with headers on every response. Limits are raised on request once traffic patterns are understood.
05
Questions we get
When does public access open?
When the documentation, sandbox provisioning and support path are all ready together. We are not announcing a date we would then have to move.
Can I start building now?
Yes, as a beta partner. Access is granted per integration rather than per signup, and it comes with a named contact rather than a forum.
Is there a card-acquiring API?
No. Paydoly acceptance is wallet, link, invoice and agent cash. Cards are not part of the current platform.
What does it cost?
Transaction pricing matches the published business rates. There is no platform or API fee during the beta.