Skip to main content
HighRiskPaymentProvider.comPayment provider reviews
Cloud payment orchestration platform

Company overview

About Gr4vy

What the company provides

  • Orchestrator
  • Multi merchant payment orchestrator

Products, provider connections, payment-method availability and data handling depend on the selected configuration.

Gr4vy, Inc. supplies single-tenant cloud payment-orchestration software.

Its universal API, Embed and Secure Fields checkout components, Flow rules, card vault, PSP and network tokenization, 3-D Secure controls, external anti-fraud connections, reporting and settlement-report reconciliation sit between a merchant and the merchant's own payment providers. Gr4vy for Platforms adds a white-label, multi-merchant route with separate workflows, routing and provider connections for each underlying merchant. The merchant or platform keeps the direct account, contract, fees and credentials with each connected provider. Gr4vy does not supply the acquiring merchant account or MID, perform payment underwriting or direct acquiring, hold merchant funds, or settle funds to the merchant.

Founded 2021gr4vy.comUpdated Aug 15, 2026

Selected product

Cloud payment orchestration platform

Connected payment-provider setup

  1. Connected payment account

    Not included with this product

  2. Connected-provider approval

    Each selected payment provider controls its own account activation

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

Primary legal entity

Gr4vy, Inc.

Jurisdiction
United States
Company type
Corporation

Legal entities by jurisdiction

One legal entity registered in United StatesOne jurisdiction

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

Product portfolio

Gr4vy products

Compare payment orchestration and payment technology by account setup, approval, payment or data flow, and contract terms.

Cloud payment orchestration platform

Role in this product

  • Payment orchestration provider
  • Payment vault and token management
  • 3-D Secure orchestration
  • Card payout API and routing

A dedicated Gr4vy cloud instance provides the universal transactions API, Embed and Secure Fields checkout paths, Flow routing and retry rules, Vault, PSP and network token handling, 3-D Secure, external fraud-service connections, card OCT payout orchestration, reports and settlement-report reconciliation.

Connected PSPs, gateways, processors, acquirers, banks and payment-method providers retain their own contracts and financial roles, including payout programme approval and movement of payout funds.

Related services
Payment orchestrationPayment routingDecline recoveryDirect APIEmbedded checkoutEmbedded payment fieldsHosted checkoutPayment linksPayment vaultRecurring billingFraud preventionAlternative payment methodsPayout orchestrationCustomer payouts
Features
PSP and acquirer connectionsOrchestrationGatewayPayment operationsCheckoutFraud and riskReportingReconciliationPricingComplianceSupportPayouts

Gr4vy for Platforms

Role in this product

  • Multi merchant payment orchestrator
  • White label multi merchant payment orchestration

A white-label multi-merchant orchestration route for software platforms.

Each underlying merchant can have separate payment workflows, routing logic and connected PSP configuration behind the platform experience. Gr4vy supplies the orchestration technology; the platform and each merchant remain responsible for their commercial relationship and the connected PSP or acquirer retains merchant-account, underwriting, acquiring and funds roles.

Related services
Alternative payment methodsDirect APIPayment orchestrationPayment routing
Features
PSP and acquirer connectionsOrchestrationGatewayPayment operationsPricingComplianceSupport

Selected product

Cloud payment orchestration platform

Related services
14 capabilities
Features
12 capabilities

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 vault and token management · 3-D Secure orchestration · Card payout API and routing
02 · Orchestration platform
Not included with this product
03 · Production activation
Each selected payment provider controls its own account activation
04 · Connected-provider funds
Gr4vy does not hold merchant funds or provide merchant settlement

Selected product: Cloud payment orchestration platform.

Payment orchestration

Cloud payment orchestration platform: routing, retries & provider failover

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

Selected product: Cloud payment orchestration platform

Included in Cloud payment orchestration platform

Features included with this product.

Solutions
Payment orchestrationPayment routingDecline recoveryDirect APIEmbedded checkoutEmbedded payment fieldsHosted checkoutPayment linksPayment vaultRecurring billingFraud preventionAlternative payment methodsPayout orchestrationCustomer payouts
Capabilities
PSP and acquirer connectionsOrchestrationGatewayPayment operationsCheckoutPayment vaultRecurring billingFraud and riskReportingReconciliationPricingComplianceSupportPayouts

Routing, retries & connected providers

Who controls routing and failover, and which connected PSPs or acquirers process and settle payments for Cloud payment orchestration platform.

Included

Payment gateway, PSP and acquirer connections

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

Fraud & authentication connections

Screen → authenticate → return decision

  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

Integration options
  • REST API
  • Embed web SDK
  • Secure fields web SDK
  • iOS SDK
  • Android SDK
  • React native SDK
+3 more
  • Server side SDKs
  • Commerce platform plugins
  • Dashboard

Gateway

Payment technology

Connected payment provider

Types of connected payment providers
  • Acquirer
  • Bank
  • Digital wallet
  • Gateway
  • Open Banking
  • Payment processor
  • PSP
Acquirer-independent
Yes
Processor-independent
Yes
Works with multiple PSPs and acquirers
Yes
Single integration
Yes
Pre-integrated provider connections
Yes
Separate PSP or acquirer approval required
Yes
Provider integration maintenance
Yes
Connected providers
≥400 connections
Types of connected payment providers
  • Payment service providers
  • Payment processors
  • Payment gateways
  • Acquirers
  • Payment methods
  • Digital wallets
  • Anti fraud services
Capabilities
  • Universal transactions API
  • Pre built payment and fraud connections
  • Merchant owned provider account connection
  • Encrypted provider credential storage
  • Provider webhook handling and synchronization
  • Standardized transaction lifecycle
  • Dashboard connection activation
  • Provider switching without checkout reintegration
Product access
  • Gr4vy embed, Gr4vy secure fields, and Gr4vy transactions API: ≥400 connections · payment-method count not disclosed

Security controls

Tokens and payment authentication

Tokenization
Yes
3-D Secure
Yes
Token formats
  • Gr4vy vault token
  • Payment service provider token
  • Network token

Operations

Webhooks, Control Panel and test environment

Tools used to test an integration and manage live payments.

Webhooks
Yes
Sandbox
Yes
Merchant control panel
Yes
API-oriented
Yes
Gateway included
Yes
Merchant chooses merchant services
Yes
Merchant manages account standing
Yes
Merchant payouts
Yes
Seller of record
No
Tax responsibility
No
Gateway features
  • Transactions API
  • Payment options API
  • Checkout sessions
  • Payment links API
  • Connected provider credential encryption
  • Connected provider webhook synchronization
+3 more
  • Authorization capture cancel and refund requests
  • Standardized transaction object
  • Idempotent API requests
Role in this product
Payment orchestrator
Payment processing model
Gr4vy normalizes and routes the merchant's technical request. The selected connected payment provider performs the payment-processing and financial roles supported by that provider account.
Taxes handled
Questions to confirm

Which connectors apply to Cloud payment orchestration platform?

Connectors are not specified for Cloud payment orchestration platform.

Which webhook events apply to Cloud payment orchestration platform?

Webhook events are not specified for Cloud payment orchestration platform.

How are new PSP or acquirer connections added to Cloud payment orchestration platform?

The process and lead time for adding a new PSP or acquirer connection are not specified.

Which alternative payment methods apply to Cloud payment orchestration platform?

Alternative payment methods are not specified for Cloud payment orchestration platform.

What account setup, data retention, export, support and termination terms apply to this product?

These product-account and data terms are not fully specified.

Connected payment providers · Cloud payment orchestration platform

Which connected providers must approve this setup?

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

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
Cloud payment orchestration platform
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.

Restricted activity

Business restrictions

Product · MCC · jurisdiction · sales practice

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

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 connected processors, PSPs, acquirers and payment methods must be contracted and active for this configuration?

    Required provider agreements, active accounts and production credentials depend on the selected configuration.

  2. 02

    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.

Payment methods & countries · Cloud payment orchestration platform

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

Cloud payment orchestration platform

Gateway and payment-provider configuration

Selected product

Client company

Eligible client countries are not specified

Business availability and connected-service coverage are separate requirements.

Payment connection capabilities

  • Universal transactions API
  • Pre built payment and fraud connections
  • Merchant owned provider account connection
  • Encrypted provider credential storage
  • Provider webhook handling and synchronization
  • Standardized transaction lifecycle
  • Dashboard connection activation
  • Provider switching without checkout reintegration

Availability depends on

  • Connected provider
  • Business country
  • Payment method
  • Currency

Gr4vy connects to payment providers, and the merchant must obtain approval from the PSP or acquirer used for the setup. Configuration-specific payment methods, countries and currencies are not specified.

01Selected product

Cloud payment orchestration platform capabilities and connections

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

Product capabilities

Connected provider types

  • Payment service providers
  • Payment processors
  • Payment gateways
  • Acquirers
  • Payment methods
  • Digital wallets
  • Anti fraud services

Connected payment providers

Connected payment providers

≥400 connections

The number available to one merchant depends on the product, jurisdiction and agreement.

Types of connected payment providers

Payment service providers, Payment processors, Payment gateways, Acquirers, Payment methods, Digital wallets, and Anti fraud services

The specific connected providers, their commercial terms, approval responsibility and country coverage depend on the merchant configuration.

Connected payment provider
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?

    Set by the connected provider accounts

    Business-country, customer-country, currency and payment-method coverage depends on the selected processor, PSP, acquirer or payment-method connection. Gr4vy does not itself provide acquiring.

    Connected payment provider
  3. 03

    Customer location

    Where can customers pay from?

    Customer-country coverage is not specified for this configuration

    Customer-country coverage depends on the connected PSP or acquirer, payment method and currency. The exact country list is not specified for this product.

    Connected payment provider

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 · Cloud payment orchestration platform

What does Cloud payment orchestration platform 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 · Cloud payment orchestration platform

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

Cloud payment orchestration platform

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

  1. Routing inputs

    No code flow rules · Conditional checkout payment option presentation

  2. Routes & failover

    Next connection on technical failure · Next connection on supported retriable ISO code

  3. Payment routing responsibilities

    Gr4vy 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

  • No code flow rules
  • Conditional checkout payment option presentation
  • Pre routing transaction decline
  • Card connection routing
  • Sequential connection cascading
  • Same connection conditional retries
  • Technical failure cascading
  • Retriable ISO and soft decline cascading
  • Split routing with per rule percentage allocation
  • Pan or network token instrument selection
  • Merchant initiated transaction message transformation
  • Co badged card scheme routing
  • Dynamic 3-D Secure control
  • Anti fraud decision routing
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

  • Rules-based routing
  • Basic sequential routing
  • Split percentage routing
  • Processor and PSP connection routing
  • Payment method presentation routing
  • Pan or network token routing

Routes & failover

Routing, retry and failover controls

Routing
01

Decline recovery

  • Next connection on technical failure
  • Next connection on supported retriable ISO code
  • Next connection on supported soft decline
  • Same connection retry after account updater card replacement

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?

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

Payment routing responsibilities

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

Available controls

Gr4vy 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

    • Payment service providers
    • Payment processors
    • Payment gateways
    • Acquirers
    • Payment methods
    • Digital wallets
    • Anti fraud services
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

Cloud payment orchestration platform: risk, licenses & support

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

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

Gr4vy routes transactions across connected payment providers

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

Role in this product
Payment orchestration provider · Payment vault and token management · 3-D Secure orchestration · Card payout API and routing
Connected providers & merchant funds
Gr4vy does not hold merchant funds or provide merchant settlementThe funds holder and merchant settlement provider are not specified.

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?

Fraud rules, 3-D Secure & provider disputes

Controls in the orchestration layer and risks held by connected providers

Fraud screening and 3-D Secure are available. The orchestration platform controls workflow routing, fraud-provider calls and available 3-D Secure options. Refunds, chargebacks, negative balances and settlement holds remain subject to the applicable connected-provider agreements.

  1. 01

    Before authorization

    Fraud screening

  2. 02

    At checkout

    3-D Secure authentication

BEFORE AUTHORIZATION

Fraud screening

Which fraud rules can block or flag a transaction for review?

Capabilities
Third-party anti fraud connectionsPrimary silent or inactive connection modesFlow rules using provider score or decisionForce 3-D Secure from fraud resultDecline from fraud resultRoute to connection from fraud resultDynamic 3-D Secure
Cardholder checks
Flow force or skip 3-D SecureAnti fraud decision triggerIssuer mandate handlingMerchant account level 3-D Secure configuration
Screening · Delivery model
Connected anti fraud provider
Screening · Connection modes
PrimarySilentInactive
Screening · Supported providers
CybersourceForterRiskifiedSardineSift
Screening · Primary mode
One configured primary anti-fraud connection can return an enforced approval or decline.
Screening · Silent mode
The provider is called and its result is logged but not enforced.
Third-party fraud integration
CybersourceForterRiskifiedSardineSift

AT CHECKOUT

3-D Secure authentication

Which 3-D Secure and verification methods are included?

Authentication · Methods
Embed 3-D SecureHosted 3-D SecureNative 3-D SecureExternal 3-D Secure data
3-D Secure
Yes
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 Cloud payment orchestration platform is not specified. Cloud payment orchestration 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 · license or registration not specified

Gr4vy, Inc.

United States · Corporation

License or regulatory registration not specified

Security & regulatory information

These certifications, safeguarding arrangements and cross-border permissions apply to named company entities or to the company generally. Which ones apply to Cloud payment orchestration platform is not specified.

01

Security standards

Certifications and assessments

PCI DSS

Service provider level 1 · Entity: Gr4vy, Inc.

PCI DSS applies to Gr4vy, Inc.

SOC 2 Type II attestation

Entity: Gr4vy, Inc.

SOC 2 Type II attestation applies to Gr4vy, Inc.

02

Security controls

Privacy and security controls

Privacy frameworks
EU GDPRUK GDPRCcpaAustralian privacy law
Privacy contact
legal@gr4vy.com
Security controls
PCI DSS level 1 card vaultTokenizationProvider credential encryptionNetwork tokenizationAPI key role and merchant account scopeSingle tenant cloud instanceWebhook signature verification
Privacy
legal@gr4vy.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 Cloud payment orchestration platform 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.

Other company contacts

Support hours are not specified for these contacts.

Sales

gr4vy.com

Developer

docs.gr4vy.com/guides/get-starteddocs.gr4vy.com/guides/features/payouts/overview

General

gr4vy.com/frequently-asked-questions

Privacy

legal@gr4vy.com
Before signingSupport contacts, hours and response times3 items to confirmReview contract terms
Cloud payment orchestration platform / 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

Cloud payment orchestration platform: 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 legal entity will sign the agreement for this product?

    The contracting legal entity is 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. Which support hours and contact channels cover Cloud payment orchestration platform, and where should a business report routing errors, failed retries or connected-provider outages?

    The support scope for Cloud payment orchestration platform and the contacts for routing and connected-provider issues are not specified.

  3. Which support-request topics and routing options are available in the support form?

    Support-form topics and routing options 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 Cloud payment orchestration platform.

  • No code flow rules, Conditional checkout payment option presentation, Pre routing transaction decline, Card connection routing, Sequential connection cascading, Same connection conditional retries, Technical failure cascading, Retriable ISO and soft decline cascading, Split routing with per rule percentage allocation, Pan or network token instrument selection, Merchant initiated transaction message transformation, Co badged card scheme routing, Dynamic 3-D Secure control, Anti fraud decision routing, Rules-based routing, Basic sequential routing, Split percentage routing, Processor and PSP connection routing, Payment method presentation routing, Pan or network token routing, Next connection on technical failure, Next connection on supported retriable ISO code, Next connection on supported soft decline, and Same connection retry after account updater card replacement

  • 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.