Test Mode
- Dashboard and workflow exploration
- Eligible test connectors and credentials
- Simulated or provider-sandbox scenarios
- Integration and response validation
- No real payment processing
Production Access
Move From Test Mode to Production
Tell us how you intend to use Transaqo so we can prepare the appropriate production environment, provider configuration, and implementation scope.
IMPLEMENTATION PATHFrom testing to a defined production environment
- 01Test ModeExplore and integrate
- 02RequirementsProviders and flows
- 03ArchitectureDeployment and boundaries
- 04ConfigurationEnvironment and connectors
- 05ValidationAgreed production scenarios
- 06ProductionActivated after readiness review
Production access is prepared around the selected providers, architecture, responsibilities, and implementation scope.
Production Readiness
Live processing requires a separate production setup.
Test Mode allows teams to explore the dashboard, configure eligible test connections, and begin integration work without processing real payments. Production introduces live provider credentials, business-specific configuration, security responsibilities, operational contacts, and an agreed service model.
Production environment
- Live provider relationships and credentials
- Production configuration and deployment
- Security and operational responsibilities
- Agreed support and implementation model
- Validation before activation
Production Request
Define the implementation before live processing begins.
Provide enough information for an initial review of the intended operating model, providers, payment flows, deployment, and production responsibilities.
01
Business and intended use
02Who will use the environment and for what operating model.
Providers and payment activity
03Connections, account status, markets, and approximate scale.
Integration and deployment
04How the platform will connect, run, and be supported.
Operational ownership
Contacts and responsibilities for production preparation.
Do not submit secrets.
Do not enter API keys, passwords, payment credentials, card data, webhook secrets, private keys, or bank-account credentials in this form.
Information Required
Eight areas define the production scope.
The initial review connects the intended business model with provider access, payment activity, technical integration, deployment, and operational ownership.
- 01
Business and Website
Establish the legal business, operating context, markets, and principal contact.
- 02
Intended Use
Define whether the environment supports a merchant, brands, a marketplace, a PSP, an ISO, or another platform model.
- 03
Payment Providers
Identify the PSPs, acquirers, methods, risk tools, vaults, authentication, and payout services to connect.
- 04
Provider Account Status
Clarify which relationships are approved, in progress, being evaluated, or not yet selected.
- 05
Expected Payment Activity
Provide approximate transaction scale, currencies, markets, methods, and launch stage where available.
- 06
Integration Model
Define the intended checkout, API, SDK, existing-platform, or Payment Bridge approach.
- 07
Deployment Model
Select or assess managed, dedicated, private-cloud, client-hosted, or on-premises infrastructure.
- 08
Operational Contacts
Identify the people responsible for technical implementation, production operations, security, and commercial coordination.
Production Access Process
From initial review to controlled activation.
Each stage confirms a different part of the production implementation. Activation occurs only after the relevant technical, operational, and commercial requirements are completed.
- 01
Review
Transaqo reviews the requested operating model, connectors, and implementation scope.
- 02
Connector Confirmation
Available integrations, required configuration, and any custom development needs are confirmed.
- 03
Architecture and Responsibility Definition
The integration model, payment-data architecture, deployment responsibilities, and operational boundaries are defined.
- 04
Commercial Agreement
The applicable platform, implementation, support, infrastructure, and connector terms are agreed.
- 05
Production Configuration
The production environment, accounts, credentials, connectors, routing rules, and relevant modules are prepared.
- 06
Validation
The agreed payment flows are tested using production or provider-certification procedures where required.
- 07
Activation
Production processing is enabled after the applicable technical and operational requirements have been completed.
Provider Approval Remains Separate
Platform access does not replace provider onboarding.
Production access to Transaqo does not itself provide approval from an acquirer, PSP, bank, payout service, fraud or authentication provider, or another financial provider.
Client
Maintains the provider relationships and accounts required for its payment activity unless a separate arrangement expressly provides otherwise.
Transaqo
Enables the technical connection, configuration, and platform operation within the agreed implementation.
Connected providers
Determine merchant acceptance, pricing, settlement, reserves, risk conditions, supported countries, and service availability.
Production Preparation
Prepare Your Production Environment
Submit your provider, integration, deployment, and operational requirements.