Skip to main content
HighRiskPaymentProvider.comPayment provider reviews
Xchange Payment Platform

Company overview

About Outpayce

What the company provides

  • Orchestrator
  • Gateway

Available countries, payment methods, data access, contracts and funds handling depend on the selected product.

Outpayce provides the travel-focused Xchange Payment Platform for payment orchestration, gateway connectivity, alternative payment methods, refund messaging, reporting and reconciliation.

XPP routes requests and data to customer-selected acquirers, gateways, payment service providers and other third parties. Those connected providers retain the merchant account, any MID, merchant underwriting, financial processing, funds custody and settlement. Outpayce S.A.U. is a Spanish electronic money institution, but that status does not authorize XPP as a direct acquirer or provider of a merchant account or MID.

outpayce.comUpdated Aug 15, 2026

Selected product

Xchange Payment Platform

Xchange Payment Platform technology

Connected payment-provider setup

  1. Connected payment account

    Not included with this product

  2. Connected-provider approval

    Outpayce reviews access to Xchange Payment Platform technology; each selected payment provider controls its own account activation

    Each connected payment provider sets its own account and activation requirements.

Primary legal entity

Outpayce, S.A.U.

Jurisdiction
Spain
Registration number
A85424893
Company type
Electronic money institution corporation

Legal entities by jurisdiction

One legal entity registered in SpainOne jurisdiction

The legal entity supplying a product can differ by product and country.

Product portfolio

Outpayce products

Compare payment-orchestration products by provider connections, routing, tokenization, channel coverage, production activation and the external merchant-services boundary.

Xchange Payment Platform

Role in this product

  • Payment orchestration provider
  • Payment gateway

A travel payment orchestration and gateway layer that lets the customer configure workflow and provider-selection rules, connect customer-selected payment providers, submit authorization, capture and refund messages, and consolidate transaction reporting.

The selected provider remains responsible for any merchant account, MID, underwriting, processing, reserves, funds movement and settlement.

Related services
Alternative payment methodsCurrency conversionPayment orchestrationPayment routing
Features
OrchestrationPayment operationsClient onboardingUnderwritingPricingReconciliationReportingCompliance

Selected product

Xchange Payment Platform

Related services
Alternative payment methodsCurrency conversionPayment orchestrationPayment routing
Features
OrchestrationPayment operationsClient onboardingUnderwritingPricingReconciliationReportingCompliance

Orchestration platform, provider connections & funds boundary

Who supplies the orchestration layer, which processors or acquirers connect to it, who activates live processing and who handles merchant funds.

01 · Role in this product
Payment orchestration provider · Payment gateway
02 · Orchestration platform
Not included with this product
03 · Production activation
Separate approval from the merchant's PSP or acquirer
04 · Connected-provider funds
Outpayce does not hold merchant funds or provide merchant settlement

Selected product: Xchange Payment Platform.

Payment orchestration

Xchange Payment Platform: routing, retries & provider failover

Review routing rules, retry behavior, provider failover, configuration ownership and the connected accounts required for live payments.

Selected product: Xchange Payment Platform technology

Included in Xchange Payment Platform

Features included with this product.

Solutions
Alternative payment methodsCurrency conversionPayment orchestrationPayment routing
Capabilities
OrchestrationPayment operationsClient onboardingUnderwritingPricingReconciliationReportingCompliance

Routing, retries & connected providers

Who controls routing and failover, and which connected PSPs or acquirers process and settle payments for Xchange Payment Platform.

Included

Payment gateway, PSP and acquirer connections

Integration options, connected PSPs and acquirers, tokenization, 3DS and merchant tools.

Gateway features

Integration → security → merchant tools

  1. 01Merchant integrationIntegration options and connected payment providers
  2. 02Payment securityTokenization, authentication and transport security
  3. 03Development & operations

Gateway connections

Merchant integration, PSP and acquirer connections

Integration options

No integration option is listed

Gateway

Payment technology

Connected payment provider

No connected acquirer or processor is listed

Security controls

Tokens and payment authentication

Operations

Webhooks, Control Panel and test environment

Tools used to test an integration and manage live payments.

API-oriented
Yes
Gateway included
Yes
Merchant chooses merchant services
Yes
Onboarding included
Yes
Role in this product
Payment orchestrator
Questions to confirm

Which connected PSP or acquirer provides the merchant account, processes transactions and sends settlement?

The connected provider depends on the merchant configuration.

Connected payment providers · Xchange Payment Platform technology

Which connected providers must approve this setup?

Outpayce reviews access to Xchange Payment Platform technology; each selected payment provider controls its own account activation.

Client company country

Eligible client countries are not specified

Company offices do not establish client eligibility or merchant-account eligibility.

Connected-provider approval

Outpayce reviews access to Xchange Payment Platform technology; each selected payment provider controls its own account activation

Each connected PSP, acquirer or processor sets its own account and activation requirements.

Provider connection
Selected processor, PSP or acquirer
Product
Xchange Payment Platform technology
01Product eligibility & acceptable use

Which businesses and provider connections can use this product?

Product eligibility and each connected provider's account requirements are separate decisions.

Eligibility requirements

01

Processing statements

Not specified

Confirm how many complete statement months are required

02

Eligibility information

Outpayce reviews the technology implementation; it does not underwrite the merchant account. Each customer-selected provider controls its own KYC, merchant approval, processing permissions, reserve terms and settlement.

03

Platform account decision

Outpayce client and implementation acceptance is separate from every connected provider's merchant-account, processing, acquiring, risk and settlement decision.

04

PSP and acquirer connection requirements

Outpayce may prepare or pass application material, payment data and communications, but the customer-selected provider can require its own KYC and contracts and controls approval for its payment service.

Approval, an agreement or credentials may be required for the PSP or acquirer selected for the payment setup; the exact requirements are not specified.

Restricted activity

Business restrictions

Product · MCC · jurisdiction · sales practice

Product, MCC, sales-practice and jurisdiction restrictions are not specified for this product.

02Product & provider setup

What is needed to activate the product and its provider connections?

Company information, commercial terms, integration details and the credentials or approvals required by each connected provider.

Product & provider setup

Open product account → connect providers → obtain provider approval → test → activate

The product and every required provider connection must be active before live use.

Platform account documents

Documents to prepare

  1. 01Business and integration information
  2. 02Customer selected provider details
  3. 03Sales channel and payment flow requirements
  4. 04Customer selected provider applications and credentials
  5. 05Provider requested KYC or regulatory documents

Platform account setup

  1. 01

    Agree the XPP solution scope, travel sales channels, integrations and commercial order forms with Outpayce.

  2. 02

    Identify each customer-selected acquirer, gateway, payment service provider, alternative payment method and risk provider required for the configuration.

  3. 03

    Complete the separate provider applications, KYC, contracts and credential exchange required by those providers.

  4. 04

    Configure business rules, payment workflows, reports and the relevant Amadeus or non-Amadeus front ends.

  5. 05

    Test the integration and move the approved configuration into the production environment.

Product & provider requirements

Account and provider-connection checks

Application and activation requirements.

Website requirements

Required website pages, disclosures and policies are not specified

Account review requirements

Company, ownership, sanctions, license and integration requirements are not specified

Account setup tasks

The onboarding tasks performed by the provider are not specified

Before applying

Provider setup requirements to confirm

Company eligibility, connected-provider requirements, credentials and activation timing are not fully specified.

Provider activation & restrictions

Required provider accounts, production credentials, prohibited activities and country restrictions.

  1. 01

    Which payment provider will make the final approval decision?

    Each selected payment provider controls its own account activation; the specific legal entity is set in the merchant agreement.

  2. 02

    What trading-history, credit, volume, ticket-size, guarantee and chargeback requirements apply to this account?

    These approval requirements are not specified.

  3. 03

    Which products, MCCs, sales practices and jurisdictions are prohibited for this product?

    Product-specific restrictions on products, MCCs, sales practices and jurisdictions are not specified.

Underwriting process & approval time

Decision criteria, manual review, when review starts or pauses, and decision timing.

  1. 04

    How long does final approval take after the complete merchant application is submitted?

    Final approval timing is not specified.

Payment methods & countries · Xchange Payment Platform technology

Which client countries, provider connections and payment methods are available for this orchestration setup?

Connected payment providers determine payment-method, country and currency coverage for this configuration.

Selected product

Xchange Payment Platform technology

Payment setup not specified

Selected product

Client company

Eligible client countries are not specified

Business availability and connected-service coverage are separate requirements.

Payment connection capabilities

Payment connection capabilities are not specified

Availability depends on

  • Connected provider
  • Business country
  • Payment method
  • Currency

Outpayce supplies payment technology. The merchant-account provider, merchant underwriter, processor, acquirer and configuration-specific payment coverage are not specified.

01Selected product

Xchange Payment Platform technology capabilities and connections

These capabilities belong to the selected product. Connected-provider and regional availability is set during configuration.

02Countries & availability

Where can the client use the platform, which connected providers cover each market, and where can customers pay?

Client eligibility, connected-provider coverage, customer country, payment method and currency are separate parts of the setup.

Country coverage

Client, connected-provider, customer and product countries

  1. 01

    Client location

    Where can the company using the orchestration platform be registered?

    Eligible client countries are not specified

    This is where the client company is registered; it does not determine connected-provider or customer-country coverage.

    Client and provider-account eligibility
  2. 02

    Connected provider coverage

    Which connected provider accounts cover each target market?

    The acquirer for each target country is not specified

    Across all products
  3. 03

    Customer location

    Where can customers pay from?

    Customer countries are not specified

    Customer countries by payment method and currency are not specified for this product.

    Across all products

Countries and payment methods

Countries and payment methods to confirm

  1. Which gateways, PSPs, processors and acquirers are available for each business country, payment method and currency?

    Payment methods, countries and currencies depend on the connected provider accounts and the merchant configuration.

  2. Which connected providers require a separate agreement, approval or production credentials?

    Commercial and account requirements differ by connected provider.

Pricing & funds · Xchange Payment Platform technology

What does Xchange Payment Platform technology cost, and which related charges are governed by another agreement?

Orchestration quote, billable events, minimum commitment and order-form terms

Pricing

Orchestration quote, billable events, minimum commitment and order-form terms

Pricing method

No public rate card; obtain the quote and order form

01Commercial terms

What makes up the quoted price?

Review the pricing plan, pricing model, fees and contract duration.

Quote & order form

No public rate card; obtain the quote and order form

02Billable events

Which billable events terms apply?

The payment, connection or workflow events that generate charges.

Billable events & unit prices

Not specified in the public pricing information

The quote or order form must identify each billable event, included allowance and overage rate.

03Settlement & payouts

Which provider settles merchant funds, and are payouts included?

The merchant settlement provider and terms are not specified unless listed below. Customer or third-party payouts are a separate service and may use another provider.

Merchant settlement & customer payouts

Sale proceeds and customer payouts

Settlement makes processed sale proceeds available to the merchant. A payout sends separate funds to a customer or third party.

01 · Minimum commitment

Minimum commitment

Any minimum monthly or annual spend required by the agreement.

Minimum commitment

Amount not specified

The applicable commitment is set in the order form.

02 · Order-form terms

Order-form terms

Initial term, renewal, cancellation notice, billing cycle and invoice currency.

Contract & invoicing

Initial term, renewal, billing cycle and invoice currency are not specified

Pricing & settlement terms

Terms to confirm in the agreement

Other terms

  1. What total price and included usage appear in the quote or order form?

    The public pricing information does not provide a usable total price.

  2. Which events or account units are billable, and what is the unit price for each?

    Billable events, included allowances and overage rates are not specified.

  3. What monthly or annual minimum commitment applies?

    The minimum commitment amount is not specified.

  4. What initial term, renewal rule, cancellation notice, billing cycle and invoice currency appear in the order form?

    The contract and invoicing terms are not specified.

Route decision flow · Xchange Payment Platform technology

How do routing, provider failover, decline recovery and decision logs work?

Routing rules, provider failover, decline recovery and decision logs

Route decision flow

Routing inputs → provider selection → outcome → retry & logs

The orchestration setup determines routing inputs, provider selection, retry rules, failover and route-decision visibility.

Selected product

Xchange Payment Platform technology

Routing rules, connected providers, decline recovery and operational logs.

  1. Routing inputs

    Customer configured business rules · Payment workflow ordering

  2. Routes & failover

    Decline-recovery behavior is not specified

    Not specified

  3. Payment routing responsibilities

    Outpayce applies routing and recovery rules · Connected PSP or processor authorizes each transaction

  4. Routing controls & logs

    Included

01

Routing inputs

Which fields and rules can drive payment routing?

Transaction fields, merchant rules and provider state used to select a route.

Routing capabilities

  • Customer configured business rules
  • Payment workflow ordering
  • Provider link determination
  • Historical traffic rule simulation
  • Fraud authentication and authorization sequencing
02

Routes & failover

How are providers selected, retried and failed over?

Provider selection, volume splits, conditional routes, retries and failover.

Selected setup

Routing entry point

How requests enter this product and which integration boundary applies.

Routing modes

  • Condition based provider selection
  • Workflow rule priorities
  • Fraud provider selection
  • Authorization and capture provider selection

Routes & failover

Routing, retry and failover controls

Routing
01

Decline recovery

Not specified

Decline-recovery behavior is not specified

Recurring payment recovery

Recurring payment recovery

Retries, provider failover and controls for recurring payment recovery.

Recovery support
Not specified

Not specified

03

Payment routing responsibilities

Who selects routes, authorizes transactions and handles merchant funds?

Outpayce selects and submits routes; connected payment providers authorize transactions and handle funds.

Payment routing responsibilities

  • Outpayce applies routing and recovery rules
  • Connected PSP or processor authorizes each transaction
  • Connected acquirer or PSP handles merchant funds

Available controls

Outpayce selects and submits routes; connected payment providers authorize transactions and handle funds.

  1. 01

    Connected provider types

    Which controls are available with this product?

    Connected provider types

    Not specified

    Connected provider types are not specified

04

Routing controls & logs

Which route decisions, provider-health signals and retry outcomes are available?

Rule management, route decisions, provider health, retries and operational logs.

Routing controls & logs

Routing inputs → route decision → provider outcome → retry & logs

Rule changes, route decisions, provider health, retries and operational logs.

  1. 01

    Routing controls & logs

    Rule management, route decisions, provider health, retries and operational logs.

    Control panel

    Included

    Route-decision logs and provider-health fields are not specified.

Before integration

Integration details not specified

  1. 01

    Which fields can drive routing, how are rule priorities resolved and when do changes take effect?

    Routing inputs, priority rules and deployment timing are not specified.

  2. 02

    Which declines can be retried through another provider, and how are duplicate authorizations prevented?

    Retry eligibility and duplicate-authorization controls are not specified.

  3. 03

    Which route decisions, provider-health signals, retries and outcomes are available in logs or webhooks?

    Routing observability and event fields are not specified.

Routing, failover & support

Xchange Payment Platform: risk, licenses & support

Connected providers, routing rules, retries, failover, change controls, contracting entity and support.

Xchange Payment PlatformService: Xchange Payment Platform technology
01 / Routing & service continuity

What happens when a payment provider fails?

Routing rules, retry limits, failover behavior, duplicate-payment protection, rule permissions and rollback.

Routing & failover

Outpayce routes transactions across connected payment providers

Payment routing and gateway connections do not make Outpayce the processor or funds holder. Authorization and settlement remain with the selected connected payment providers under their own agreements. The Xchange Payment Platform technology agreement controls routing rules, retries, failover and access to routing data.

Role in this product
Payment orchestration provider · Payment gateway
Connected providers & merchant funds
Outpayce does not hold merchant funds or provide merchant settlementMerchant settlement remains with the selected connected provider under its separate agreement; the provider and settlement terms depend on the merchant configuration.

Provider outages & routing continuity

How are failed routes retried, switched or rolled back?

Timeout handling, retry limits, failover, duplicate-payment protection and routing-rule change controls belong in the agreement.

  • What happens when a connected gateway, processor or acquirer is unavailable or returns an uncertain result?

  • Who can change routing rules, and how are rule changes tested, approved and rolled back?

Before signingRouting, retry, failover, duplicate-payment and rule-change terms2 items to confirmReview contract terms
02 / Contracting entity & connected providers

Which legal entity signs the software agreement, and which connected-provider agreements are required?

The software contracting entity and each connected payment provider's regulated services are separate. The connected-provider agreements identify who processes and settles each payment.

For this product

Software contracting entity and connected providers

Payment orchestration. The contracting legal entity for Xchange Payment Platform is not specified. Xchange Payment Platform is a technology product; payment processing, merchant-account services and settlement remain with the selected connected providers under their own agreements and authorizations.

A software company registration or PCI DSS certification does not identify which connected provider processes or settles a payment.

  1. 01 · Software contracting entity

    Not specified for this product

  2. 02 · Product role

    Payment orchestration

  3. 03 · Connected payment services

    Separate provider agreements and authorizations

Company legal entities, licenses & registrations

Company registrations and payment-services licenses do not identify the contracting entity for every product.

1 entity · 1 license or registration

Outpayce, S.A.U.

Spain · Registry A85424893 · Electronic money institution corporation

Electronic money institution

Banco de España · Registration 6727 · 1 permitted payment service · Active · Entity: Outpayce, S.A.U.

Security & regulatory information

Certifications, safeguarding arrangements and cross-border permissions for this product.

01

Security controls

Privacy and security controls

Security controls
Payment card data masking in reportsCustomer and connected provider PCI DSS obligationsControlled production environmentAccess control for merchant portal and data exchange
General
legal@outpayce.com
Before signingContracting entity, payment services license and legal terms1 item to confirmReview contract terms
03 / Support

How can merchants reach support?

Company support hours and contact channels are available. It is not specified which ones cover Xchange Payment Platform technology and routing errors, failed retries or connected-provider outages. First-response and resolution targets are also not specified.

Support contacts

Company support hours and contacts

The contacts that cover this product and routing errors, failed retries or connected-provider outages are not specified.

Company contacts

Support hours are not specified for these contacts.

Sales

outpayce.com/en/contact-us

General

legal@outpayce.com

Merchant support

sac@outpayce.com
Before signingSupport contacts, hours and response times3 items to confirmReview contract terms
Xchange Payment Platform technology / Before signing

What should the payment orchestration agreement include?

Confirm connected-provider agreements, pricing, routing rules, retries, failover, duplicate-payment protection, logs, support and termination.

Before signing

Xchange Payment Platform technology: terms to confirm

Confirm which providers can be connected, how routes and retries work, and who handles outages and uncertain payment results.

Providers, routing & pricing

Connected providers, usage allowances, route inputs and priorities, retry eligibility and premium features

Failover, control & observability

Provider outages, uncertain results, duplicate protection, rule permissions, rollback, logs and webhooks

Contract checklist

Terms to review by topic

Jump to the underlying product details

  1. 01Payment continuity & routing controlsProvider outages, uncertain results, duplicate-payment protection, permissions and rule rollback.
  2. 02Contracting entity & payment responsibilitiesPlatform contract, connected-provider agreements, data roles and any regulated payment service involved.
  3. 03Routing & provider supportContacts and response targets for routing errors, failed retries and provider outages.
Payment orchestration agreement

Routing and provider terms to confirm

Review pricing, connected-provider requirements, routing rules, retries, failover, duplicate-payment controls, logs, support and termination.

Payment continuity & routing controlsProvider outages, uncertain results, duplicate-payment protection, permissions and rule rollback.

  1. What happens when a connected gateway, processor or acquirer is unavailable or returns an uncertain result?

    Timeout handling, retry limits, failover behavior and duplicate-payment protection are not specified.

  2. Who can change routing rules, and how are rule changes tested, approved and rolled back?

    Routing-rule permissions, testing and rollback controls are not specified.

Contracting entity & payment responsibilitiesPlatform contract, connected-provider agreements, data roles and any regulated payment service involved.

  1. Which privacy framework, controller roles and data-transfer terms apply to this product?

    The privacy framework, controller roles and data-transfer terms are not specified for this product.

Routing & provider supportContacts and response targets for routing errors, failed retries and provider outages.

  1. What first-response, update and resolution targets apply by incident severity?

    First-response and resolution targets are not specified.

  2. Who handles routing errors, failed retries, provider outages and duplicate-payment risks?

    No escalation contact or process is specified for routing and connected-provider incidents.

  3. Which support hours and contact channels cover Xchange Payment Platform technology, and where should a business report routing errors, failed retries or connected-provider outages?

    The support scope for Xchange Payment Platform technology and the contacts for routing and connected-provider issues are not specified.

Product summary

What this product already includes

What the orchestration product includes, which provider restrictions apply and which routing terms are not specified.

Included capabilities

Capabilities included with Xchange Payment Platform technology.

  • Customer configured business rules, Payment workflow ordering, Provider link determination, Historical traffic rule simulation, Fraud authentication and authorization sequencing, Condition based provider selection, Workflow rule priorities, Fraud provider selection, and Authorization and capture provider selection

  • Payment orchestration technology

Provider and routing conditions

Connected-provider approvals, agreements, credentials, operating limits and market coverage.

  • Connected-provider requirements, operating limits, event coverage and service levels depend on the selected configuration.

Terms to confirm

Pricing, provider, routing, retry, failover, observability and termination terms to include in the agreement.

  • Unit prices, usage allowances, overage rates, contract length, minimum spend and renewal terms are not specified.