Enterprise FAQ

Yes. Veengu has a distributed, microservices architecture with stateless services that scale horizontally per component. Every production deployment runs at least two nodes in a cluster across availability zones, with load balancers distributing traffic and asynchronous, queue-based processing keeping the system stable under load.

PostgreSQL underpins the transactional core; a separate ClickHouse store handles analytical and reporting workloads so they never touch the operational hot path; an in-memory data grid provides cluster cache; and a message queue drives asynchronous processing. Files are stored in AWS S3, or MinIO for on-premise deployments.

The platform is designed to support tens of millions of accounts. In production, one of the largest deployments runs beyond 3M individual end users and 6M accounts; another active deployment supports around 500K individual users and 3,000 agents; and a large deployment includes more than 1,000 merchants.

It is multi-zone by design, with blue-green database deployments and auto-restart and heartbeat health checks, so most upgrades run with minimal to no downtime. Achieved availability for any deployment depends on the service plan and deployment design — see the high-availability page.

All traffic uses TLS/SSL. Sensitive data — payment tokens, cash-payout and remittance codes — is encrypted at rest, using keys held in a managed cloud key-management service (AWS KMS on AWS, the equivalent on Huawei Cloud, or operator-managed on-premise). Any additional field can be configured for encryption during implementation.

Role-based access control with granular per-tenant roles and separation of duties, multi-factor authentication for the back office, and step-up authentication for end-users. A maker-checker (four-eyes) principle is supported through the configurable workflow engine for KYC review, payout confirmation and internal approvals.

Yes — a Secure Development Lifecycle with design approvals, code review and automated plus manual testing, regular penetration testing, and vulnerability management with severity-based patching. Full detail is on the platform security page.

Veengu integrates with screening providers — such as LexisNexis Bridger, or a provider of your choice — for sanctions, PEP and negative-media checks, running at onboarding and on a configured re-screening cadence. You contract your chosen provider directly, keeping the commercial relationship and pricing in your hands, and Veengu wires it into the KYC workflow.

Veengu provides configurable KYC, AML-supporting workflows, audit trails, reporting tools, and integration capabilities. The licensed operator remains responsible for regulatory compliance decisions, monitoring policies, reporting obligations, and end-user outcomes.

Yes. KYC runs on a configurable workflow engine supporting multi-step routes, four-eyes review, and branching on residency, risk score or any captured attribute — with manual exceptions where needed. Every KYC action is recorded in an immutable audit trail queryable from the operator back office.

Veengu provides built-in controls out of the box — transaction, profile and min/max balance limits, automated task creation on AML-screening matches, and blacklist/whitelist through your screening provider. For dedicated fraud scoring, your preferred fraud and transaction-monitoring system connects directly into transaction execution through the Transaction Monitoring API, with real-time scoring during a transaction and post-transaction notifications.

Specialised, access-controlled APIs for end-user channels, partner and enterprise integration, transactional ecosystems, and external transaction-monitoring systems. OpenAPI specifications are published and a sandbox environment is part of the service, so each integration is provisioned with exactly the endpoints its licensed modules need.

Yes. Your team can build on the standard integration APIs, or Veengu can deliver the integration for you. USSD connects through the Frontend API and USSD-gateway partners such as Infobip; SMS through AWS SNS, a local gateway, or an SMPP interface; banks and partners through the incoming and outgoing transfer APIs; and AML through direct provider integrations. All of these have been delivered in production projects.

Third-party services — SMS, email, push notifications, maps, bot-protection, AML screening — run on your own provider accounts, billed directly by each provider at their own rates. You keep the direct relationship and the pricing, with no Veengu markup, and these sit alongside the Veengu fee rather than inside it.

Both, with the same platform, APIs and back office. SaaS is operated by Veengu on AWS or Huawei Cloud; on-premise deploys into your datacentre or private cloud. A common path is SaaS first, on-premise later, with a documented migration path. See the SaaS-or-on-premise page.

SaaS runs in the AWS or Huawei Cloud regions Veengu serves; on-premise runs wherever you choose to host it. The platform is cloud-agnostic — built on mainstream Linux, JVM and container infrastructure — so it can be deployed to, and migrated between, any compliant cloud or datacentre.

On SaaS (AWS or Huawei Cloud), database availability and backups — including point-in-time recovery for the last 7 days — are managed with cloud-native tools. The default data-retention period is 3 years and is configurable for on-premise, with database partitioning allowing old partitions to be archived or detached.

At least one production and one testing/staging environment. For larger projects with multiple integrations and data migrations, additional test, staging or SIT environments can be provided by agreement.

Enterprise support runs through a ticketing portal, chat, calls and email, with incidents categorised L1–L4 and a defined escalation matrix. Veengu has SLAs and uptime SLAs in place; the exact SLA depends on the selected service plan. See the support & SLA page.

Under a continuous-delivery model: minor updates several times per week, major updates typically weekly with backward compatibility, and breaking changes rare and announced well in advance. Updates ship through the Support & Maintenance plan with staged rollout and automatic rollback.

By scope, not per seat or per transaction — across implementation, custom development, a recurring SaaS or licence fee, and customization maintenance. Pricing depends on use case, integrations, deployment region and scale; first-year platform budget starts above a USD 70K floor. See the pricing page.

Each project includes a remote knowledge-transfer session sized to its complexity, plus continuous support through UAT, SIT and go-live. Additional training for existing or new staff is available on request.