Installments

DEUNA allows merchants to offer installments in a flexible and fully-orchestrated way across any integration method — Widgets, SDKs, or Direct API.
Our platform supports three different models for defining which installment options should be presented to the customer and ultimately processed with the payment provider:

1. Merchant-Provided Installments
2. DEUNA Installment Campaigns
3. Payment-Provider Installments

Depending on your business needs, you can enable one or combine multiple strategies to ensure customers always see the correct installment options based on card brand, BIN, issuer capabilities, currency, and routing rules.

1. Merchant-Provided Installments

Merchants can explicitly define the number of installments they want to offer to customers. This is the most direct and controlled model.

How it works

You provide the installment value directly to DEUNA:

• When processing a payment via API, include the installments parameter.
• When using DEUNA Widgets, provide the list of allowed installments during widget initialization.

DEUNA will:

• Present these installments to the user (if using a widget)
• Process the payment using the selected installment count
• Respect routing rules defined by the merchant

When to use this model

Use this approach when:

• You want full control over the installment list
• You manage eligibility logic internally
• You need different installment sets based on products, markets, or pricing tiers

2. Installment Campaigns (DEUNA Smart Rules)

Installment campaigns allow you to configure rules inside DEUNA that dynamically determine installment options based on:

• Transaction amount
• Currency
• Card brand
• BIN ranges
• Country
• Custom merchant conditions
• Routing strategies

How it works

1. Configure installment campaigns in the DEUNA console or via API.
2. DEUNA evaluates the rules in real time.
3. The widget or API response automatically returns the installment options to offer.

What DEUNA does

• Uses card metadata (BIN, brand, issuer country, etc.)
• Applies merchant-defined business logic
• Ensures consistent installment options across widgets, API, routing, and retries
• Allows merchants to change installment logic without modifying their backend

Use cases

• Offer 3 and 6 installments for Visa cards above USD 100
• Exclude corporate or prepaid cards
• Seasonal promotions requiring higher installment limits
• Installment configurations that differ by geographic region

This is the recommended model for dynamic, scalable installment orchestration.

3. Payment-Provider Installments

In this model, DEUNA retrieves installment options directly from the payment processor in real time.

This is typically used when the merchant does not have a commercial agreement defining which installments should be offered.
Instead, the merchant relies entirely on the provider’s rules.
DEUNA consults the configured payment provider during each transaction to obtain the installment plans available for that specific card and context.

How it works

• Merchant enables provider installments in DEUNA.
• During checkout, DEUNA calls the payment provider’s installment API or metadata service.
• The provider returns the list of eligible installment options.
• DEUNA normalizes and returns the options through the widget or API.

Fallback & Retry Considerations

If using fallback or retry logic:

• Ensure all fallback providers support the same installment options, or
• Disable fallback for installment transactions, or
• Limit installments to the intersection of supported values across all providers.

Example:
If Provider A supports 3/6/12 and Provider B supports 3/6, a transaction initialized with 12 installments cannot be retried at Provider B.

DEUNA can enforce rules that prevent incompatible installment selections.

Provider limitations

Provider rules may depend on:

• Local vs international cards
• Issuer-bank partnerships
• MCC category
• Supported currencies
• Card type (credit, debit, corporate)

DEUNA normalizes provider responses into a unified format.