Intelligent Payment Routing
Machine-learning selection of an eligible payment acquirer or network for individual transactions, according to configured conversion or processing-cost objectives.
Recorded characteristics
- Function
- Adyen Uplift Intelligent Payment Routing uses machine learning to select a payment-processing route for individual transactions. The feature operates within available routing choices and merchant configuration. Adyen handles the actual routing operation. Model-owned decision: selection of an eligible acquirer or payment network for a transaction, with conversion or processing-cost optimisation as the documented objective. The internal relationship between predictive models, eligibility filters and deterministic optimisation is not publicly established. Actions: the selected route is used by Adyen's payment infrastructure to process the transaction. The model does not independently authorise payments, move funds or control settlement. Outside actions: the consequential action occurs in external payment-processing infrastructure operated by Adyen; routing is executed outside the model itself. No independent model execution authority is claimed. Human confirmation: merchant activation is required. The documented routing workflow does not describe per-transaction human approval. This does not mean merchant configuration is unnecessary. Lifecycle: documented merchant-enableable commercial feature. No customer-specific activation or observed transaction outcome has been independently verified.
- Data access
- Adyen Uplift integrations use payment and checkout data, with general payment-request requirements and recommended contextual fields. The exact subset of these fields consumed by Intelligent Payment Routing's ML model is not publicly established.
- Actions
- Can take actions
- External actions
- Yes
- Human confirmation
- Not required
- Permission basis
- Not established
- Administrative control
- Adyen documents Customer Area permissions governing configuration of Uplift Optimize settings. These are merchant configuration permissions, not the model's runtime execution identity. The precise configuration-role names, runtime service identity and internal execution permissions are not established in the stored evidence.
- Default state
- Disabled
- Availability
- Available within supported Adyen Uplift configurations with at least two eligible payment routes. Availability and integration support vary by region and configuration. Universal availability is not asserted. Off by default; merchant activation occurs through Customer Area > Uplift > Optimize.
- Licensing
- Not established
- External model or provider
- Not established
- Limitations and uncertainty
- L01: At least two eligible routes are required. L02: Routing choices are constrained by configured schemes, MCCs and eligibility conditions; global route freedom is not established. L03: Feature availability and integration support vary by region and configuration. L04: The internal model architecture, training method, weights and feature inputs are not publicly established. L05: The division between ML prediction, deterministic optimisation and eligibility filtering is not publicly established. L06: Route-selection confidence scores and explanations are not publicly established. L07: Model timeout, inference failure and fallback routing behaviour are not publicly established. L08: Runtime service identity and internal execution permissions are not publicly established. L09: Per-transaction override or approval mechanisms are not publicly established. L10: Routing-specific licensing, fees and full geographic eligibility are not publicly established. L11: No customer-specific activation or observed routing outcome has been independently verified.
Evidence
- Enable Adyen Uplift
Supports: Limitations · Availability · Default state · Human confirmation · External actions · Actions · General · Function · Primary source
Supports L01, L02, L05, L07 and L09: multi-route prerequisite and eligibility constraints documented; ML/optimisation/eligibility division, fallback behaviour and per-transaction override mechanisms not publicly established.
Requires at least two eligible payment routes.
Off by default; merchant activation through Customer Area > Uplift > Optimize.
Merchant activation is required; the documented workflow does not describe per-transaction human approval.
Routing is executed by Adyen's payment-processing infrastructure, outside the model itself.
The selected route is used by Adyen's payment infrastructure to process the transaction.
Machine learning selects an eligible payment route for each transaction according to documented conversion or processing-cost objectives, with regional objective options qualified for the US and Australia.
Uplift Intelligent Payment Routing uses machine learning to select a payment-processing route for individual transactions within available routing choices and merchant configuration.
- Adyen Uplift requirements and recommendations
Supports: Limitations · Availability · Data access · Primary source
Integration and availability limitations; model-specific inputs not publicly established.
Uplift integration prerequisites: supported web integration types, Checkout API versions, webhook requirements and PCI qualification for raw-card-data integrations.
General Uplift payment-request requirements and recommended contextual fields; the model-specific input subset is not publicly established.
- Adyen Uplift
Supports: Limitations · Availability · Permission basis · General · Admin controls · Primary source
Product-level limitations; universal availability not asserted.
Availability is regional and integration-dependent.
Uplift merchant configuration is subject to Customer Area permissions; the model's runtime execution identity and internal permission basis are not publicly established.
Adyen Uplift product identity and lifecycle as a documented merchant-enableable feature.
Customer Area permissions govern merchant configuration of Uplift settings; specific role names are not established by the stored evidence.