Onboarding and KYC already start inside your brand.
Registration, identification and validation can happen within your experience, with IOPAY technology working behind the scenes in a white-label model.
KYCOnboardingWhite-label
White-label
Your brand in front. From KYC to final operations
Build your own onboarding, KYC, payment and operations journeys without rebuilding the financial layer from scratch. Your company controls the experience; IOPAY connects KYC, payments, APIs, sellers, split, events and reconciliation under a white-label architecture.
White-label
Your brand.
A single experience for different touchpoints.
Checkouts
Links
Platforms
Portals
Sellers
IOPAY White-label
A complete operation.An experience that's entirely yours.
White-label doesn't have to mean rebuilding onboarding, KYC, payments, sellers, rules and financial operations. The same base can be embedded into your product and evolve as complexity grows.
01 · KYC
The journey goes from registration to payment with no change of context.
From customer entry to charge confirmation, the experience can stay aligned with your interface, rules and commercial flow.
Your own UXContinuous flowConversion
Financial logic remains configurable and fully transparent.
Sellers, split, transfers and reconciliation can follow the operation's original context instead of being born in parallel controls.
SellersSplitReconciliation
The same base keeps up with growth.
Start with a focused journey and evolve the integration as new products, channels, participants and rules enter the operation.
ScaleNew channelsMore automation
01
KYC & onboardingRegistration and validation inside your brand.
↗02
ExperienceThe commercial journey stays continuous until payment.
↗03
OperationPayments, sellers, split, events and reconciliation.
↗04
ScaleThe same base supports new products, channels and operations.
↗
Platform features
Far beyond checkout.
KYC & KYB
Orchestration
Multi-acquiring
Payments
Account & settlement
APIs & webhooks
Risk & antifraud
Recurring payments
Analytics
Reconciliation
White-label can cover the entire operational journey: customer entry and validation, payment capture, financial rules, seller management, automations, post-transaction and financial visibility.
01 · EntryOnboarding
Compliance, KYC & KYB
Merchant pre-registration
Individual and business validation
Approval and rejection flows
Internal risk score
Compliance checks and verifications
02 · CapturePayment core
Payments & transaction lifecycle
Pix, card and boleto
Multi-acquiring and orchestration
Smart routing and redundancy
Authorization, pre-authorization and capture
Tokenization, one-click buy and zero-dollar check
Cancellations and refunds
03 · MarketplacesMulti-party
Sellers, split & distribution
Seller and recipient management
Split per transaction
Transfers and payouts
Accounts and balances per participant
Event and transaction queries
04 · FinanceMerchant OS
Account, receivables & settlement
Balances, future schedule and receivables
Financial calendar
Prepayments, settlements and payouts
Statements, ledger, queries and reports
Inflows, outflows, transfers and payouts
05 · DeveloperAPI-first
APIs, SDKs & sandbox
REST APIs
Interactive documentation
Isolated test and sandbox environments
Transaction simulators
SDKs: Laravel, PHP, JavaScript, NodeJS, Java and Python
Authentication, credentials and custom integrations
06 · EventsAutomation
Webhooks & messaging
Configurable callbacks
Real-time events
Automatic retries
Integration with internal systems
High-resilience messaging
07 · RiskProtection
Antifraud & post-transaction
Pre- and post-transaction prevention
Risk engine and rules by segment
Konduto, ClearSale and Visa Cybersource
Chargebacks, disputes and Visa RDR
IOPAY Automated Verification
08 · RevenueRecurring payments
Subscriptions & retries
Plans and recurring billing
Flexible billing cycles
Subscriber management
Smart retries and fault tolerance
Real-time conversion reports
09 · ChannelsCommerce
Checkout, links & plugins
Transparent checkout
Payment links
Payment buttons
E-commerce plugins
Static websites and landing pages
10 · OperationsBack office
Dashboards & management
Transaction & buyer management
API and credentials
Webhook settings and retrieval
EC Management, EC SSO and Analytics PRO
Conversion, cancellations, refunds and settlements
11 · FinanceReconciliation
Reconciliation & visibility
Reconciliation of transactions, settlements and payouts
Integration with acquirers, banks and receivables registrars
CERC-ready and EDI flows
Messaging and real-time financial visibility
Analytical dashboards and reports
12 · SecurityInfrastructure
Tokenization & security
Vault and secure card reuse
Encryption of sensitive data
Security controls for payments
Segregated environments
PCI-DSS 4.0.1 and a compliance-ready architecture
The availability and configuration of each feature may vary by product, integration, partner and contracted scope.
Platform architecture
Four layers. One operation.
The platform combines financial services, intelligence, integration and experience in a single architecture. The company chooses how much to expose to the customer and how much to keep operating behind its brand.
Interfaces to sell and operate.
Checkouts
Portals
Dashboards
Payment links
Connectivity for your product.
REST APIs
SDKs
E-commerce plugins
Webhooks
Rules that guide the operation.
Compliance & risk engine
Pricing and proposal management
Transactional monitoring
Antifraud
The financial layer behind it.
Gateway, acquiring and payments
Recurring payments
Account manager
Reconciliation
Orchestration
One integration. Many capabilities.
Multi-acquiringConnectivity with multiple payment partners.
RoutingRedundancy and selection logic across processing routes.
ReconciliationTransactions, settlements and payouts tracked in a single view.
SettlementAutomated split, transfers and receivables flows.
From KYC to final operations
Your own journey, with IOPAY technology behind every step.
White-label should preserve the perception of your product while IOPAY technology operates behind the scenes, from onboarding and KYC to payments, events, sellers, split and reconciliation. The goal is to reduce context switching for the customer and complexity for your team.
KYC inside your experience.
Registration, identification and validations can happen under your brand, supported by IOPAY technology.
Payments within the experience.
Connect Pix, cards and boleto to the flows that make sense for your business model.
Participants and rules connected.
When there are multiple recipients, sellers and split can follow the operation's context.
Events to keep everything in sync.
Use webhooks and APIs to reflect status changes in internal systems, ERPs, CRMs and back offices.
Where it makes sense
White-label for businesses where payments are part of the product.
The architecture is especially useful when the financial experience needs to be integrated into the company's software, platform or main commercial relationship.
Payment, participants and distribution in a connected structure.
Own journeys supported by APIs and operational components.
Connect billing and events to the routine the customer already uses.
Preserve IDs, participants and financial rules throughout the flow.
Use the infrastructure as the foundation for journeys that require greater product control.
Build payment experiences flawlessly
From merchant onboarding to reconciliation.
From merchant onboarding to reconciliation.
The entire architecture is integrated and runs on the same processes
Behind the white-label experience, the operation can coordinate onboarding, capture channels, integrations, participants, financial rules and post-transaction on the same technology base, from customer entry to reconciliation.
KYCOnboarding, identification and validationEntry
PaymentsPix, cards and boletoCore
Digital channelsPlugins, checkout and payment linksCommerce
PortalsOperational portals and query journeysPortal
In-personCard terminals and NFCPOS
CorporateCorporate cards and spend managementExpense
IntegrationREST API & webhooksTech
ParticipantsSellers & recipientsContext
DistributionSplit, transfers and financial rulesRules
FinanceReconciliation, settlement and trackingOperation
For developers
Build amazing experiences, payment journeys and products.
Use APIs, webhooks and test environments to connect payments and events to your product's architecture and expand what's possible with Iopay technology
REST APIs
Webhooks
Sandbox
SDKs
Credentials
Integration example
API-first
// crie uma transação no seu fluxo POST /v2/transactions { "amount": 42890, "method": "pix", "reference_id": "pedido_8842" } // mantenha sua aplicação sincronizada payment.approved → webhook
IOPAY Content
Less development.
Less development.
More ready-made product.
Four reads for those who want to put payments under their own brand without turning the implementation into a long infrastructure project.
Ready to use
Payment link: start charging without an online store
A simple way to create digital charges, share them with the customer and track payment without building a new journey from scratch.
Read article↗
Brand & governance
Local sales without losing identity and central control
How networks can distribute operations across units and sellers while preserving brand identity, attribution, reconciliation and governance.
Read article↗
Abstracted infrastructure
A payments layer so you don't rebuild everything with every new need
See how a single layer can concentrate checkout, tokenization, payment methods, routing and reconciliation without spreading complexity across the product.
Read article↗
Less operational effort
How to choose a payments partner beyond the rate
An executive view on ease of deployment, support, security, reconciliation and the ability to grow without unnecessarily increasing internal effort.
Read article↗
Bring KYC, payments and operations inside
your brand effortlessly.
Talk to the IOPAY team to structure a white-label experience aligned with your product, architecture and operating model, from onboarding to final operations.