Documentation / API Reference
Public developer guidance for the supported SelamNow integration surface, onboarding model, and controlled access path.
Review supported banking capabilities, integration access, and onboarding steps. Institution-specific endpoints and integration details are shared during approved onboarding.
Sandbox endpoints, keys, scopes, workspace identifiers, and production cutover details are shared only after solution fit, ownership review, and security alignment are complete.
SelamNow expects integrations to enter through the supported API and gateway boundary rather than through direct databases, unowned services, or extension-layer shortcuts.
After initial discovery, teams move into architecture review, sandbox enablement, test evidence, and rollout planning so the eventual implementation stays operationally safe.
Public-facing discovery covers accounts and customer servicing, payments and transfers, lending and portfolio workflows, and reporting and compliance interfaces, without exposing internal routing, runbooks, or privileged management operations.
Teams clarify the institution, channel, and stakeholders, pass architecture and security review, receive sandbox enablement, and move through evidence capture before production onboarding.
Need controlled API access?
Use the public reference to scope your use case, then engage SelamNow for sandbox access, credentials, and institution-specific contracts.