v2 REST + GraphQL · eu-west-1

Move money without the mess.

AcmePay is a single API for payments, payouts and reconciliation. Built for marketplaces, fintechs and SaaS platforms that outgrew bolt-on billing.

Idempotent by default Ledger-backed reconciliation OpenAPI 3.1 spec
bash
# create and capture a payment
curl https://api.acmepay.duckdns.org/api/v2/payments \
  -H "Authorization: Bearer $ACMEPAY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d amount=4200 -d currency=gbp -d capture=true

{
  "id": "pay_3Nk8Qv2aLdZ",
  "status": "succeeded",
  "amount": 4200,
  "currency": "gbp"
}
200 OK

Powering payments for modern platforms

Northwind Kestrel Loop Meridian Harbor Fathom

Platform

One API, three primitives

Accept money, send money, and reconcile every movement against a single ledger.

Payments

Card, bank debit and wallet acceptance through one /payments resource. Idempotent by default.

Payouts

Push funds to sellers and users on your schedule. Batched or real-time via /payouts.

Reconciliation

Every movement is a ledger entry. Export to your warehouse or pull it live over GraphQL.

Architecture

Built on a modern stack

The AcmePay platform runs as a set of small services behind a single API gateway. The public API is REST with a GraphQL read layer; everything is documented with OpenAPI at docs.acmepay.duckdns.org.

Public APIhttps://api.acmepay.duckdns.org/api/v2 · REST + GraphQL
Docsdocs.acmepay.duckdns.org (OpenAPI / Swagger)
Statusstatus.acmepay.duckdns.org
Regionseu-west-1 (primary)
1API for money movement
REST + GraphQLWrites and reads
OpenAPI 3.1Spec-first, always
eu-west-1Primary region

Customers

Trusted by finance teams

“We migrated three billing integrations onto AcmePay in a quarter.”

— Head of Payments, a marketplace

“The ledger model finally made month-end close boring.”

— Financial Controller, a SaaS platform

Start building today

Read the API reference, spin up a sandbox, and make your first request in minutes.