Built for Developers

Your Code. Your Logic. Connected Payments.

Bring payment workflows into your applications with developer-focused documentation, integration guidance and technical resources designed for your implementation journey.

Developer-first integrationDocumentation structured around implementation.Structured payment workflowsUnderstand requests, responses and transaction flows.Security-conscious implementationBuild with secure credential handling in mind.
Digiway Developer Resources

Build Thoughtfully. Integrate Securely.

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.

Clear technical documentationOrganised around how you implement.
Security-conscious integration practicesBuilt with credential safety in mind.
Structured implementation guidanceFrom access to production readiness.
Implementation Path

From API Access to Production.

Follow a clear implementation path from initial API access to production readiness.

  1. Access

    Request API Access

    Contact the Digiway team to confirm service availability, complete the required onboarding process and obtain authorised API credentials for your integration.

  2. Understand

    Understand the API Structure

    Review the relevant endpoints, authentication requirements, mandatory parameters, response formats and transaction flow before implementation.

  3. Build

    Develop & Validate

    Build your integration and test supported scenarios using the authorised testing environment, where available. Check successful responses, error handling and transaction status verification.

  4. Launch

    Prepare for Production

    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.

API Reference

Clear Specifications. Verified Examples.

Understand each operation through clear technical specifications and verified implementation examples.

Digiway API ReferenceSandbox · Illustrative
POST/v1/payments

FieldTypeRequired
200 OK
Illustrative layout — actual endpoints depend on your enabled service.
Endpoints

Endpoint Documentation

Each API operation is documented with its endpoint, HTTP method, authentication requirements, mandatory fields, optional parameters and expected response.

Examples

Request & Response Examples

Verified examples explain the request format, response fields, success conditions and relevant error scenarios, aligned with the actual API specification.

SDKs

SDKs & Integration Samples

Supported SDKs, language-specific examples or standard HTTP integration instructions are published as available, with supported versions and prerequisites clearly identified.

Reference

Developer-Friendly Reference

Documentation organised by service and operation, with searchable endpoints, copy-code controls, field descriptions and clear error-code explanations.

Authentication & Security

Secure by Implementation.

Protect your integration with secure credential handling and the authentication methods defined in the official documentation.

Your server

Keep Credentials Private

Store API secrets securely, restrict access to authorised systems and never expose private credentials in browser-side code or public repositories.

Server → API

Follow the Approved Authentication Flow

Implement the authentication method specified by Digiway. Where supported, maintain separate credentials and configurations for testing and production.

API → Server

Validate Notifications & Callbacks

If webhooks or callbacks are supported, verify their authenticity according to the documented method and design your application to handle duplicate events safely.

Testing

A Structured Testing Approach.

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.

View Testing Documentation →
Troubleshooting

Troubleshoot Common Issues.

Identify common integration problems and follow the documented steps to investigate them.

Auth issue

Authentication Failed

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 order
CredentialsAuth formatPermissionsEnvironment
Still stuck? Submit a technical query →
Validation issue

Invalid Request Parameters

Review 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 order
Mandatory fieldsData typesAccepted valuesVerified example
Still stuck? Submit a technical query →
Status issue

Transaction Status Is Unclear

Use 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 order
Status enquiryNo blind retryIdempotency
Still stuck? Submit a technical query →
Webhook issue

Webhook or Callback Not Received

Where 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 order
Endpoint configServer availabilityResponse handlingReconciliation
Still stuck? Submit a technical query →
Technical Assistance

Let's Solve the Technical Challenge.

Need 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.
Developer Support Form

Submit a Technical Query

Provide the information needed to help the technical team understand your issue.

Other ways to reach us

Please enter your full name.
Please enter a valid email address.
Please enter your business name.
Please select a category.
Please describe the issue.

Never include secret API keys, passwords, OTPs or confidential customer data. By submitting, you agree that DIGIWAY PAYMENT may contact you about this query.

Developer FAQs

Your Questions, Answered.

Answers to common questions about API access, integration, testing and technical support.

How can I get API access from Digiway?

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.

Where can I find the API endpoints?

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.

Does Digiway provide a sandbox 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.

Which programming languages and SDKs are supported?

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.

How should I handle API errors?

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.

What should I do if an API request times out?

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.

How do I move my integration to production?

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.

How can I contact developer support?

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.