TermDefinition
SandboxA safe testing environment where users can try out OneKhusa features and processes without affecting the live (production) environment.
ProductionThe live environment where real users interact with OneKhusa and actual data is processed. It’s the version used for day-to-day operations, not for testing or development.
OrganisationRefers to the entity or business that holds the merchant account and uses OneKhusa to manage its financial or operational activities. eg Government Entity,Merchant,Payments Service Provider and Organisation
MerchantAn individual or organization that uses OneKhusa to receive payments, make disbursements, and manage financial transactions through the platform. eg payment s
ConnectorsA payment channel that a merchant uses in OneKhusa to send and receive money.
EFT (Electronic Funds Transfer)A method in the OneKhusa payment gateway that allows merchants to electronically send or receive money directly between bank accounts, without using cash or checks.
Collections (Accept payments)The inflow of funds into OneKhusa’s payment gateway, representing payments received from customers or other sources.
WebhooksA feature that allows a merchant to receive real-time notifications from OneKhusa about specific events, such as when a transaction is successful or fails.
Callback urlA URL provided by the merchant that specifies where OneKhusa should send notifications or responses, such as transaction updates or status confirmations.
Rate limitA configuration that controls how many requests the server can receive within a specified period of time, helping to prevent overloading or abuse of the system.
Batch disbursementA process in OneKhusa where money is transferred to multiple recipients at once. This can be done by uploading files in JSON, CSV, or XLS formats.
Single disbursementA process in OneKhusa where money is transferred to a single recipient.
Authorization LevelsA configuration feature in OneKhusa that determines how disbursements are approved:
• 2-Eye Principle: A single user can both create and authorize a disbursement.
• 4-Eye Principle: Two users are required at different levels; one creates the disbursement, and the other authorizes it.
• 6-Eye Principle: Three users are required at different levels; one creates the disbursement, another reviews it, and a third approves it before the disbursement can occur.