Payments Infrastructure architecture

Use this conceptual overview to understand the DEUNA execution layer before choosing an integration method. For implementation choices, start with Integrate with DEUNA.

Payments Infrastructure gives merchants one operating layer for 600+ payment connections. Integrate once, enable compatible providers and payment methods, control the customer experience and routing policy, and operate the payment lifecycle through one set of platform concepts.

Provider, country, method, and operation availability depends on the merchant account and each connection. Use the Provider capabilities catalog as the public source of truth and confirm production enablement with your DEUNA Technical Account Manager.

Expand

Infrastructure capabilitiesAsk Athia about this#

How a payment moves through the platformAsk Athia about this#

DEUNASequence diagramExpand

Build with explicit boundariesAsk Athia about this#

• Keep private API credentials on merchant-controlled backend services.
• Treat browser redirects and SDK callbacks as customer-experience signals; retrieve or receive the authoritative payment state.
• Use idempotency on supported side-effecting operations and reconcile an uncertain outcome before retrying.
• Configure only providers and capabilities confirmed for the target account, environment, country, and payment method.
• Preserve the original order and attempt identifiers across routing, retries, refunds, disputes, and reconciliation.
• Separate a successful request submission from a final provider or financial outcome.

Connect intelligence and agentsAsk Athia about this#

Payments Infrastructure can supply normalized transaction outcomes to Payments Intelligence. Supported Agentic Optimization decisions can then run within the payment flow without adding a separate decision hop, while static policy remains available as a fallback.

Prepare for productionAsk Athia about this#

1. Confirm merchant accounts, environments, credentials, providers, methods, and countries.
2. Select the integration experience and complete sandbox end-to-end tests.
3. Define routing, fraud, authentication, capture, timeout, and fallback behavior.
4. Validate asynchronous provider updates and operational reconciliation.
5. Test success, pending, decline, timeout, duplicate, redirect, and uncertain-outcome scenarios.
6. Confirm support ownership, observability, rate limits, and provider-specific go-live requirements.

ContinueAsk Athia about this#