Skip to main content
All systems operationalChangelogv1
Log in

Connections

On this page

Connect payment processors, anti-fraud providers, and alternative payment methods once, then use them across your payment strategy.

What is a connection#

A connection is the reusable link between your DEUNA merchant account and an external provider. It stores the provider configuration and makes its supported capabilities available to your payment experience and routing strategy.

01
Connect the provider
Add the credentials and options requested for that provider.
02
Activate capabilities
Choose the operations, payment methods, and security features your account supports.
03
Use it in a strategy
Route payments and risk checks through active connections.
04
Operate and monitor
Track status, disable a connection, or adjust supported settings in Admin.
Interactive exampleUses sample data and does not make API requests.
Production
Payments

Connections

Discover and manage payment, wallet, and anti-fraud integrations.

Acme LATAM · Production
5 sample connectionsUpdated just now
ConnectionsTypeStatusAction
AdyenPayment gatewayConnected
WorldpayPayment gatewayConnected
PayPalPayment methodConnected
Mercado PagoPayment methodNot connected
RiskifiedAnti-fraud engineNot connected

Configure connections#

Start with the live catalog, then follow the guide for the connection type you want to enable.

Provider capabilitiesCompare providers by country, currency, payment type, and supported operation.Payment gatewaysConnect card processors and configure purchase, authorization, capture, refund, and 3DS support.Payment methodsEnable wallets, bank transfers, vouchers, BNPL, and other local payment methods.Anti-fraud enginesConnect risk providers and place their decisions before or after authorization.Commerce pluginsUse a supported commerce-platform connector when you want a lower-code setup.Payment strategiesPut active connections into default, conditional, retry, and risk-routing rules.

Manage connections#

Configuration settings help adapt the integration to the specific needs of your payment strategy, ensuring the proper functioning of each connection in DEUNA.

Payment processor settingsManage the connection name, payment operation, enabled methods, and 3DS availability.Payment method settingsManage the connection name and understand which values become fixed after activation.Anti-fraud settingsMaintain the configuration used by your risk provider.

Payment processor settings

Once a payment processor has been successfully configured and activated, the following fields can be edited:

SettingsEditableDescription
Connection nameYesThe connection name can be changed at any time
CredentialsNoIt will not be possible to edit the configuration keys once the processor is activated.
OperationsYesYou can switch between Purchase and Authorization according to your transaction preferences.
Alternative payment methodsYesAt any time the merchant can activate or deactivate an alternative payment method through the payment processor configuration.
Security methodYesAt any time the merchant can enable 3DS as a security method. In Payment Strategies, you can define when 3DS authentication should be applied.

Payment method settings

Once an Alternative payment method has been successfully configured and activated, the following fields can be edited:

SettingsEditableDescription
Connection nameYesYou can change the connection name at any time
CredentialsNoYou cannot edit the configuration keys once the alternative payment method is activated.

Anti-fraud settings

Once an anti-fraud provider has been successfully configured and activated, the merchant can edit the configuration keys whenever desired.

Disable connections

Connections can be disabled so they stop operating in your payment strategy.

Alternate credentials for a retry

A card-processing connection can be linked to one alternate credential for a retry through the same payment processor. DEUNA considers the alternate only after the primary connection has made a dispatched attempt; the alternate is not eligible as a primary Dynamic Routing candidate.

The alternate must belong to the same merchant, store, payment processor, country, and compatible currency. DEUNA keeps the original rule attribution and installment selection, but uses the alternate connection's credentials and capabilities for the retry.

The alternate is not used when authorization data is bound to the original connection, including an existing 3DS result, consent flow, subsequent recurring payment, PSP token, incompatible installment plan, or incompatible capture and CVV requirements.

Error management#

View specific errors from the payment processors they have activated.

You can change the action associated with each error, customizing your payment strategy in detail.

FieldsDescription
ProcessorList of active payment processors linked to the merchant.
Error codeNumeric identifier associated with the error from the payment processor.
Processor error messageDetailed error description provided by the payment processor.
ActionableOptions available when receiving the "Retry" or "Decline" error after a transaction.

You can edit the actionable for errors.

If the default alternative is changed, then the original option is shown through an indicator.

Edit the actionable

Edit the actionable for payment processor errors, with the following options.

If a transaction fails with a specific error code provided by the processor:

  • Retry: The order will be directed to the subsequent processor defined in the payment strategy, offering the opportunity to make a new processing attempt.
  • Decline: The order will be declined and will not be routed to the next processor defined in the payment strategy.

Edit the actionable for an error code:

  1. In Error management,click on the Actionable list for the error you want to edit.
  2. Select the Retry/Decline option.
  3. Click Confirm .

Edit multiple error codes

To edit multiple error codes:

  1. Access Error management in the side menu
  2. Select the errors you want to edit by checking the box next to each error.
  3. In the editing bar, choose the option you want to edit from the dropdown menu, either Actionable or Final message.
  4. Click Save in the editing bar.
  5. Confirm your changes by clicking the Confirm button in the modal.