Endpoint Documentation
Each API operation is documented with its endpoint, HTTP method, authentication requirements, mandatory fields, optional parameters and expected response.
Bring payment workflows into your applications with developer-focused documentation, integration guidance and technical resources designed for your implementation journey.
Strong integrations start with clear technical documentation, secure implementation and careful testing. Explore the developer resources available for your approved Digiway services and build payment workflows that fit your business requirements.
The essential technical resources to understand, implement and manage your payment integration.
Explore the technical specifications for available API operations, including request methods, parameters, response structures and integration prerequisites.
Browse API Reference →key_••••••••Understand the authentication method, credential requirements and access permissions specified for your approved integration.
View Authentication Guide →{ "status": "ok"}Review verified request and response examples to understand how API operations are structured and how your application should process the results.
Explore Code Examples →Validate your implementation, review error responses and investigate integration issues before proceeding to production.
Explore Testing Guide →Follow a clear implementation path from initial API access to production readiness.
Contact the Digiway team to confirm service availability, complete the required onboarding process and obtain authorised API credentials for your integration.
Review the relevant endpoints, authentication requirements, mandatory parameters, response formats and transaction flow before implementation.
Build your integration and test supported scenarios using the authorised testing environment, where available. Check successful responses, error handling and transaction status verification.
Complete the required testing, security checks and approvals. Configure authorised production credentials and verify the integration before enabling live transactions.
Before Going Live: Confirm production access, supported transaction flows, error-handling behaviour and the applicable operational requirements before launch.
Navigate directly to the technical resources relevant to your business workflow.
Understand the supported payment initiation flow, transaction responses, status verification and related integration requirements.
Explore Payment APIs →Review the available collection workflows, payment references and transaction status handling for supported payment methods.
Explore Collection APIs →Explore the authorised payout workflows, applicable beneficiary information and available transfer status responses.
Explore Payout APIs →Find technical information for supported account-related workflows and the transaction references or reporting features available for reconciliation.
Explore Account APIs →Review integration resources for supported bill payment services, transaction submission and status enquiries, where API access is available.
Explore Bill Payment APIs →API access is available only for services enabled on your Digiway account.
Understand each operation through clear technical specifications and verified implementation examples.
/v1/paymentsEach API operation is documented with its endpoint, HTTP method, authentication requirements, mandatory fields, optional parameters and expected response.
Verified examples explain the request format, response fields, success conditions and relevant error scenarios, aligned with the actual API specification.
Supported SDKs, language-specific examples or standard HTTP integration instructions are published as available, with supported versions and prerequisites clearly identified.
Documentation organised by service and operation, with searchable endpoints, copy-code controls, field descriptions and clear error-code explanations.
Protect your integration with secure credential handling and the authentication methods defined in the official documentation.
Store API secrets securely, restrict access to authorised systems and never expose private credentials in browser-side code or public repositories.
Implement the authentication method specified by Digiway. Where supported, maintain separate credentials and configurations for testing and production.
If webhooks or callbacks are supported, verify their authenticity according to the documented method and design your application to handle duplicate events safely.
Validate your implementation in an authorised testing environment before processing live transactions. Verify your integration against the documented requirements and confirm that your application handles expected outcomes correctly.
Identify common integration problems and follow the documented steps to investigate them.
Verify the configured credentials, required authentication format and assigned permissions. Check that you are using the correct environment and that your credentials are valid.
Check in this orderReview the API specification and check mandatory fields, data types, accepted values and request formatting. Compare the request with the verified example for that operation.
Check in this orderUse the documented status enquiry process to verify the original transaction. A timeout does not necessarily mean failure; follow the applicable retry and idempotency rules before resubmitting a financial request.
Check in this orderWhere webhook support is available, review your endpoint configuration, server availability and response handling. Follow the documented retry or reconciliation process to investigate missed notifications.
Check in this orderNeed help with API access, integration errors or technical documentation? Share the relevant details with the Digiway team to identify the appropriate next steps.
Share relevant error details, but never include secret credentials or confidential customer data.Provide the information needed to help the technical team understand your issue.
Answers to common questions about API access, integration, testing and technical support.
Contact the Digiway team to confirm the required service, complete any applicable onboarding and request API credentials through the authorised process. Access depends on service availability and the relevant business and technical approvals.
Refer to the official API Reference for your enabled service. It identifies supported operations, endpoint URLs, request methods, required parameters and response formats. Always use the documentation matching your API version and environment.
Contact the Digiway technical team to confirm whether a sandbox is available for your service. Where provided, the documentation explains how to obtain test credentials, validate supported scenarios and prepare for production activation.
Refer to the current developer documentation for officially supported SDKs, code samples and integration methods. If an SDK is unavailable for your preferred language, ask the technical team about the supported HTTP API integration approach.
Review the HTTP status, API response code and error details documented for the relevant endpoint. Check the request parameters and authentication configuration, then follow the documented recovery process. When contacting support, provide the request reference and a redacted error response.
A timeout does not necessarily mean the transaction failed. Check the transaction status using the supported enquiry mechanism before retrying a financial operation. Follow the documented idempotency and retry rules to avoid duplicate processing.
Complete the applicable integration tests, security checks and approval requirements. Obtain production credentials through the authorised process, verify your production configuration and confirm that your application handles transaction responses correctly before enabling live transactions.
Use the designated Digiway support channel and provide the affected API operation, approximate time, request or transaction reference and a redacted error response. Never share secret API keys, passwords, OTPs or sensitive customer information in your support request.