Skip to main content

​
Contract

  • Sandbox and live base URLs are confirmed and .example placeholders are gone.
  • Supported currencies, countries, routes, and account types are approved.
  • External routeId provisioning is documented and tested.
  • Versioning, deprecation, error-code, and status-lifecycle policies are approved.
  • Rate-limit header behavior and webhook retry policy are explicitly approved.
  • Support contact, hours, severity definitions, and response targets are published.

​
Verification

  • npm run generate produces no unexplained diff.
  • npm test passes against the matching API revision.
  • npm run docs:validate, npm run docs:links, and npm run docs:a11y pass.
  • npm run check:ready passes.
  • Every cURL, Node.js, and Python request example succeeds in sandbox.
  • The transfer tutorial succeeds for a fresh sandbox business.
  • Duplicate externalReference, timeout, 429, and 5xx recovery paths are tested.
  • Valid, invalid, stale, duplicate, and manually resent webhooks are tested.
  • A developer unfamiliar with Sakawave completes the quickstart without assistance.

​
Approval and operations

  • API engineering approves request, response, error, rate, and lifecycle accuracy.
  • Security and product approve credential, masking, webhook, and public-behavior guidance.
  • Monitoring covers authentication failures, rate-limit failures, transfer failures, webhook delivery, and reconciliation lag.
  • On-call and support teams can search by X-Request-ID, external reference, transfer ID, and transaction ID without viewing secrets.
  • A rollback and customer-communication plan exists for documentation or contract regressions.