Skip to main content
On this page

Start with your goal#

Understand the payment platform#

DEUNA provides one payment layer across 600+ payment connections, customer experiences, routing and risk controls, and post-payment operations. The capability you configure at each layer determines the next guide you need.

Payments + fraudRisk-aware decisions before processing.
01 · experience
Collect payment information
Use a DEUNA checkout experience or your own interface with the Direct API.
02 · decision
Authenticate and route
Apply supported authentication, fraud decisions, routing rules, and connection eligibility.
03 · processing
Run the payment
The selected connection processes the card or alternative payment method and returns its result.
04 · operations
Act on the final state
Confirm the status before fulfillment, then capture, void, refund, retry, report, or reconcile as required.

The payment status—not the browser redirect or a single provider response—is the lifecycle source of truth. Use webhooks and an explicit status lookup when a result can change asynchronously.

Accept and store payment methods#

Browse acceptance and credential features
  • Address normalization standardizes supported address input before it reaches payment and fraud connections.
  • Card type detection identifies supported card characteristics for the checkout experience.
  • Currency conversion explains the supported conversion experience and its payment implications.
  • Card tokenization covers stored credentials, customer association, and CVV behavior by connection.
  • Consent flows covers supported wallet authorization and reuse.

Orchestrate, authenticate, and protect#

Browse routing, authentication, and risk controls

Handle payment workflows and lifecycle operations#

Start with the shared payment workflow and status reference, then use the method-specific workflow and the operation you need.

Browse capture, void, and refund controls

Offer installments and recurring payments#

For a business-model view of repeat collections, continue to Recurring Commerce.

Apply a commerce pattern#

Order data, fulfillment timing, capture strategy, and refunds vary by business model. Choose the closest pattern before adapting the payment lifecycle.

Compare all commerce patterns when more than one model applies.

Build and operate#

Before production, confirm the selected provider capabilities, implement every reachable payment status, and validate the complete flow in the sandbox environment.