Our platform, connected to banking rails
Duoza operates its own platform on its own source code. The acceptance layer supports hosted checkout, iframe, Direct Pay API, payment links, invoices, and physical POS, with a live banking partner connected through the bank’s API.
The diagram shows the merchant acceptance operating flow. Product-specific architecture and data-flow guidance are included in your integration onboarding.
Participants and responsibilities
| Participant | Role |
|---|---|
| Customer | Initiates the purchase and completes any required cardholder authentication. |
| Merchant | Provides goods or services and owns the customer order. |
| Duoza | Runs the acceptance platform, integration experience, and merchant operational support. |
| Acquiring bank | Underwrites merchants, holds the acquiring licence and scheme membership, and settles directly to merchants. |
| Card network and issuer | Route the card transaction and handle the issuer’s authentication and authorization decisions. |
From acceptance to settlement
The customer enters the merchant’s selected payment experience. Duoza connects the payment to the acquiring bank, with the card network and issuer participating in authentication and authorization. 3-D Secure supports the online cardholder authentication journey.
The acquiring bank settles merchant funds directly. Duoza reporting, monitoring, and chargeback support help merchants manage the operational work around each payment.
Design for your chosen channel
Use the onboarding architecture package to map your application, the Duoza payment experience, and the acquiring boundary. Match data handling and security responsibilities to hosted, embedded, direct, or in-store acceptance.
The current platform connects to a live banking partner. Multi-bank routing is a roadmap capability that will extend the acquiring connectivity model.