​

The All-in-One Payments Platform for SMEs

Omnispay helps small businesses manage their cash flow effectively by simplifying how they collect, pay, and borrow. With a robust payment infrastructure, Omnispay enables seamless transactions while ensuring security, scalability, and reliability. 🔗 Visit our website: Omnispay

​

Custom Response Codes

​

Transaction Limits

​

Standard HTTP Response Codes

​

Card Types

​

Supported Currency

The available currency codes on your account are determined by the merchant accounts you have with your acquiring bank. You can only process transactions in those currencies. Submitting a transaction request in a currency that is not available on your account will result in the request being rejected.

​

Available Currencies

​

🧾 Documenting Parent-Child Merchant Relationship Flow

This document explains how parent-level API keys work to authenticate merchants using apikey and accountId.

​

🔑 How Parent-Level API Keys Work

1. Parent-Level API Key Usage
   • A payment aggregator holds a parent API key that is used to process payments on behalf of multiple merchants (sub-merchants).
2. Why Passing accountId is Recommended
   • Helps track which merchant initiated the transaction (auditability).
   • Avoids mistakes where a request for one merchant goes to another.
   • Enables specific rate limits and security policies for each merchant.

---

​

❓ Which accountId Should Be Passed in the Header?

• If the parent (API key owner) is acting on behalf of a child merchant, send the child’s accountId in the request.
• If a merchant is calling on their own, use their own accountId.
• If accountId is missing:
  • Reject the request.

---