Routing Currency Validation
Validate the transaction currency against configured APM connections before Dynamic Routing selects an account.
On this page
Dynamic Routing can filter Alternative Payment Method (APM) connections by their configured currency before selecting an account. This avoids sending an APM payment to credentials configured for a different currency.
What this validation does#
- Compares the order currency with the currency configured for each candidate APM connection.
- Excludes an APM connection when its configured currency does not match the transaction currency.
- Leaves non-APM processor candidates unchanged; this filter is not a universal currency validator for every processor type.
- Prevents an authorization attempt through an APM connection that was removed by the filter.
The validation only runs when it is enabled for the merchant and store. It does not perform Dynamic Currency Conversion (DCC).
Currency validation
Preview which processors remain eligible for the transaction currency.
Why it matters#
Without this validation, an APM credential can be selected for a currency it was not configured to process. This can result in a provider rejection, reconciliation problems, or an incorrect account being used.
The filter removes the incompatible APM candidate before DEUNA invokes the provider.
High-level behavior#
When DEUNA receives a transaction:
- The order is created with a currency (for example, USD or MXN).
- Dynamic Routing builds the list of candidate connections from the active APM rules.
- For every APM candidate, DEUNA compares the transaction currency with the connection currency configured in Admin.
- A mismatched APM connection is removed from the candidate list.
- Routing continues with the remaining eligible connection. If no compatible APM connection remains, the payment cannot be sent through that routing selection.
Typical scenarios#
Scenario 1: Mismatch prevented
| Order | 100 USD |
|---|---|
| Configuration | A routing rule selects an APM connection configured for MXN only |
| Validation | DEUNA detects that USD does not match MXN |
| Result | The APM connection is skipped before provider invocation |
Scenario 2: Happy path
| Order | 500 MXN |
|---|---|
| Configuration | Routing rule points to an APM connection configured as MXN |
| Validation | DEUNA detects MXN = MXN |
| Result | Transaction is sent to authorization normally |
Scenario 3: Card processor candidate
| Order | 100 MXN |
|---|---|
| Configuration | Candidate is a non-APM card processor |
| Validation | The APM currency filter does not remove the candidate |
| Result | Normal routing and processor-specific currency validation continue independently |
Error handling#
If no compatible APM connection is available after filtering:
- DEUNA does not send the payment through a mismatched APM connection.
- The integration receives the routing or payment failure produced when no eligible configured connection can be selected.
Treat this as a routing or connection-configuration issue rather than automatically retrying the same credential.
Best practices for merchants and integrators#
To avoid unexpected declines due to currency mismatch:
- Configure the correct currency for each APM connection in DEUNA Admin.
- Review Dynamic Routing rules so each currency can reach an eligible APM credential.
- When adding a country, currency, or APM account, verify that the order currency matches the connection configuration.
If routing repeatedly has no eligible APM connection, review the rule and connection currency in Admin, then contact DEUNA with example transaction IDs.