Docs
Tout ce qu’il faut pour intégrer Baynoy : accepter des paiements, gérer comptes et cartes, et déplacer de la crypto — depuis une seule API.
Pas encore en service — api.baynoy.com ne résout pas, les exemples ci-dessous ne fonctionneront donc pas aujourd'hui. Ils décrivent le contrat que nous construisons, et les formes de cette page peuvent encore changer.
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 a secret key (bk_test_/bk_live_) as a Bearer token, each key carries only the scopes you gave it, and money-moving requests are also signed with the key's signing secret.
curl https://api.baynoy.com/v1/catalog/links \
-H "Authorization: Bearer bk_test_..." \
-H "Content-Type: application/json" \
-d '{"title": "Design retainer", "amountMinor": "4900", "assetKey": "fiat:EUR"}'
# -> {"id": "lnk_...", "slug": "k3x9q2"} — the page is https://baynoy.com/pay/k3x9q2Versioning
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.