Welcome to the Payments section of our documentation! This section is designed to guide you through the seamless integration of our Payment Gateway with your e-commerce platforms, APIs, or custom solutions. Whether you're a seasoned developer or new to online payments, we provide comprehensive instructions and resources to facilitate a smooth integration process.
Environment Modes
Our platform provides two environment modes, Playground and Production, to help you seamlessly test and deploy your integration with our gateway.
Playground Mode
In Playground mode, all requests are processed in test mode, allowing you to safely experiment with our service, test new features, or simulate transactions without incurring any real charges. This mode is ideal during development and integration phases or when trying out recently added functionality.
Production Mode
Switching to Production mode enables live transactions. When set to Production, all requests are processed as real transactions, and the requested amount is charged and deposited into your wallet, as per your instructions. This mode should only be used once you're ready to go live and accept actual payments.
You can toggle between these environments in your Dashboard at any time, making it easy to test and deploy as needed.
Integration Options
Explore our range of integration options tailored for various e-commerce platforms and APIs. Choose the method that best suits your requirements, and follow our step-by-step instructions to integrate our Payment Gateway seamlessly into your website or application.
Notifications
Welcome to the Notifications section of our documentation! In this section, we outline the process by which merchants can stay informed about the status of their transactions and communicate effectively with their customers. As a merchant utilizing our services, it's essential to leverage the web-hooks and the endpoints provided to you for querying the transaction status.
Occasionally
If the response or error message we provide to you is not in the line of the status codes we have shared in this documentation then be sure to check the following in the response.
- You may get a response with
payloadkey ormessagekey - You may receive validation errors which you must handle correctly for good user experience on your platform.
Note:
Except for these other statuses and responses have being explained for you. If you have a way to improve this documentation due to a difficult you faced during intergration, Please go ahead and do so.
Transaction Status Updates
As part of our service, merchants are responsible for confirming the status of transactions with their customers. Which includes options for Email notifications. Promptly informing customers about transaction outcomes. Stay informed about successful payments, pending transactions, and any issues that may require attention.
Proactive Communication
Ensure proactive communication with customers by promptly addressing any transaction-related inquiries or concerns. Utilize the transaction status information provided by our system to provide accurate and timely updates to customers, fostering trust and loyalty. By staying proactive and transparent, you can enhance the overall customer experience and build strong relationships with your clientele.
Compliance and Best Practices
Adhere to regulatory requirements and industry best practices when communicating transaction status with customers. Maintain transparency, accuracy, and confidentiality in all communications to uphold the integrity of your business operations and comply with relevant regulations. By prioritizing compliance and best practices, you can build trust and credibility with your customers while mitigating risks associated with improper communication practices.