Skip to main content
HighRiskPaymentProvider.comPayment provider reviews
BR-DGE Integrate and Connect

Company overview

About BR-DGE

What the company provides

  • Orchestrator
  • Gateway
  • Payment data reporting provider
  • Payment vault provider

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

BR-DGE is payment-orchestration software operated by Comcarde Limited.

Its modular products provide hosted and API integration, connections to payment providers, rules-based routing, central tokenisation, consolidated reporting and white-label orchestration. BR-DGE states that it is not a payment service provider and does not hold funds; the merchant or white-label client retains its contracts with connected PSPs and acquirers, which provide the merchant account, any MID, payment underwriting, financial processing, funds custody and settlement.

br-dge.toUpdated Aug 15, 2026

Selected product

BR-DGE Integrate and Connect

BR-DGE Integrate hosted and API integration

Gateway account & connected payment providers

  1. Connected payment account

    Not included with this product

  2. Connected-provider approval

    BR-DGE reviews access to BR-DGE Integrate hosted and API integration; final approval by the merchant underwriter

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

Primary legal entity

Comcarde Limited

Jurisdiction
United Kingdom
Registration number
SC454090
Incorporated
Jul 9, 2013
Company type
Private limited company

Legal entities by jurisdiction

One legal entity registered in United KingdomOne jurisdiction

Operating scale

Platform connections
≥400 payment ecosystem connections
Payment providers and acquirers
≥100 PSPs and acquirers
Payment methods
≥300 payment methods

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

Product portfolio

BR-DGE products

Compare payment orchestration, payment vaulting, and payment reporting and analysis by account setup, approval, payment or data flow, and contract terms.

BR-DGE Integrate and Connect

Role in this product

  • Payment gateway
  • Checkout technology provider
  • Payment orchestration provider
  • Payment provider connection layer

Use REST API, hosted SDK components or a hosted payment page to connect the merchant experience to BR-DGE and activate configured PSP, acquirer, payment-method, fraud and authentication connections.

BR-DGE supplies the integration and connectivity layer; each connected provider retains its own commercial approval, merchant account, MID, payment decision and funds responsibilities.

Related services
Alternative payment methodsDirect APIEmbedded checkoutFraud preventionHosted checkoutPayment orchestration
Features
GatewayCheckoutPSP and acquirer connectionsPayment operationsFraud and riskClient onboardingUnderwritingPricingCompliance

BR-DGE Optimise

Role in this product

  • Payment orchestration provider

Configure processor priority, amount and currency rules, load balancing, multi-level routing and failover across approved pay-in and pay-out providers.

BR-DGE evaluates the merchant's rules and routes the request; the selected provider performs authorization, financial processing and funds movement.

Related services
Decline recoveryPayment orchestrationPayment routing
Features
OrchestrationPayment operationsFraud and riskReportingClient onboardingUnderwritingPricingCompliance

BR-DGE Vault

Role in this product

  • Payment vault provider

Capture and store sensitive card credentials in a PCI-compliant central vault, combine network and gateway tokens behind a BR-DGE token, import existing card data and preserve routing choice across linked processors.

The vault protects credentials but does not provide a merchant account, card acquiring or settlement.

Related services
Payment vault
Features
Client onboardingUnderwritingPricingCompliance

BR-DGE Insights

Role in this product

  • Payment data reporting provider

Consolidate online payment data into real-time dashboards covering success, failure, provider routing, acquiring rates, volumes, credential and token status, authentication and fraud-provider flows.

Insights reports on connected-provider activity; it does not replace the provider's financial or settlement records.

Related services
Payment orchestration
Features
ReportingClient onboardingUnderwritingPricingCompliance

BR-DGE White Label

Role in this product

  • Payment orchestration provider

Embed BR-DGE integration, connectivity, routing, vault and reporting modules under a payment provider's or platform's brand.

The white-label client continues to own its merchant relationship and any regulated or acquiring services it supplies; BR-DGE remains the underlying technology layer.

Related services
Direct APIPayment orchestrationPayment routingPayment vault
Features
GatewayPSP and acquirer connectionsOrchestrationFraud and riskReportingClient onboardingUnderwritingPricingCompliance

Selected product

BR-DGE Integrate and Connect

Related services
6 capabilities
Features
9 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 gateway · Checkout technology provider · Payment orchestration provider · Payment provider connection layer
02 · Orchestration platform
Not included with this product
03 · Production activation
Separate approval from the merchant's PSP or acquirer
04 · Connected-provider funds
BR-DGE does not hold merchant funds or provide merchant settlement

Selected product: BR-DGE Integrate and Connect.

Checkout

BR-DGE Integrate and Connect: checkout, payment data & provider connections

Review checkout ownership, payment-data handling, supported integrations and the connected providers required for live payments.

Selected product: BR-DGE Integrate hosted and API integration

Included in BR-DGE Integrate and Connect

Features included with this product.

Solutions
Alternative payment methodsDirect APIEmbedded checkoutFraud preventionHosted checkoutPayment orchestration
Capabilities
GatewayCheckoutPSP and acquirer connectionsPayment operationsFraud and riskClient onboardingUnderwritingPricingCompliance

Checkout, payment data & provider roles

Who operates checkout, handles payment data, authorizes payments and handles merchant funds for BR-DGE Integrate and Connect.

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

Gateway availability
Available by commercial agreement and implementation scope. Every payment route also requires the merchant's or white-label client's separate approval, contract and credentials with the relevant connected provider.
Transaction processing
No
Merchant settlement
No
Merchant funds
No
Merchant funds
Does not handle merchant funds
Merchant account
No
MID
No
Direct acquiring
No
Merchant account model
BR-DGE supplies hosted and API gateway technology. The merchant's connected PSP or acquirer supplies and controls the merchant account, any MID, payment underwriting, financial processing, reserves and settlement.
  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
  • Server to server REST API
  • Web SDK
  • Android SDK
  • iOS SDK
  • Hosted fields
  • Hosted payment page

Gateway

Payment technology

Connected payment provider

Types of connected payment providers
  • Acquirer
  • Digital wallet
  • Gateway
  • Open Banking
  • Payment processor
  • PSP
Acquirer-independent
Yes
Processor-independent
Yes

Security controls

Tokens and payment authentication

Tokenization
Yes
3-D Secure
Yes
Token formats
  • BR-DGE Vault token
  • Gateway token
  • Network token

Operations

Webhooks, Control Panel and test environment

Tools used to test an integration and manage live payments.

Webhooks
Yes
Merchant control panel
Yes
API-oriented
Yes
Gateway included
Yes
Merchant chooses merchant services
Yes
Onboarding included
Yes
Gateway features
  • REST API
  • Hosted SDK components
  • Hosted payment page
  • Payment provider connection
  • Payment method configuration
  • Transaction response normalisation
Webhook events
  • Payment status change
  • Payout status change
  • Refund status change
Role in this product
Gateway
Questions to confirm

Which connectors apply to BR-DGE Integrate hosted and API integration?

Connectors are not specified for BR-DGE Integrate hosted and API integration.

Is a sandbox available for BR-DGE Integrate hosted and API integration?

Sandbox is not specified for BR-DGE Integrate hosted and API integration.

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 · BR-DGE Integrate hosted and API integration

Which connected providers must approve this setup?

BR-DGE reviews access to BR-DGE Integrate hosted and API integration; final approval by the merchant underwriter.

Product eligibility

Owner, director and operating-location requirements are not specified

Connected-provider approval

BR-DGE reviews access to BR-DGE Integrate hosted and API integration; final approval by the merchant underwriter

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

Provider connection
Merchant underwriter named in the agreement
Product
BR-DGE Integrate hosted and API integration
Regulated-business license
Required license type and issuing jurisdiction are not specified
01Product eligibility & acceptable use

Which businesses and provider connections can use this product?

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

Eligibility requirements

01

Eligibility information

This is BR-DGE technology and implementation acceptance, not payment or merchant-account underwriting. Connected PSPs and acquirers control merchant approval, any MID, reserves, financial processing and settlement.

02

Platform account decision

BR-DGE technology-client acceptance is separate from every PSP, acquirer, merchant-account, payment-method and fraud-provider decision.

03

PSP and acquirer connection requirements

BR-DGE can connect and configure providers, but the merchant or white-label client obtains each provider's separate approval and account unless that client itself supplies the regulated service.

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

Restricted activity

Business restrictions

Product · MCC · jurisdiction · sales practice

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

02Product & provider setup

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

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

Product & provider setup

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

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

Platform account documents

Documents to prepare

  1. 01Business and integration information
  2. 02Selected provider and payment flow details
  3. 03Business and integration requirements
  4. 04Connected provider contracts and credentials
  5. 05Payment flow and routing requirements
  6. 06Security and PCI scope information

Platform account setup

  1. 01

    Define whether the client is an enterprise merchant, payment provider or platform and select the required BR-DGE modules.

  2. 02

    Map existing and planned PSP, acquirer, payment-method, authentication and fraud-provider relationships.

  3. 03

    Complete each connected provider's separate merchant or partner application, contract, KYC and credential exchange.

  4. 04

    Choose REST API, hosted SDK or Hosted Payment Page integration and define PCI scope.

  5. 05

    Configure provider priority, routing, failover, tokenisation and reporting rules that apply to the selected modules.

  6. 06

    Test the complete flow with each provider before production activation.

Product & provider requirements

Account and provider-connection checks

Application and activation requirements.

Website requirements

Required website pages, disclosures and policies are not specified

Account review requirements

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

Account setup tasks

The onboarding tasks performed by the provider are not specified

Before applying

Application requirements to confirm

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

Approval & restrictions

Who reviews the business and which products, jurisdictions or MCCs are excluded.

  1. 01

    Which payment provider will make the final approval decision?

    Final approval by the merchant underwriter; the specific legal entity is set in the merchant agreement.

  2. 02

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

    These approval requirements are not specified.

  3. 03

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

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

Underwriting process & approval time

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

  1. 04

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

    Final approval timing is not specified.

Payment methods & countries · BR-DGE Integrate hosted and API integration

Which countries and payment methods are available for this gateway or orchestration setup?

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

Selected product

BR-DGE Integrate hosted and API integration

Payment setup not specified

Selected product

Client company

Eligible client countries are not specified

Business availability and connected-service coverage are separate requirements.

Payment connection capabilities

Payment connection capabilities are not specified

Availability depends on

  • Connected provider
  • Business country
  • Payment method
  • Currency

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

01Selected product

BR-DGE Integrate hosted and API integration capabilities and connections

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

02Countries & availability

Where can the client be based, which PSP or acquirer serves each target market, and where can customers pay?

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

  1. 01

    Client location

    Where can the company using the technology be registered?

    Eligible client countries are not specified

    This is where the business is registered; it does not determine acquiring-country or customer-country availability.

    Client and merchant-account eligibility
  2. 02

    Acquiring countries

    Where is merchant acquiring available?

    The acquirer for each target country is not specified

    Across all products
  3. 03

    Customer location

    Where can customers pay from?

    Customer countries are not specified

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

    Across all products

Countries and payment methods

Countries and payment methods to confirm

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

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

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

    Commercial and account requirements differ by connected provider.

Pricing & funds · BR-DGE Integrate hosted and API integration

What does BR-DGE Integrate hosted and API integration cost, and which related charges are governed by another agreement?

Checkout price, billable usage, contract term and additional costs

Pricing

Checkout price, billable usage, contract term and additional costs

Pricing method

Not publicly disclosed

01Commercial terms

What makes up the quoted price?

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

Pricing model

  • Not publicly disclosed

Public rates

No public rate card

Other fee amounts

Not specified
Monthly fee

Amount not specified

Setup fee

Amount not specified

Application fee

Amount not specified

Annual fee

Amount not specified

Gateway fee

Amount not specified

PCI fee

Amount not specified

Daily batch fee

Amount not specified

Early termination fee

Amount not specified

Monthly minimum

Amount not specified

These fee amounts are not specified.

02Billing basis

Which usage units determine the recurring bill?

The usage units that determine the recurring bill.

Usage drivers

Not specified

Transaction volume, payment methods, provider connections and optional checkout components

The quantities, included allowances and overage rates are not specified.

03Contract & additional costs

How is the product invoiced, and which costs sit outside the base price?

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 & 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

Additional costs

Implementation, optional-service, third-party and support charges outside the base price.

Additional fee categories

May apply
  • Selected platform modules
  • Implementation and integration
  • Provider connections
  • Transaction volume
  • Connected provider fees

Amounts and applicability depend on the connected provider or optional service.

Pricing & contract terms

Terms to confirm in the agreement

Price

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

  2. What initial term, renewal rule, cancellation notice, billing cycle and invoice currency apply?

    The contract and invoicing terms are not specified.

  3. What amounts and triggers apply to selected platform modules, implementation and integration, provider connections, transaction volume, and connected provider fees?

    These additional fee categories can apply, but their amounts and triggers are not specified.

Other terms

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

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

Checkout flow · BR-DGE Integrate hosted and API integration

How do checkout, tokenization, provider connections and implementation work?

Checkout surfaces, tokenization, connected providers, SDKs and events

Checkout flow

Collect payment details → tokenize → submit → events & diagnostics

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

BR-DGE Integrate hosted and API integration

Checkout integrations, tokenization, provider connections, SDKs and webhooks.

  1. Checkout surfaces

    BR-DGE REST API · BR-DGE hosted SDK and fields

  2. Merchant-services connections

    Merchant account provider · Connected merchant account provider · Merchant underwriting · Connected merchant underwriting

  3. Checkout responsibilities

    Gateway · Comcarde Limited trading as BR-DGE · Merchant account provider · Connected merchant account provider

  4. SDKs & implementation

    Android · iOS

01

Checkout surfaces

Which hosted, embedded or API checkout options are available?

Merchant-controlled and embedded checkout options for collecting payment details.

Checkout products

  • BR-DGE REST API
  • BR-DGE hosted SDK and fields
  • BR-DGE Hosted Payment Page

Checkout capabilities

  • Merchant-controlled REST API checkout
  • Hosted fields
  • Hosted payment page
  • Customisable payment method presentation
  • Web and mobile support
  • PCI scope reduction
02

Merchant-services connections

Which payment providers can checkout connect to?

The merchant-account, underwriting, acquiring, processing and settlement parties used with this checkout product.

Selected setup

Connections entry point

How requests enter this product and which integration boundary applies.

Merchant-services roles

  • Merchant account provider · Connected merchant account provider
  • Merchant underwriting · Connected merchant underwriting

Merchant-services connections

Connected payment-provider types

Connections

No additional merchant-services connections details are specified.

Tokenization & reuse

Tokenization & reuse

Token creation and reuse for future or recurring payments.

Tokenization
  • BR-DGE Vault token
  • Gateway token
  • Network token
03

Checkout responsibilities

Who collects and tokenizes payment details, authorizes payments and handles funds?

BR-DGE Integrate hosted and API integration supplies the checkout and gateway. Merchant-account approval, processing and settlement remain with the parties assigned below.

Checkout responsibilities

  • Gateway · Comcarde Limited trading as BR-DGE
  • Merchant account provider · Connected merchant account provider
  • Merchant underwriting · Connected merchant underwriting
04

SDKs & implementation

Which SDKs, events and implementation diagnostics are available?

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.

  1. 01

    SDKs & implementation

    Client SDKs, environments, event handling and operational diagnostics.

    Mobile SDKs

    • Android
    • iOS

    Webhooks

    • Payment status change
    • Payout status change
    • Refund status change

    Merchant Interface

    Available

Before integration

Integration details not specified

  1. 01

    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.

  2. 02

    Which legal entities act as merchant account provider and merchant underwriting for BR-DGE Integrate hosted and API integration, 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.

  3. 03

    Are request logs and API error diagnostics available, and how long are they retained?

    Request-log availability, fields and retention are not specified.

Checkout, credentials & support

BR-DGE Integrate and Connect: risk, licenses & support

Checkout integration, payment-provider connections, tokenization, data handling, contracting entity and support.

BR-DGE Integrate and ConnectService: BR-DGE Integrate hosted and API integration
01 / Checkout & data continuity

What happens when checkout or a connected provider fails?

Timeout handling, fallback behavior, duplicate-payment protection, payment-data retention, deletion and portability.

Checkout & data continuity

BR-DGE provides checkout and payment-provider connections

Connected gateways, processors and acquirers authorize transactions and handle merchant funds. The BR-DGE Integrate hosted and API integration agreement controls the checkout integration, stored credentials and provider connectivity.

Role in this product
Payment gateway · Checkout technology provider · Payment orchestration provider · Payment provider connection layer
Connected providers & merchant funds
BR-DGE does not hold merchant funds or provide merchant settlementThe funds holder and merchant settlement provider are not specified.

Checkout outages & data continuity

How are failed checkouts and stored credentials handled?

Timeouts, fallback behavior, duplicate-payment protection, data retention, deletion and export terms belong in the agreement.

  • What happens when checkout or a connected payment provider is unavailable or returns an uncertain result?

  • Which payment fields are collected, stored or passed to connected providers, and how can stored credentials be exported or deleted?

Fraud, authentication & chargebacks

Fraud screening, 3-D Secure and chargeback handling

Fraud screening and 3-D Secure are available. Responsibility for chargebacks, refunds, fraud losses and negative balances is not specified. The agreement must also state who can suspend processing or hold settlement funds.

  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 fraud provider connectivityThird-party authentication connectivityRisk profile routing3-D Secure route configuration
Screening · Model
BR-DGE can connect third-party fraud tools and use their outputs in merchant-configured workflows; the public product material does not establish BR-DGE as the merchant's payment underwriter.
Third-party fraud integration
Fraud prevention services3-D Secure and authentication services

AT CHECKOUT

3-D Secure authentication

Which 3-D Secure and verification methods are included?

Authentication · Model
BR-DGE can connect and route to configured authentication services. The selected provider performs the authentication service under its own agreement.
3-D Secure
Yes
Before signingCheckout outage, fallback, payment-data retention, deletion and portability terms2 items to confirmReview contract terms
02 / Legal entity, license & registration

Which legal entity provides the payment technology product and any regulated payment services?

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 gateway. The contracting legal entity for BR-DGE Integrate and Connect 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.

  1. 01 · Contracting entity

    Not specified for this product

  2. 02 · Payment services legal entity

    Not specified for this product

  3. 03 · License or registration

    Not specified for this product

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

Comcarde Limited

United Kingdom · Registry SC454090 · Private limited company · Incorporated Jul 9, 2013

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 BR-DGE Integrate hosted and API integration is not specified.

01

Security standards

Certifications and assessments

PCI DSS service provider

Service provider level 1 · Third-party service provider · Entity: Comcarde Limited

PCI DSS service provider applies to Comcarde Limited.

SOC 2 Type 2 attestation

Entity: Comcarde Limited

SOC 2 Type 2 attestation applies to Comcarde Limited.

02

Security controls

Privacy and security controls

Security controls
PCI DSS level one service providerSOC two type two attestationMulti cloud multi region architectureRegular penetration testingHosted card data collection options
General
info@br-dge.to
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 BR-DGE Integrate hosted and API integration and checkout, tokenization or provider-connection failures. First-response and resolution targets are also not specified.

Support contacts

Company support hours and contacts

The contacts that cover this product and checkout, tokenization or provider-connection failures are not specified.

Company contacts

Support hours are not specified for these contacts.

Sales

br-dge.to/contact

General

info@br-dge.to

Developer

docs.br-dge.io
Before signingSupport contacts, hours and response times3 items to confirmReview contract terms
BR-DGE Integrate hosted and API integration / Before signing

What should the technology services agreement include?

Confirm product scope, software pricing, connected-provider responsibilities, data handling, service levels, support and termination.

Before signing

BR-DGE Integrate hosted and API integration: terms to confirm

Confirm the product scope, connected-provider responsibilities, pricing, data handling, service levels and exit terms.

Product, usage & pricing

Included features, environments, usage allowances, overage rates, third-party costs and contract term

Data, service levels & exit

Data handling, security, uptime, recovery, support, suspension, portability and termination

Contract checklist

Terms to review by topic

Jump to the underlying product details

  1. 01Availability, security & continuityService levels, incident handling, data access, suspension and post-termination continuity.
  2. 02Contracting entity & service responsibilitiesTechnology contract, data roles, connected-provider agreements and any regulated service involved.
  3. 03Technical supportSupport contacts, hours, severity levels, response targets and escalation.
Technology services agreement

Product terms to confirm

Review software pricing, integration scope, connected-provider responsibilities, data handling, service levels, support and termination.

Availability, security & continuityService levels, incident handling, data access, suspension and post-termination continuity.

  1. What happens when checkout or a connected payment provider is unavailable or returns an uncertain result?

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

  2. Which payment fields are collected, stored or passed to connected providers, and how can stored credentials be exported or deleted?

    Payment-data handling, retention, deletion and portability terms are not specified.

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

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

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

Technical supportSupport contacts, hours, severity levels, response targets and escalation.

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

    First-response and resolution targets are not specified.

  2. Who handles checkout failures, token errors, provider-connection outages and duplicate-payment risks?

    No escalation contact or process is specified for checkout and provider-connection incidents.

  3. Which support hours and contact channels cover BR-DGE Integrate hosted and API integration, and where should a business report checkout, tokenization or provider-connection failures?

    The support scope for BR-DGE Integrate hosted and API integration and the contacts for checkout and provider-connection issues are not specified.

Product summary

What this product already includes

What this technology product includes, which configuration restrictions apply and which service terms are not specified.

Included capabilities

Capabilities included with BR-DGE Integrate hosted and API integration.

  • Merchant-controlled REST API checkout, Hosted fields, Hosted payment page, Customisable payment method presentation, Web and mobile support, PCI scope reduction, BR-DGE REST API, BR-DGE hosted SDK and fields, BR-DGE Hosted Payment Page, Android, and iOS

  • Payment gateway technology

Product restrictions and conditions

Acceptable use, supported connections, configuration limits, data conditions and account restrictions.

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

Terms to confirm

Pricing, integration, data, service-level, support and termination terms to include in the technology agreement.

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