Production onboarding
Production endpoint configuration requires a verified technical transition from development environments to live transaction processing. Cardflo provides development teams with a strict deployment checklist to ensure production payment readiness across all integrated acquirer partners and alternative methods.
- Category
- Developer
- Capabilities
- 10
- Available on
- All plans
Cardflo's production onboarding process is designed for efficiency and clarity. We guide merchants through the necessary steps to configure their payment infrastructure for live transactions, ensuring all compliance and security requirements are met.
Our streamlined approach minimises delays and enables rapid deployment of your payment solution.
Production onboarding streamlines the technical setup required for new MIDs and acquirer connections, ensuring all KYB compliance steps are met. This process quickly activates live processing across Cardflo’s verified acquirer partner network, getting merchants operational without delay.
Production onboarding overview
Production onboarding represents the final technical and operational transition from a sandbox environment to a live processing state. This phase involves the rigorous validation of merchant credentials, the configuration of Merchant Identification Numbers (MIDs), and the formal activation of acquirer connections within the payment gateway or orchestration layer.
During this process, the Payment Service Provider (PSP) verifies that the merchant's integration adheres to Payment Card Industry Data Security Standard (PCI DSS) requirements and relevant regional mandates such as Strong Customer Authentication (SCA) under PSD2.
The workflow ensures that live API credentials are securely exchanged and that all risk management parameters, including Anti-Money Laundering (AML) and Know Your Business (KYB) checks, are fully satisfied. By systematic alignment of technical endpoints and financial accounts, this stage mitigates the risk of transaction failures or settlement delays at the point of launch.
How production onboarding works
Credential validation and KYB assessment
The process commences with a comprehensive review of the merchant's legal entity status and operational risk profile. Compliance teams evaluate corporate documentation to satisfy AML and KYB requirements. This ensures that the entity is authorised to handle cardholder data and receive settlements through the specified banking partners and acquirers.
MID and acquirer configuration
Upon approval, the system facilitates the setup of production Merchant Identification Numbers. This involves linking the gateway to specific acquiring banks and ensuring that Merchant Category Codes (MCCs) are correctly assigned. These identifiers are essential for the accurate routing of authorisation requests and the subsequent clearing and settlement of funds.
Security protocol and 3DS enforcement
Technical teams verify the implementation of security measures including TLS versioning and 3D Secure (3DS) configurations. The onboarding workflow ensures that the merchant's environment is prepared to handle SCA signals, reducing the likelihood of soft declines by issuers who require additional authentication for live cross-border or high-value transactions.
Live API key synchronisation
Sandbox credentials are decommissioned in favour of live production keys and secrets. This step requires the merchant to update their environment variables to point towards production endpoints. A final connectivity test is often performed to confirm that the gateway correctly recognises the authenticated requests from the merchant server.
Final settlement and payout verification
The final stage involves the verification of the merchant's bank account details for settlement purposes. This ensures that the flow of funds from the acquirer through the PSP to the merchant's corporate account is unimpeded. Any reserve requirements or rolling reserves are also finalised during this concluding administrative phase.
Why production onboarding matters
Risk Mitigation and Compliance Assurance
A structured production onboarding process ensures that all regulatory hurdles are cleared prior to the processing of the first live transaction. By verifying PCI DSS compliance and KYB status early, merchants avoid the risk of sudden account suspension or fund freezes. This rigorous check protects both the merchant and the acquirer from fraud and legal non-compliance, establishing a stable foundation for long-term transaction processing.
Authorisation Rate Optimisation
Correct configuration of MIDs, MCCs, and 3DS protocols during onboarding directly influences authorisation success rates. If a merchant is incorrectly categorised or if authentication signals are missing, issuers are more likely to issue hard declines. Precise setup ensures that transaction metadata is transmitted accurately, allowing issuer risk engines to process requests with higher confidence and lower friction for the end consumer.
Production onboarding use cases
Endpoint configuration go-live
Lead developers moving a checkout into production must replace non-live API base URLs, callback destinations and environment flags without sending payment requests to the wrong endpoint. Cardflo supports a configuration review covering production URLs, MID mapping, 3DS2 return paths and webhook destinations before live traffic is enabled.
First live payment verification
Technical project managers need to confirm that an initial live card payment completes authorisation, 3DS2 handling, capture and webhook delivery before wider release. Cardflo helps teams trace the transaction through gateway orchestration and the selected acquirer partner, then verify response codes, order state and reporting records.
Production traffic surge readiness
Retail teams launching a timed product release can exceed production API rate limits when checkout sessions, payment attempts and status requests rise together. Cardflo reviews expected request profiles, coordinates production thresholds and helps technical teams monitor latency, throttling responses, authorisation rates and routing behaviour during the opening traffic window.
Production alerting handover
Operations teams taking ownership after deployment need production alerts that distinguish checkout errors, acquirer timeouts, 3DS2 failures and webhook delivery delays. Cardflo helps define launch dashboards and escalation contacts, then supports close monitoring of initial live transactions so technical owners can investigate failures before normal operational coverage begins.
Production onboarding by the numbers
This represents a typical range seen by merchants who correctly configure MIDs and 3DS during the live onboarding process compared to unoptimised setups.
Industry standard for automated KYB tools used during onboarding to ensure compliance with global anti-money laundering regulations and sanctions screening.
The standard settlement period for many merchants once a production account is fully activated and the initial verification phase is complete.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Production onboarding
- Validation of corporate legal documents to satisfy global KYB and AML regulatory mandates.
- Technical verification of PCI DSS compliance levels required for live transaction processing environments.
- Assignment and activation of specific Merchant Identification Numbers (MIDs) for domestic and international acquirers.
- Configuration of Merchant Category Codes (MCCs) to align with card scheme industry classifications.
- Exchange of production-grade API keys and secure authentication tokens for live server communication.
- Implementation and testing of 3D Secure protocols to satisfy SCA requirements under PSD2.
- Setup of Alternative Payment Methods (APMs) and digital wallets within the live checkout environment.
- Verification of settlement bank accounts and confirmation of payout cycles for cleared funds.
- Configuration of webhooks for real-time transaction status updates and automated reconciliation processes.
- Fine-tuning of risk threshold settings and fraud prevention filters within the production gateway layer.
A short scoping call, then a written plan for your MIDs.
Questions about Production onboarding
How long does the production onboarding process typically take for a standard merchant?
The duration of production onboarding varies based on the complexity of the merchant's treasury requirements and the speed of the KYB verification. For standard low-risk businesses, the process may conclude within three to five business days.
However, for high-risk merchants or those requiring multiple international acquirer connections, the timeline may extend to several weeks.
This period includes the time necessary for the acquiring bank to review the application, the technical setup of MIDs, and the final validation of the integration's security protocols.
What is the difference between sandbox testing and production onboarding?
Sandbox testing occurs in a simulated environment where no real money moves and transactions are processed against mock issuer responses. Production onboarding is the process of moving that integration into the live financial ecosystem.
This requires real API keys, verified legal documentation, and active connections to acquiring banks. While sandbox testing focuses on code logic, production onboarding focuses on regulatory compliance, financial settlement, and the actual movement of funds through the card schemes.
Which checks confirm production payment readiness before live traffic begins?
Technical project managers should confirm that live endpoint URLs, webhook destinations, allowed domains and production configuration values are deployed in the correct environment.
They should also verify that monitoring, alerting, reconciliation references and incident contacts are active, and that expected traffic remains within production rate limits. The launch record should identify the approved MID, currencies and payment methods, with rollback criteria agreed before genuine customer transactions begin.
Why is KYB documentation necessary at this stage of the integration?
Know Your Business (KYB) documentation is a legal requirement for Payment Service Providers and acquirers to prevent money laundering and terrorist financing.
During onboarding, the provider must verify the ultimate beneficial owners of the company and ensure the business is not on any international sanctions lists.
This due diligence protects the integrity of the payment network and is a non-negotiable step before live transactions can be authorised or settled.
How do software updates or changes to the API affect an already onboarded merchant?
Once a merchant has completed production onboarding, minor API updates are typically handled through versioning to ensure backward compatibility. However, significant changes to data handling or the introduction of new regulatory requirements, such as PSD3, may require a brief re-onboarding or validation step.
Continuous monitoring is practised to ensure that the merchant's technical setup remains in alignment with changing card scheme rules and security standards.
What happens if a merchant fails the compliance check during onboarding?
If a merchant fails the initial compliance or KYB check, the onboarding process is paused. The provider will typically issue a request for further information or clarification regarding the business's operations, ownership, or financial standing.
If the risks cannot be mitigated or if the business model violates the terms of service of the acquirer or the card schemes, the application for a production account may be declined.
Related guides.
See how Cardflo compares.
From the blog
Opening a merchant account is essential for any eCommerce or retail business wanting to accept electronic payments. This guide explains how acquiring banks and providers process transactions from Visa and Mastercard. It details the necessary documentation and steps required to receive funds from customer card payments. Merchants must select the specific networks they wish to accept before applying.
Read articleHigh-risk industries require specialised merchant accounts to manage financial instability and fraud risks. These accounts enable secure credit and debit card processing for sectors like adult entertainment. Cardflo supports high-risk models by providing tailored accounts with advanced risk tools to ensure efficient business operations. This guide outlines the key considerations for researching these accounts.
Read articleReady to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.