Skip to main content

Forward compatibility

Last updated: 2026-05-04

To keep your integration stable as the API evolves:

  1. Ignore unknown JSON fields. New fields can be added without a version bump.
  2. Be tolerant to new enum values. Treat unknown enum strings as "unknown" and handle safely.
  3. Do not rely on strict schemas that reject additional fields (common issue with some generated clients).
  4. Prefer reading merchants.swagger.json for contract shape, and this documentation for request validation, webhooks, and integration flow.
  5. Treat mobile-money operator codes as discovery-driven values, not as a stable swagger enum. Reuse discovery results as returned.