Company overview
What the company provides
Products, provider connections, payment-method availability and data handling depend on the selected configuration.
Spreedly provides payment orchestration and a portable payment vault.
Merchants connect their own payment providers and credentials; Spreedly supplies the API, tokenization, routing, retries, 3-D Secure, fraud-service integrations and reporting. It does not provide the merchant account, acquiring or merchant settlement.
Selected product
Connected payment-provider setup
Connected payment account
Not included with this product
Connected-provider approval
Separate approval from the connected PSP or acquirer
Each connected payment provider sets its own account and activation requirements.
Primary legal entity
Legal entities by jurisdiction
The legal entity supplying a product can differ by product and country.
Product portfolio
Compare payment orchestration, payment vaulting, payment technology, and payment reporting and analysis by account setup, approval, payment or data flow, and contract terms.
Role in this product
One API for connecting gateways, processors, wallets and local payment methods.
Spreedly does not provide the merchant account or payment-provider credentials; separate commercial approval is required where the connected provider requires it.
Role in this product
A gateway-independent payment vault for tokenizing, storing, importing and exporting payment credentials.
The vault keeps payment data portable; it does not provide the merchant account or move merchant funds.
Role in this product
Payment routing, retries and failover across the merchant's connected providers.
Results depend on the providers, accounts and routing rules available to the merchant.
Role in this product
One integration for applying 3-D Secure and third-party fraud tools across payment providers.
The connected fraud vendor and merchant rules determine the checks used for each transaction.
Role in this product
Transaction, feature usage, billing and operational reports across the Spreedly account.
Settlement data still comes from the connected payment providers.
Selected product
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.
Selected product: Connect.
Review routing rules, retry behavior, provider failover, configuration ownership and the connected accounts required for live payments.
Included in Connect
Features included with this product.
Routing, retries & connected providers
Who controls routing and failover, and which connected PSPs or acquirers process and settle payments for Connect.
Included
Integration options, connected PSPs and acquirers, tokenization, 3DS and merchant tools.
Checkout & provider connections
Checkout → tokenization → connected payment provider
Gateway connections
Integration options
No integration option is listed
Gateway
Payment technology
Connected payment provider
Security controls
Operations
Tools used to test an integration and manage live payments.
How are new PSP or acquirer connections added to Connect?
The process and lead time for adding a new PSP or acquirer connection are not specified.
Which alternative payment methods apply to Connect?
Alternative payment methods are not specified for Connect.
Which connected PSP or acquirer provides the merchant account, processes transactions and sends settlement?
The connected provider depends on the merchant configuration.
Included
Compare hosted checkout, embedded UI, Web SDK and REST API with country and currency coverage.
Choose a checkout integration
The integration option determines who controls the checkout UI and the implementation effort.
Developer tools
Checkout controls
Which currencies are supported for Connect?
Currencies are not specified for Connect.
Which languages are supported for Connect?
Languages are not specified for Connect.
Which commerce plugins are available for Connect?
Commerce plugins are not specified for Connect.
Review which credentials can be stored, how tokens move between providers and what access, retention and export controls apply.
Included in Vault
Features included with this product.
Credential storage, token access & payment providers
Who stores payment credentials, who can use the tokens and which connected provider authorizes live payments for Vault.
Included
Spreedly tokenizes and stores payment credentials through Vault. Payment method import, export, retention, redaction and supported Advanced Vault features are part of this product.
Portable payment vault
Tokens stay separate from a single gateway account. Import, retention, reuse and export are distinct vault operations.
Payment methods accepted by the vault and how tokens can be reused
Storage states, retention controls and personal-data redaction
Move payment methods into the vault or to a supported destination
Review routing rules, retry behavior, provider failover, configuration ownership and the connected accounts required for live payments.
Included in Optimize
Features included with this product.
Routing, retries & connected providers
Who controls routing and failover, and which connected PSPs or acquirers process and settle payments for Optimize.
Included
Integration options, connected PSPs and acquirers, tokenization, 3DS and merchant tools.
Gateway features
Integration → security → merchant tools
Gateway connections
Integration options
No integration option is listed
Gateway
Payment technology
Connected payment provider
No connected acquirer or processor is listed
Security controls
Operations
Tools used to test an integration and manage live payments.
Which connected PSP or acquirer provides the merchant account, processes transactions and sends settlement?
The connected provider depends on the merchant configuration.
Included
Spreedly's payment orchestration covers routing, cascading and authentication. Connected payment providers make the financial decisions and control funds movement.
Routing decision engine
01 · Choose route
Routing rules, weights and who configures cascading
02 · Recover decline
Authentication and alternate-payment recovery
03 · Monitor & manage
Routing controls, currency conversion and reporting
Review the signals the product evaluates, the decisions it returns, rule ownership, review tools and the actions available to the payment system.
Included in Protect
Features included with this product.
Risk checks, rules & decision handling
Which risk checks Protect performs, who controls the rules and how its decisions are used.
Included
Spreedly connects fraud screening and payment authentication through Protect.
Fraud screening & decisions
01 · Score & decide
Monitoring, scoring, rules and authentication controls
Review available reports, data timing, reconciliation coverage, exports and dependencies on connected providers.
Included in Resolve
Features included with this product.
Transaction data, reports & reconciliation
Who supplies transaction data, report updates and reconciliation inputs for Resolve.
Included
Spreedly provides transaction reports and reconciliation data for Resolve through its reporting channels.
Operations data
Reports · Transaction, provider, feature-usage and billing reports
Reconciliation
Multiple-provider and multiple-source reconciliation coverage
Separate approval from the connected PSP or acquirer.
Client company country
Company offices do not establish client eligibility or merchant-account eligibility.
Connected-provider approval
Separate approval from the connected PSP or acquirer
Each connected PSP, acquirer or processor sets its own account and activation requirements.
Product eligibility and each connected provider's account requirements are separate decisions.
Restricted activity
Product · MCC · jurisdiction · sales practice
Product, MCC, sales-practice and jurisdiction restrictions are not specified for this product.
Before applying
Company eligibility, connected-provider requirements, credentials and activation timing are not fully specified.
Required provider accounts, production credentials, prohibited activities and country restrictions.
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.
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.
Spreedly reviews the client, tokenisation use case and configured token-service connections.
Product eligibility
Connected token services and payment providers retain authorization, processing and settlement responsibilities.
Product account review
Spreedly approves access to the configured vault and token-service scope
The provider reviews the company and product use before activating the technology account.
The product's acceptable-use rules determine which businesses and use cases can activate an account.
Restricted activity
Product · MCC · jurisdiction · sales practice
Product, MCC, sales-practice and jurisdiction restrictions are not specified for this product.
Company information, intended product use, commercial terms and integration details required before activation.
Product account application
Product access begins after account review, configuration and testing are complete.
Client, token & use-case inputs
Required company and account-setup documents are not specified
Account review, integration and activation steps are not specified
Product account requirements
Application and activation requirements.
Token-service & data-scope information
Required website pages, disclosures and policies are not specified
Security, token & provider-compatibility checks
Connected token services and payment providers retain authorization, processing and settlement responsibilities.
Approved tokenisation scope
The onboarding tasks performed by the provider are not specified
Before applying
Company eligibility, acceptable-use restrictions, account requirements and activation timing are not fully specified.
Who reviews the business and which products, jurisdictions or MCCs are excluded.
Which credential and token types, network and gateway token services and processors are supported?
Vault compatibility depends on the configured token and provider connections.
Which tokenisation policy, access controls, PCI scope, data residency and portability terms apply?
Security and portability terms are configuration-specific.
Which integration tests and production gates must pass before vault access is enabled?
Activation requirements depend on the selected token services and processors.
Separate approval from the connected PSP or acquirer.
Client company country
Company offices do not establish client eligibility or merchant-account eligibility.
Connected-provider approval
Separate approval from the connected PSP or acquirer
Each connected PSP, acquirer or processor sets its own account and activation requirements.
Product eligibility and each connected provider's account requirements are separate decisions.
Restricted activity
Product · MCC · jurisdiction · sales practice
Product, MCC, sales-practice and jurisdiction restrictions are not specified for this product.
Before applying
Company eligibility, connected-provider requirements, credentials and activation timing are not fully specified.
Required provider accounts, production credentials, prohibited activities and country restrictions.
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.
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.
Not included with this product.
Product eligibility
Financial account approval
Not included with this product
Financial account approval is outside this technology product.
Before applying
Company eligibility, acceptable-use restrictions, account requirements and activation timing are not fully specified.
Who reviews the business and which products, jurisdictions or MCCs are excluded.
What company information is required to open a Protect account, and how long does activation take?
Protect account setup requirements and timing are not specified.
Which business activities and product uses are prohibited by the acceptable-use policy?
Product-specific acceptable-use restrictions are not specified.
Not included with this product.
Product eligibility
Financial account approval
Not included with this product
Financial account approval is outside this technology product.
Before applying
Company eligibility, acceptable-use restrictions, account requirements and activation timing are not fully specified.
Who reviews the business and which products, jurisdictions or MCCs are excluded.
What company information is required to open a Resolve account, and how long does activation take?
Resolve account setup requirements and timing are not specified.
Which business activities and product uses are prohibited by the acceptable-use policy?
Product-specific acceptable-use restrictions are not specified.
Connected payment providers determine payment-method, country and currency coverage for this configuration.
Selected product
Connect
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
Availability depends on
Spreedly 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.
These capabilities belong to the selected product. Connected-provider and regional availability is set during configuration.
Connected provider types
Connected payment providers
≥150 gateway connections
The number available to one merchant depends on the product, jurisdiction and agreement.
Types of connected payment providers
Gateways, Payment processors, Wallets, and Fraud services
The specific connected providers, their commercial terms, approval responsibility and country coverage depend on the merchant configuration.
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
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.
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. Spreedly does not itself provide acquiring.
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.
Countries and payment methods
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.
Which connected providers require a separate agreement, approval or production credentials?
Commercial and account requirements differ by connected provider.
Payment vault reach means credential, token-service and processor compatibility for the configured client and use case.
Selected product
Vault
Configured token-service compatibility
Selected product
Client company
Defined by the selected product configuration
Business availability and connected-service coverage are separate requirements.
Vault compatibility
Availability is product- and contract-specific.
Availability depends on
Availability is product- and contract-specific.
These capabilities belong to the selected product. Connected-provider and regional availability is set during configuration.
Connected payment providers are not identified for this product.
Client eligibility, merchant-account approval, acquiring coverage and customer-country availability are separate parts of the payment setup.
Country coverage
Client, connected-provider, customer and product countries
Where can the company using the technology be registered?
Defined by the selected product configuration
This is where the business is registered; it does not determine acquiring-country or customer-country availability.
Where is merchant acquiring available?
Configured token, payment or data providers
Spreedly supplies vault technology; connected providers retain payment authorization, processing and settlement.
Where can customers pay from?
Configured token, payment or data providers
Configured token, payment or data providers define supported credentials, token services, processors and portability.
Countries and payment methods
Which credentials, token services, processors, countries and data-residency options are supported?
Vault coverage depends on the configured token and provider connections.
Which token import, export, portability and termination procedures apply?
Portability depends on token ownership and connected-service terms.
Connected payment providers determine payment-method, country and currency coverage for this configuration.
Selected product
Optimize
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
Spreedly supplies payment technology. The merchant-account provider, merchant underwriter, processor, acquirer and configuration-specific payment coverage are not specified.
These capabilities belong to the selected product. Connected-provider and regional availability is set during configuration.
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
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.
Which connected provider accounts cover each target market?
The acquirer for each target country is not specified
Where can customers pay from?
Customer countries are not specified
Customer countries by payment method and currency are not specified for this product.
Countries and payment methods
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.
Which connected providers require a separate agreement, approval or production credentials?
Commercial and account requirements differ by connected provider.
Supported transaction data, risk signals, decision controls, payment flows and countries define this fraud prevention product.
Selected product
Protect
Fraud prevention coverage
Selected product
Client company
Client-country availability for this fraud prevention product is not specified
Business availability and connected-service coverage are separate requirements.
Fraud prevention capabilities
Availability depends on
Protect scores transactions using the data supplied through the integration. Available signals, decision controls, payment flows and countries depend on the product configuration.
These capabilities belong to the selected product. Connected-provider and regional availability is set during configuration.
Authentication controls
Client eligibility, merchant-account approval, acquiring coverage and customer-country availability are separate parts of the payment setup.
Country coverage
Client, connected-provider, customer and product countries
Where can the company using the technology be registered?
Client-country availability for this fraud prevention product is not specified
This is where the business is registered; it does not determine acquiring-country or customer-country availability.
Where is merchant acquiring available?
Selected during configuration
The fraud and authentication services enabled for this account are not specified.
Where can customers pay from?
Set by the connected fraud and 3-D Secure services
Business countries, payment methods and regions supported by each connected service are not specified.
Countries and payment methods
Which transaction, device and customer data fields can be sent for risk scoring?
Required and optional risk signals are not specified for each integration.
Which decision outcomes, reason codes, review tools and regional restrictions apply?
Decision responses, manual-review options and country coverage are not fully specified.
Report coverage depends on the connected payment providers, accounts and available history.
Selected product
Resolve
Reporting connection coverage
Selected product
Client company
Business-country availability for this reporting product is not specified
Business availability and connected-service coverage are separate requirements.
Available reports
Availability depends on
Resolve consolidates data from connected payment providers. Available reports, currencies, time zones and historical coverage depend on those connections.
These capabilities belong to the selected product. Connected-provider and regional availability is set during configuration.
Connected data
Client eligibility, merchant-account approval, acquiring coverage and customer-country availability are separate parts of the payment setup.
Country coverage
Client, connected-provider, customer and product countries
Where can the company using the technology be registered?
Business-country availability for this reporting product is not specified
This is where the business is registered; it does not determine acquiring-country or customer-country availability.
Where is merchant acquiring available?
Multiple payment providers supported
The payment providers and accounts feeding this reporting product are selected during setup.
Where can customers pay from?
Set by the connected payment providers
Business countries, currencies, time zones and report history depend on the connected data sources.
Countries and payment methods
Which payment providers and accounts can feed the consolidated reports?
The connected data sources for this account are not specified.
Which currencies, time zones, report periods, export formats and historical dates are available?
Report coverage, timing and export details are not specified.
Checkout price, billable usage, contract term and additional costs
Pricing
Checkout price, billable usage, contract term and additional costs
Pricing method
Custom
Review the pricing plan, pricing model, fees and contract duration.
No public rate card
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
These fee amounts are not specified.
The usage units that determine the recurring bill.
Transaction volume, payment methods, provider connections and optional checkout components
The quantities, included allowances and overage rates are not specified.
Contract length, billing cycle, invoice currency, minimum spend and renewal terms. Implementation, optional-service, third-party and support charges outside the base price.
Invoice terms and costs outside the base price
Contract terms and additional charges
Contract, invoice and additional-cost terms define the software subscription and its bill.
01 · Contract & invoicing
Contract length, billing cycle, invoice currency, minimum spend and renewal terms.
Contract terms
Contract length, billing cycle, minimum spend and renewal terms are not specified
02 · Additional costs
Implementation, optional-service, third-party and support charges outside the base price.
Costs to include in the quote
Connected PSP or gateway charges, tokenization, mobile SDK and support costs
Pricing & contract terms
What amounts apply to the monthly fee, setup fee, application fee, annual fee, gateway fee, PCI fee, daily batch fee, early-termination fee, and monthly minimum?
These fees have no stated amount or waiver.
What initial term, renewal rule, cancellation notice, billing cycle and invoice currency apply?
The contract and invoicing terms are not specified.
How is checkout priced, which usage units are included and what are the overage rates?
Unit prices, included allowances and overage rates are not specified.
How will checkout volume, connected providers, environments and support level change the monthly bill?
The billable units and pricing tiers needed for a cost forecast are not specified.
Which connected PSP or gateway charges, tokenization, mobile SDK and support costs are billed separately?
Additional product and third-party charges are not specified.
Vault price, token-service costs & external funds boundary
Pricing
Vault price, token-service costs & external funds boundary
Pricing method
Quote or contract specific; amounts not publicly disclosed
Vault, tokenisation, network or gateway token service, implementation, support and data-portability charges.
Review the pricing plan, pricing model, fees and contract duration.
Quote or contract specific; amounts not publicly disclosed
Vault, tokenisation, network or gateway token service, implementation, support and data-portability charges.
Which party stores, creates, updates, exchanges and controls each credential or token.
Spreedly supplies the vault; configured token or payment services come from Configured token, payment or data providers
Token ownership, portability, data residency and provider compatibility are contract-specific.
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
Sale proceeds and settlement responsibility
Settlement makes processed sale proceeds available to the merchant.
Payment responsibility
Authorization, processing and settlement remain with Configured token, payment or data providers
Spreedly does not handle funds through the standalone vault role.
Pricing & settlement terms
Which vault, tokenisation, token-service, implementation, support and portability charges apply?
Vault pricing and billable units are not fully public.
Which network, gateway, updater or other third-party token-service costs are passed through?
Third-party costs depend on the configured token services.
What token export, portability, deletion, retention and post-termination charges apply?
Token and data exit terms are contract-specific.
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
Review the pricing plan, pricing model, fees and contract duration.
No public rate card; obtain the quote and order form
The payment, connection or workflow events that generate charges.
Not specified in the public pricing information
The quote or order form must identify each billable event, included allowance and overage rate.
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
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
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
What total price and included usage appear in the quote or order form?
The public pricing information does not provide a usable total price.
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.
What monthly or annual minimum commitment applies?
The minimum commitment amount is not specified.
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.
Fraud prevention price, billable usage, contract term and additional costs
Pricing
Fraud prevention price, billable usage, contract term and additional costs
Pricing method
Custom
Review the pricing plan, pricing model, fees and contract duration.
No public rate card
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
These fee amounts are not specified.
The usage units that determine the recurring bill.
Screened payment attempts, enabled rules and models, review volume and API usage
The quantities, included allowances and overage rates are not specified.
Contract length, billing cycle, invoice currency, minimum spend and renewal terms. Implementation, optional-service, third-party and support charges outside the base price.
Invoice terms and costs outside the base price
Contract terms and additional charges
Contract, invoice and additional-cost terms define the software subscription and its bill.
01 · Contract & invoicing
Contract length, billing cycle, invoice currency, minimum spend and renewal terms.
Contract terms
Contract length, billing cycle, minimum spend and renewal terms are not specified
02 · Additional costs
Implementation, optional-service, third-party and support charges outside the base price.
Costs to include in the quote
Third-party data checks, custom rules or models, implementation and premium support costs
Pricing & contract terms
What amounts apply to the monthly fee, setup fee, application fee, annual fee, gateway fee, PCI fee, daily batch fee, early-termination fee, and monthly minimum?
These fees have no stated amount or waiver.
What initial term, renewal rule, cancellation notice, billing cycle and invoice currency apply?
The contract and invoicing terms are not specified.
How is fraud prevention priced, which usage units are included and what are the overage rates?
Unit prices, included allowances and overage rates are not specified.
How will screening volume, enabled risk controls, review workload and support level change the monthly bill?
The billable units and pricing tiers needed for a cost forecast are not specified.
Which third-party data checks, custom rules or models, implementation and premium support costs are billed separately?
Additional product and third-party charges are not specified.
Reporting price, billable usage, contract term and additional costs
Pricing
Reporting price, billable usage, contract term and additional costs
Pricing method
Custom
Review the pricing plan, pricing model, fees and contract duration.
No public rate card
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
Amount not specified
These fee amounts are not specified.
The usage units that determine the recurring bill.
Connected accounts, report volume, retained history and export frequency
The quantities, included allowances and overage rates are not specified.
Contract length, billing cycle, invoice currency, minimum spend and renewal terms. Implementation, optional-service, third-party and support charges outside the base price.
Invoice terms and costs outside the base price
Contract terms and additional charges
Contract, invoice and additional-cost terms define the software subscription and its bill.
01 · Contract & invoicing
Contract length, billing cycle, invoice currency, minimum spend and renewal terms.
Contract terms
Contract length, billing cycle, minimum spend and renewal terms are not specified
02 · Additional costs
Implementation, optional-service, third-party and support charges outside the base price.
Costs to include in the quote
Additional data sources, extended history, custom exports and support costs
Pricing & contract terms
What amounts apply to the monthly fee, setup fee, application fee, annual fee, gateway fee, PCI fee, daily batch fee, early-termination fee, and monthly minimum?
These fees have no stated amount or waiver.
What initial term, renewal rule, cancellation notice, billing cycle and invoice currency apply?
The contract and invoicing terms are not specified.
How is reporting priced, which usage units are included and what are the overage rates?
Unit prices, included allowances and overage rates are not specified.
How will connected accounts, retained history, exports and support level change the monthly bill?
The billable units and pricing tiers needed for a cost forecast are not specified.
Which additional data sources, extended history, custom exports and support costs are billed separately?
Additional product and third-party charges are not specified.
Checkout flow · Connect
Checkout surfaces, tokenization, connected providers, SDKs and events
Checkout flow
The checkout integration determines who controls the payment form, how payment details are tokenized, which providers receive the payment request, and which SDKs and webhooks are available.
Selected product
Connect
Checkout integrations, tokenization, provider connections, SDKs and webhooks.
Checkout surfaces
Headless checkout · Drop-in checkout
Merchant-services connections
Payment processor · Connected payment processor · Acquirer · Connected acquirer
Checkout responsibilities
Gateway · Connected gateway · Payment processor · Connected payment processor
SDKs & implementation
iOS · Android
Checkout surfaces
Merchant-controlled and embedded checkout options for collecting payment details.
Merchant-services connections
The merchant-account, underwriting, acquiring, processing and settlement parties used with this checkout product.
Selected setup
How requests enter this product and which integration boundary applies.
Merchant-services connections
No additional merchant-services connections details are specified.
Tokenization & reuse
Token creation and reuse for future or recurring payments.
Not specified
Checkout responsibilities
Connect supplies the checkout and gateway. Merchant-account approval, processing and settlement remain with the parties assigned below.
Checkout responsibilities
SDKs & implementation
Client SDKs, environments, event handling and operational diagnostics.
SDKs & implementation
Checkout integration → tokenization → payment submission → webhooks & error reporting
Client SDKs, environments, webhook events, request logs and operational diagnostics.
Client SDKs, environments, event handling and operational diagnostics.
Webhook availability and events are not specified
Before integration
Which checkout surface is included, who receives card data and which PCI DSS validation applies to the merchant?
The contracted checkout surface and merchant PCI DSS scope are not specified.
Which legal entities act as payment processor and acquirer for Connect, and what approval, agreements and production credentials do they require?
The product assigns these roles outside the gateway, but does not name every legal entity.
Which payment, error and provider events are available through webhooks and request logs?
Checkout event and diagnostics coverage is not specified.
Payment lifecycle · Vault
Vault integration, token lifecycle & provider compatibility
Payment lifecycle
The selected product determines the integration, transaction controls, payment processing, merchant settlement and reporting.
Selected product
Vault
Integration, processing, merchant settlement and reporting for this product.
Vault integration
Spreedly vault API and token operations
Token & payment-provider connections
Configured token, payment or data providers
Vault & external-payment responsibilities
Spreedly: vault technology · Configured token, payment or data providers: token services, payment processing & settlement
Vault audit & portability records
Spreedly vault and token audit records
Vault integration
Credential, token, customer-reference and payment-provider interfaces for the configured vault use case.
Spreedly vault API and token operations
Credential, token, customer-reference and payment-provider interfaces for the configured vault use case.
Token & payment-provider connections
Configured network token, gateway token, updater and processor compatibility.
Selected setup
How requests enter this product and which integration boundary applies.
Token & payment-provider connections details are not specified.
Token & payment-provider connections
Configured network token, gateway token, updater and processor compatibility.
Configured token, payment or data providers
Credential & token lifecycle
Stored-credential consent, payment scheduling and retry rules apply to each recurring-payment setup.
Other recurring-payment terms
Credential intake · token creation or exchange · update · use · revocation or export
Create, store, exchange, update, retrieve, revoke, export and delete operations where contracted.
Vault & external-payment responsibilities
The provider supplies vault technology; connected payment providers retain authorization, processing and settlement.
Vault & external-payment responsibilities
Spreedly: vault technology · Configured token, payment or data providers: token services, payment processing & settlement
The standalone vault role does not take responsibility for the connected provider's payment or funds flow.
Vault audit & portability records
Token events, access logs, provider mappings, portability, retention and deletion evidence.
Additional operational terms
Additional reporting and operations terms for this product.
Spreedly vault and token audit records
Token events, access logs, provider mappings, portability, retention and deletion evidence.
Before integration
Which credential and token operations, environments, access controls, webhooks and certification tests are enabled?
Vault operations depend on the configured token services and providers.
How are token creation, exchange, update, revocation, portability, retention and deletion handled?
Token lifecycle and ownership are contract-specific.
What happens to tokens, mappings, logs and provider connections during an incident or after termination?
Vault continuity and exit procedures must be explicit.
Route decision flow · Optimize
Routing rules, provider failover, decline recovery and decision logs
Route decision flow
The orchestration setup determines routing inputs, provider selection, retry rules, failover and route-decision visibility.
Selected product
Optimize
Routing rules, connected providers, decline recovery and operational logs.
Routing inputs
Payment routing · Retries
Routes & failover
Retry through another gateway · Provider failover
Payment routing responsibilities
Spreedly applies routing and recovery rules · Connected PSP or processor authorizes each transaction
Routing controls & logs
Included
Routing inputs
Transaction fields, merchant rules and provider state used to select a route.
Routes & failover
Provider selection, volume splits, conditional routes, retries and failover.
Selected setup
How requests enter this product and which integration boundary applies.
Routes & failover
Recurring payment recovery
Retries, provider failover and controls for recurring payment recovery.
Included
Payment routing responsibilities
Spreedly selects and submits routes; connected payment providers authorize transactions and handle funds.
Payment routing responsibilities
Available controls
Spreedly selects and submits routes; connected payment providers authorize transactions and handle funds.
Which controls are available with this product?
Connected provider types
Routing controls & logs
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.
Rule management, route decisions, provider health, retries and operational logs.
Included
Route-decision logs and provider-health fields are not specified.
Before integration
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.
Which declines can be retried through another provider, and how are duplicate authorizations prevented?
Retry eligibility and duplicate-authorization controls are not specified.
Which route decisions, provider-health signals, retries and outcomes are available in logs or webhooks?
Routing observability and event fields are not specified.
Risk decision flow · Protect
Fraud screening, 3-D Secure, service fallback and decision data
Risk decision flow
The risk setup determines where screening runs, which providers receive data, how failures are handled and which outcomes return to the payment flow.
Selected product
Protect
Fraud screening, connected risk services, decision data and review tools.
Screening point
Fraud-provider integrations · Pre-authorization fraud checks
Connected fraud services
Enabled fraud providers, timeout rules and fallback behavior are not specified
Risk decision boundary
Spreedly provides fraud screening and authentication · The service returns fraud and authentication outcomes
Decisions & logs
Decision fields, reason codes, exports and retention are not specified
Screening point
Where fraud screening and authentication run in the authorization flow.
Connected fraud services
Fraud-provider connections, request fields, timeouts and fallback behavior.
Selected setup
How requests enter this product and which integration boundary applies.
Enabled fraud providers, timeout rules and fallback behavior are not specified
Connected fraud services
No additional connected fraud services details are specified.
3-D Secure & authentication
Authentication controls, versions, exemptions and challenge handling.
Risk decision boundary
Spreedly provides fraud screening and authentication; the merchant and payment providers retain payment and account responsibilities.
Risk decision boundary
Decisions & logs
Risk results, reason codes, authentication outcomes, exports and retention.
Decisions & logs
Screening request → provider result → merchant action → decision log
Risk results, reason codes, review outcomes, exports and retention.
Risk results, reason codes, authentication outcomes, exports and retention.
Decision fields, reason codes, exports and retention are not specified
Before integration
Which fraud and 3-D Secure services are enabled, and which payment methods and regions does each support?
The enabled providers and their coverage are not specified.
What happens when a fraud or 3-D Secure service times out, fails or returns an unavailable result?
Timeout, fallback and fail-open or fail-closed behavior is not specified.
Which decision fields, reason codes and authentication outcomes are returned and retained?
Decision output and retention are not specified.
Reporting data flow · Resolve
Connected data sources, report coverage, refresh timing and reconciliation
Reporting data flow
The reporting setup determines connected data sources, report coverage, update timing, exports and reconciliation keys.
Selected product
Resolve
Connected payment data, report coverage, refresh timing, exports and reconciliation.
Data sources
Multiple data sources · Multiple payment providers
Report coverage
Transactions · Provider performance
Reporting responsibilities
Spreedly consolidates payment-provider data · Connected providers supply transaction and settlement data
Exports & reconciliation
Export formats, join keys and correction handling are not specified
Data sources
Payment providers, accounts and data sets connected to the reporting product.
Report coverage
Transactions, provider performance, feature usage and billing data.
Selected setup
How requests enter this product and which integration boundary applies.
Report coverage
No additional report coverage details are specified.
Refresh & history
Data latency, available history, time zones and backfill behavior.
Reporting responsibilities
Spreedly consolidates connected-provider data; each provider remains responsible for its transaction and settlement data.
Reporting responsibilities
Exports & reconciliation
Export formats, identifiers, reconciliation workflows and correction handling.
Exports & reconciliation
Provider data → refresh → report → export & reconciliation
Export formats, identifiers, correction handling and reconciliation workflows.
Export formats, identifiers, reconciliation workflows and correction handling.
Export formats, join keys and correction handling are not specified
Before integration
Which providers, merchant accounts and environments can be connected to the reports?
The connected data-source matrix is not specified.
How much history is available, how quickly does each report update and which time zone does it use?
History, refresh timing and time-zone rules are not specified.
Which export formats and identifiers join provider transactions to orders, fees, refunds and disputes?
Export formats and reconciliation keys are not specified.
Connected providers, routing rules, retries, failover, change controls, contracting entity and support.
Routing rules, retry limits, failover behavior, duplicate-payment protection, rule permissions and rollback.
Payment routing and gateway connections do not make Spreedly the processor or funds holder. Authorization and settlement remain with the selected connected payment providers under their own agreements. The Connect agreement controls routing rules, retries, failover and access to routing data.
Provider outages & routing continuity
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?
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 Connect is not specified. Connect 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.
01 · Software contracting entity
Not specified for this product
02 · Product role
Payment orchestration
03 · Connected payment services
Separate provider agreements and authorizations
Company registrations and payment-services licenses do not identify the contracting entity for every product.
Spreedly, Inc.
United States · Delaware corporation
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 Connect is not specified.
Certifications and assessments
PCI DSS
Service provider level 1 · Entity: Spreedly, Inc.
PCI DSS applies to Spreedly, Inc.
SOC 2 Type II attestation
Entity: Spreedly, Inc.
SOC 2 Type II attestation applies to Spreedly, Inc.
Privacy and security controls
Company support hours and contact channels are available. It is not specified which ones cover Connect and routing errors, failed retries or connected-provider outages. First-response and resolution targets are also not specified.
Support contacts
The contacts that cover this product and routing errors, failed retries or connected-provider outages are not specified.
Merchant
24/7
Merchant support
Other company contacts
Support hours are not specified for these contacts.
Merchant support
Developer
Credential capture and storage, tokenization, access controls, data portability, contracting entity and support.
Credential access, tokenization, data location, retention, deletion, backup, export and post-termination portability.
Spreedly stores or exchanges configured credentials and tokens. The configured token, payment or data providers retain token-service, payment authorization, processing and settlement responsibilities.
Vault access & data continuity
Export access, migration timing, retention, deletion, backup and incident-notification terms belong in the vault agreement.
Which credentials and tokens are stored, where, under which access, encryption, residency and audit controls?
Which network, gateway, updater and processor token services are supported, and how are token failures recovered?
The entity providing the technology may or may not also provide regulated payment services. That relationship is not specified for this product.
For this product
Contracting entity and payment services authorization
Spreedly standalone vault technology. The contracting legal entity for Vault is not specified. Any legal entity providing regulated payment services is not specified. The applicable license or registration is not specified.
Whether the same or different legal entities provide the technology and any regulated payment services is not specified.
01 · Contracting entity
Not specified for this product
02 · Payment services legal entity
Not specified for this product
03 · License or registration
Not specified for this product
Company registrations and payment-services licenses do not identify the contracting entity for every product.
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 Vault is not specified.
Certifications and assessments
PCI DSS
Service provider level 1 · Entity: Spreedly, Inc.
PCI DSS applies to Spreedly, Inc.
SOC 2 Type II attestation
Entity: Spreedly, Inc.
SOC 2 Type II attestation applies to Spreedly, Inc.
Privacy and security controls
Company support hours and contact channels are available. It is not specified which ones cover Vault and credential-capture failures, token errors, imports, exports or vault outages. First-response and resolution targets are also not specified.
Support contacts
The contacts that cover this product and credential-capture failures, token errors, imports, exports or vault outages are not specified.
Merchant
24/7
Merchant support
Other company contacts
Support hours are not specified for these contacts.
Merchant support
Developer
Connected providers, routing rules, retries, failover, change controls, contracting entity and support.
Routing rules, retry limits, failover behavior, duplicate-payment protection, rule permissions and rollback.
Payment routing and gateway connections do not make Spreedly the processor or funds holder. Authorization and settlement remain with the selected connected payment providers under their own agreements. The Optimize agreement controls routing rules, retries, failover and access to routing data.
Provider outages & routing continuity
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?
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 Optimize is not specified. Optimize 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.
01 · Software contracting entity
Not specified for this product
02 · Product role
Payment orchestration
03 · Connected payment services
Separate provider agreements and authorizations
Company registrations and payment-services licenses do not identify the contracting entity for every product.
Spreedly, Inc.
United States · Delaware corporation
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 Optimize is not specified.
Certifications and assessments
PCI DSS
Service provider level 1 · Entity: Spreedly, Inc.
PCI DSS applies to Spreedly, Inc.
SOC 2 Type II attestation
Entity: Spreedly, Inc.
SOC 2 Type II attestation applies to Spreedly, Inc.
Privacy and security controls
Company support hours and contact channels are available. It is not specified which ones cover Optimize and routing errors, failed retries or connected-provider outages. First-response and resolution targets are also not specified.
Support contacts
The contacts that cover this product and routing errors, failed retries or connected-provider outages are not specified.
Merchant
24/7
Merchant support
Other company contacts
Support hours are not specified for these contacts.
Merchant support
Developer
Transaction screening, risk scores, rule control, manual review, fallback behavior, contracting entity and support.
Screening inputs, risk scores, rule ownership, manual review, timeout and fail-open or fail-closed behavior.
The business sets its acceptance and review rules. The fraud service returns risk signals or decisions; the payment provider remains responsible for payment authorization and money movement.
Provider outages & rule continuity
Timeouts, fallback rules, manual-review procedures, rule-change controls and service levels belong in the product agreement.
What happens when the fraud-screening service times out, fails or returns no decision?
Who controls risk thresholds, allowlists, blocklists and manual-review actions, and how quickly can they be changed?
Fraud screening & risk decisions
Transaction screening is available. Rule ownership, manual review, timeout behavior and fail-open or fail-closed settings depend on the product configuration and agreement.
Screen
Transaction screening & risk scores
SCREEN
Which signals, models and rules determine the returned risk decision?
The agreement should name the fraud service provider and define its security, privacy and data-processing responsibilities.
For this product
Contracting entity and fraud service provider
Fraud and authentication provider. The contracting entity for Protect is not specified. The fraud service provider entity is not specified. The applicable license or registration is not specified.
A company registration does not identify the contracting entity or the security and data-processing terms for the fraud service.
01 · Contracting entity
Not specified for this product
02 · Fraud service provider entity
Not specified for this product
03 · License or registration
Not specified for this product
Company registrations and payment-services licenses do not identify the contracting entity for every product.
Spreedly, Inc.
United States · Delaware corporation
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 Protect is not specified.
Certifications and assessments
PCI DSS
Service provider level 1 · Entity: Spreedly, Inc.
PCI DSS applies to Spreedly, Inc.
SOC 2 Type II attestation
Entity: Spreedly, Inc.
SOC 2 Type II attestation applies to Spreedly, Inc.
Privacy and security controls
Company support hours and contact channels are available. It is not specified which ones cover Protect and fraud-screening timeouts, missing risk decisions, false positives or rule issues. First-response and resolution targets are also not specified.
Support contacts
The contacts that cover this product and fraud-screening timeouts, missing risk decisions, false positives or rule issues are not specified.
Merchant
24/7
Merchant support
Other company contacts
Support hours are not specified for these contacts.
Merchant support
Developer
Connected data sources, report coverage, refresh timing, reconciliation, retention, contracting entity and support.
Connected accounts, report history, refresh timing, correction handling, exports, retention and post-termination access.
Connected providers remain responsible for their transaction and settlement data. The merchant reconciles provider reports to orders, balances and ledgers.
Data quality & report continuity
Data-quality monitoring, correction timing, report history, exports, retention and post-termination access belong in the agreement.
How quickly are provider outages, missing records and delayed reports detected and corrected?
How much report history remains available after a provider connection or the product account is closed?
The entity providing the technology may or may not also provide regulated payment services. That relationship is not specified for this product.
For this product
Contracting entity and payment services authorization
Payment reporting provider. The contracting legal entity for Resolve is not specified. Any legal entity providing regulated payment services is not specified. The applicable license or registration is not specified.
Whether the same or different legal entities provide the technology and any regulated payment services is not specified.
01 · Contracting entity
Not specified for this product
02 · Payment services legal entity
Not specified for this product
03 · License or registration
Not specified for this product
Company registrations and payment-services licenses do not identify the contracting entity for every product.
Spreedly, Inc.
United States · Delaware corporation
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 Resolve is not specified.
Certifications and assessments
PCI DSS
Service provider level 1 · Entity: Spreedly, Inc.
PCI DSS applies to Spreedly, Inc.
SOC 2 Type II attestation
Entity: Spreedly, Inc.
SOC 2 Type II attestation applies to Spreedly, Inc.
Privacy and security controls
Company support hours and contact channels are available. It is not specified which ones cover Resolve and missing records, delayed reports, incorrect totals or failed exports. First-response and resolution targets are also not specified.
Support contacts
The contacts that cover this product and missing records, delayed reports, incorrect totals or failed exports are not specified.
Merchant
24/7
Merchant support
Other company contacts
Support hours are not specified for these contacts.
Merchant support
Developer
Confirm connected-provider agreements, pricing, routing rules, retries, failover, duplicate-payment protection, logs, support and termination.
Before signing
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
Jump to the underlying product details
Review pricing, connected-provider requirements, routing rules, retries, failover, duplicate-payment controls, logs, support and termination.
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.
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.
Which legal entity will sign the agreement for this product?
The contracting legal entity is not specified for this product.
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.
Who receives security incidents, and what notification window applies?
The security incident contact and notification deadline are not specified.
What first-response, update and resolution targets apply by incident severity?
First-response and resolution targets are not specified.
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.
Which support hours and contact channels cover Connect, and where should a business report routing errors, failed retries or connected-provider outages?
The support scope for Connect and the contacts for routing and connected-provider issues are not specified.
Which support-request topics and routing options are available in the support form?
Support-form topics and routing options are not specified.
What the orchestration product includes, which provider restrictions apply and which routing terms are not specified.
Capabilities included with Connect.
Headless checkout, Drop-in checkout, Embedded payment fields, Mobile SDKs, Universal tokenization, iOS, Android, and React Native
Payment orchestration technology
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.
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.
Confirm pricing, credential storage and tokenization, data location, retention, deletion, portability, service levels, support and termination.
Before signing
Confirm where payment credentials are stored, which providers can use them, and how they can be exported or deleted.
Pricing & migration
Stored-credential and tokenization fees, usage allowances, imports, exports, migration work and support
Storage, access & continuity
Data location, retention, deletion, provider compatibility, uptime, recovery and post-termination access
Contract checklist
Jump to the underlying product details
Review pricing, data location, retention, deletion, provider compatibility, credential import and export, service levels, support and termination.
What portability, export, deletion, retention and continuity terms apply at migration or termination?
Credential and token exit rights are contract-specific.
Which credentials and tokens are stored, where, under which access, encryption, residency and audit controls?
Vault security and data scope depend on the configured service.
Which network, gateway, updater and processor token services are supported, and how are token failures recovered?
Token compatibility and recovery depend on connected providers.
Which entity contracts for the vault, and which token-service and payment providers receive or control each credential or token?
Entity and data roles depend on configured connections.
Which PCI, privacy, residency, encryption, key-management, access, incident, audit and deletion terms apply?
Vault security scope must be explicit for the configured data.
Which contacts, hours and response targets cover vault access, token creation or exchange, credential updates, provider compatibility and data export?
Vault support must cover the stored data and connected token services.
How are token-service failures, security incidents and portability or deletion requests escalated?
Vault, token-service and security ownership must be explicit.
What the vault includes, which use restrictions apply and which storage, portability and service terms are not specified.
Capabilities included with Vault.
Payment cards, ACH bank accounts, Secure payment method storage, Payment method retention, Lifecycle Management, Network tokenization, and Payment method data enrichment
Payment vault
Pricing, storage, retention, deletion, portability, service-level and termination terms to include in the vault agreement.
Unit prices, usage allowances, overage rates, contract length, minimum spend and renewal terms are not specified.
Provider compatibility, data location, retention, deletion, export timing and vault service levels are not specified.
Confirm connected-provider agreements, pricing, routing rules, retries, failover, duplicate-payment protection, logs, support and termination.
Before signing
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
Jump to the underlying product details
Review pricing, connected-provider requirements, routing rules, retries, failover, duplicate-payment controls, logs, support and termination.
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.
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.
Which legal entity will sign the agreement for this product?
The contracting legal entity is not specified for this product.
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.
Who receives security incidents, and what notification window applies?
The security incident contact and notification deadline are not specified.
What first-response, update and resolution targets apply by incident severity?
First-response and resolution targets are not specified.
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.
Which support hours and contact channels cover Optimize, and where should a business report routing errors, failed retries or connected-provider outages?
The support scope for Optimize and the contacts for routing and connected-provider issues are not specified.
Which support-request topics and routing options are available in the support form?
Support-form topics and routing options are not specified.
What the orchestration product includes, which provider restrictions apply and which routing terms are not specified.
Capabilities included with Optimize.
Payment routing, Retries, Provider failover, Recurring payment recovery, Static gateway routing, Split volume routing, Conditional routing, and Retry through another gateway
Payment orchestration technology
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.
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.
Confirm pricing, payment coverage, risk checks, decisions, timeouts, fallback rules, data retention, support and termination.
Before signing
Confirm which risk checks run, what decisions they return and what happens when the service is unavailable.
Coverage, decisions & pricing
Screened volume, billable checks, payment coverage, risk signals, outputs and reason codes
Fallback, control & support
Timeouts, fail-open or fail-closed rules, manual review, rule changes, retention and incident escalation
Contract checklist
Jump to the underlying product details
Review pricing, payment and regional coverage, risk signals, decision output, timeouts, fallback rules, data retention, support and termination.
What happens when the fraud-screening service times out, fails or returns no decision?
Timeout, retry and fail-open or fail-closed behavior is not specified.
Who controls risk thresholds, allowlists, blocklists and manual-review actions, and how quickly can they be changed?
Rule ownership, change controls and manual-review procedures are not specified.
Which legal entity will sign the agreement for this product, and which license or registration applies?
The contracting legal entity is not specified for this product.
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.
Who receives security incidents, and what notification window applies?
The security incident contact and notification deadline are not specified.
What first-response, update and resolution targets apply by incident severity?
First-response and resolution targets are not specified.
Who handles fraud-screening timeouts, missing risk decisions, false positives and manual-review incidents?
No escalation contact or process is specified for fraud-screening and risk-decision incidents.
Which support hours and contact channels cover Protect, and where should a business report fraud-screening timeouts, missing decisions, false positives or rule issues?
The support scope for Protect and the contacts for fraud-screening and risk-decision issues are not specified.
Which support-request topics and routing options are available in the support form?
Support-form topics and routing options are not specified.
What this fraud prevention product includes, which use restrictions apply and which operating terms are not specified.
Capabilities included with Protect.
Fraud-provider integrations, Pre-authorization fraud checks, and 3-D Secure
Fraud screening and 3-D Secure
Pricing, coverage, decision, fallback, retention, service-level and termination terms to include in the agreement.
Unit prices, usage allowances, overage rates, contract length, minimum spend and renewal terms are not specified.
Enabled fraud providers, timeout behavior, fallback rules, decision fields and service levels are not specified.
Confirm pricing, connected accounts, report coverage, history, refresh timing, exports, reconciliation, corrections, retention, support and termination.
Before signing
Confirm which accounts feed the reports, how quickly data updates, how records reconcile and how long exports remain available.
Coverage, history & pricing
Connected accounts, retained history, refresh timing, time zones, usage allowances and export charges
Reconciliation, corrections & retention
Export formats, join keys, missing records, correction timing and post-termination data access
Contract checklist
Jump to the underlying product details
Review pricing, connected accounts, history, refresh timing, exports, reconciliation identifiers, corrections, retention, support and termination.
How quickly are provider outages, missing records and delayed reports detected and corrected?
Data-quality monitoring, correction timing and outage handling are not specified.
How much report history remains available after a provider connection or the product account is closed?
Report retention, export access and post-termination availability are not specified.
Which legal entity will sign the agreement for this product?
The contracting legal entity is not specified for this product.
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.
Who receives security incidents, and what notification window applies?
The security incident contact and notification deadline are not specified.
What first-response, update and resolution targets apply by incident severity?
First-response and resolution targets are not specified.
Who handles missing transactions, delayed reports, incorrect totals and failed exports?
No escalation contact or process is specified for reporting and data-quality incidents.
Which support hours and contact channels cover Resolve, and where should a business report missing records, delayed reports, incorrect totals or export failures?
The support scope for Resolve and the contacts for report and data-quality issues are not specified.
Which support-request topics and routing options are available in the support form?
Support-form topics and routing options are not specified.
What the reporting product includes, which data-source restrictions apply and which reporting terms are not specified.
Capabilities included with Resolve.
Transactions, Provider performance, Feature usage, and Billing
Reporting and reconciliation software
Pricing, data-source, history, refresh, export, correction, retention and termination terms to include in the agreement.
Unit prices, usage allowances, overage rates, contract length, minimum spend and renewal terms are not specified.
Connected accounts, report history, refresh timing, export formats, correction handling and retention are not specified.
