Docs
Everything you need to integrate Baynoy: accept payments, manage accounts and cards, and move crypto — from one API.
Not live yet — api.baynoy.com does not resolve, so the examples below will not run today. They describe the contract we are building to, and the shapes on this page may still change.
One API for money in, money held, money out
Payments, accounts, payouts, cards and crypto share one REST API, one error envelope and one idempotency model. Amounts are always integers in the currency's smallest unit with an explicit currency code — floats are never accepted or returned.
Authentication
Keys can be created in the dashboard today, and they are real — but api.baynoy.com does not resolve yet, so there is nowhere to send them. When it does: server-to-server calls use secret keys (bk_test_/bk_live_) as a Bearer token, publishable keys only start checkout sessions, and payouts, refunds and card reveal require separately scoped keys.
curl https://api.baynoy.com/v1/payment_links \
-H "Authorization: Bearer bk_test_..." \
-H "Idempotency-Key: 4f7c9a2e-..." \
-d amount=4900 -d currency=EUR -d title="Design retainer"Versioning
The major version lives in the URL (/v1). Additive fields arrive without notice — tolerate unknown fields; breaking changes only ever ship as a new version with a dated migration guide.