Payments
Explore DEUNA payment products and features, then choose the guides for acceptance, orchestration, risk, lifecycle operations, installments, and recurring payments.
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.
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
- Default processing, specific rules, and conditional rules define the routing foundation.
- APM routing, currency validation, and routing by percentage cover specialized selection behavior.
- Configure 3DS and implement the 3DS purchase flow cover connection setup and customer action.
- Address Verification Service management and manual review cover additional supported decision points.
- Recommendation engine documents the public rule-management contract for eligible integrations.
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
- Multiple Partial Captures (MPC) splits an authorized amount across supported captures within the documented limits.
- Automatic void on authorizations releases eligible uncaptured authorizations after the configured period.
- Multiple Partial Refunds (MPR) applies more than one eligible refund against a captured payment.
- Asynchronous refunds require reconciliation after the initial refund request is accepted.
- Concurrent capture and refund explains supported operation ordering and safety boundaries.
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.