Payment features
Choose and operate DEUNA payment capabilities across authentication, cards, installments, lifecycle operations, and routing.
On this page
Payment features extend the core payment lifecycle. Use this guide to choose the capability you need, understand where it acts, and open the code-grounded implementation guide without treating a globally documented feature as automatically enabled for every provider.
01 · qualify
Confirm eligibility
Check the provider, payment method, market, currency, channel, operation, and merchant configuration.
02 · configure
Enable the capability
Apply the approved connection, campaign, strategy, or account setting in DEUNA.
03 · integrate
Send the contract
Use the documented API or SDK fields and preserve the returned identifiers and next actions.
04 · verify
Test every outcome
Exercise success, decline, timeout, duplicate, asynchronous, and recovery paths.
05 · operate
Reconcile continuously
Use authoritative states and verified webhooks before fulfillment or follow-up operations.
Find a capability#
Authentication and risk
3D SecureChoose DEUNA- or provider-managed 3DS and handle frictionless and challenge flows.Issuer authenticationDynamic authenticationSelect authentication or verification from transaction, risk, customer, and issuer context.Policy-driven verificationAddress verificationUse standardized address-verification results in fraud and routing policy.Normalized AVS signalsManual reviewKeep fulfillment blocked while a third party resolves a pending risk decision.Held decisionsRecommendation engineManage ordered provider choices and supported weighted child rules.Prioritized provider rulesAddress normalizationNormalize supported billing and shipping fields before provider processing.Consistent address input
Card and credential handling
Card tokenizationReduce repeated credential entry while keeping PCI responsibilities explicit.Provider tokens and CVV verificationCard type detectionUse the detected card type consistently across routing and operations.BIN-derived routing contextConsent flowsTrack and reuse provider consent without treating it as payment confirmation.Supported wallet authorizationCurrency conversionCarry approved FX information through the payment lifecycle.Presentment and settlement context
Installments and amount lifecycle
InstallmentsConfigure campaigns, retrieve eligible terms, and send the exact selected option.Eligibility to selected planMultiple partial capturesCapture an approved authorization in supported increments.One authorization, staged fulfillmentMultiple partial refundsReturn collected funds in supported increments while respecting the remaining amount.Native or aggregated refundsAsynchronous operationsSeparate request acceptance from the provider's final operation result.Capture, refund, and voidConcurrent operationsUnderstand how supported overlapping capture or refund requests are validated.Serialized amount validationAutomatic voidConfigure the supported expiration behavior and reconcile the resulting void.Release uncaptured authorizations
Place the feature in the payment lifecycle#
Flow diagram
| Stage | Feature examples | What remains authoritative |
|---|---|---|
| Before processing | Address normalization, card detection, recommendation, anti-fraud | The backend order and configured connection eligibility |
| Authentication | 3DS, dynamic authentication, wallet consent | The returned next action and later payment state—not the browser return alone |
| Processing | Purchase, authorization, installments, conversion | The confirmed DEUNA payment amount, currency, and status |
| After authorization | Capture, partial capture, automatic void | Remaining authorized amount and provider-confirmed operation state |
| After collection | Refund, partial refund, asynchronous refund | Remaining refundable amount and provider-confirmed operation state |
Compatibility is multidimensional#
A feature is ready only when all required dimensions agree:
| Dimension | Verify |
|---|---|
| Provider and credentials | The connection and credential type support the operation |
| Market and currency | The configured country, currency, and settlement arrangement are eligible |
| Payment method | The selected card, wallet, bank transfer, voucher, or BNPL method exposes the capability |
| Channel and SDK | Web, iOS, Android, React Native, or Direct API supports the required customer action |
| Account configuration | The feature, strategy, campaign, limits, and time windows are enabled for the merchant |
| State handling | The integration supports every transient, success, failure, and recovery state it can receive |
Use Provider capabilities for published availability and Payment workflow and statuses for the complete state model.
Release checklist#
- Document the business outcome and the exact condition that enables the feature.
- Confirm public API or SDK fields against the linked guide; do not infer fields from Admin labels.
- Test the feature with its real provider, market, currency, and payment method combination.
- Include denied, pending, timeout, duplicate, partially completed, and unavailable cases.
- Make backend actions idempotent and keep private credentials out of client applications.
- Fulfill or reverse funds only from an authoritative DEUNA state.
- Monitor both customer-experience metrics and financial reconciliation after launch.