Contract notes
Understand what the source establishes and what needs deployment confirmation.
Examples are not complete schemas
Request/response examples preserve source field names and types, but do not prove all requiredness, validation bounds or HTTP success codes. The source's mixed status casing and envelopes are intentional in these docs.
Local source versus production
Local backend review confirmed the six-line merchant HMAC construction and clarified plugin timestamp/hex encoding. Collection creation and payout initiation use HTTP 201 in local controllers; payee creation is documented in user testing as HTTP 200. No live endpoint was called while building this documentation.
Open integration questions
Confirm deployed schemas, complete error/status vocabularies, webhook canonicalization and retry policy, idempotency retention/concurrency, balance semantics and merchant-specific permissions. A verified response for a dummy payee does not establish live bank-provider validation.
Unpublished capabilities
No standalone sandbox, official SDK package, live execution console or public merchant mandate API is advertised here. Dashboard-only operations remain outside the public API specification.