Onboarding and KYC are already starting within your brand.
Cadastre, identification and validation can happen in your experience, with IOPAY technology working behind the scenes on a white-label model.
KYCOnboardingWhite-label
White-label
Your brand comes first. From KYC to daily operations
Build your own onboarding, KYC, payment and trading journeys without starting 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 mark.
A single experience for different points of contact.
Checkouts
Links
Platforms
Other vehicles
Sellers
White label IOPAY
A full operation.It's a totally your experience.
White-label doesn't have to mean rebuilding onboarding, KYC, payments, sellers, rules and financial operations. The same basis can be incorporated into your product and evolve as the complexity grows.
01 · KYC
The journey goes from register to payment without any change of context.
From the customer's input to the confirmation of the charge, the experience can remain aligned with their interface, rules and business flow.
Own UXContinuous flowThe conversion
Financial logic remains configurable and fully transparent.
Sellers, split, rollover and reconciliation may follow the original context of the operation rather than being born in parallel controls.
SellersSplitReconciliation
The same basis accompanies growth.
Start with an objective journey and integrate as new products, channels, participants and rules enter into operation.
ScaleNew channelsMore automation
01
KYC & onboardingRegister and validate within your trademark.
↗02
ExperienceThe business journey shall remain continuous until payment.
↗03
OperationsPayments, sellers, split, events and settlement.
↗04
ScaleThe same basis follows new products, channels and operations.
↗
Platform Resources
Way beyond the checkout.
KYC & KYB
Orchestra
Multi-purchase
Payments
Accounting & settlement
APIs & webhooks
Risk and anti-fraud
Recurrence
The following is the list of the following:
Reconciliation
The white label can be used to track the entire operational journey: customer entry and validation, payment capture, financial rules, seller management, automation, post-transaction and financial vision.
01 · EntryOnboarding
Compliance, KYC & KYB
Pre-registration of establishments
Validation of person and company
Approval and rejection flows
Internal Risk Score
Consultations and compliance checks
02 · CapturePayment core
Payments & transaction cycle
Pix, card and boleto
Multi-acquisition and orchestration
Smart routing and redundancy
Authorisation, pre-authorisation and capture
Tokenization, one-click buy and zero-dollar check
Cancellations and withdrawals
03 · MarketplacesMulti-party
Sellers, split & distribution
Sellers and receivers management
Split by transaction
Payment Split and transfers
Accounts and balances per participant
Events and movements consultations
04 · FinancialMerchant OS
Accounting, receivables & settlement
Balances, future schedule and receivables
The financial calendar
The amount of the adjustment shall be reported in the following table:
Excerpts, ledger, consultations and reports
Input, output, transfers and payouts
05 · DeveloperAPI-first
APIs, SDKs & sandbox
REST APIs
Interactive documentation
Insulated test and sandbox environments
The following table shows the following:
SDKs: Laravel, PHP, JavaScript, NodeJS, Java and Python
Authentication, credentials and customized integrations
06 · EventsAutomation
Webhooks & messaging
Configurable callbacks
Real-time events
Automatic retention
Integration with internal systems
High resilience messaging
07 · RiskProtection
Anti-fraud and post-transaction
Pre- and post-transaction prevention
Risk engine and rules by segment
Konduto, ClearSale e Visa Cybersource
Chargeback, disputes and RDR Visa
IOPAY Automated Verification
08 · RevenueRecurrence
Signatures and withdrawals
Recurring plans and charges
Flexible charging cycles
Subscriber management
Smart retention and failure tolerance
Real-time conversion reports
09 · CanalsTrade
Checkout, links & plugins
Transparent checkout
Payment links
Payment buttons
E-commerce plugins
Static sites and landing pages
10 · OperationBackoffice
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 · FinancialReconciliation
Conciliation & visibility
Conciliation of transactions, settlements and payouts
Integration with acquirers, banks and registrars
CERC-ready and EDI flows
Real-time financial messaging and vision
Analytical dashboards and reports
12 · SecurityInfrastructure
Tokenization & security
Vault and safe reuse of cards
Encryption of sensitive data
Security checks for payments
Segregated environments
PCI-DSS 4.0.1 and compliance-ready architecture
The availability and configuration of each resource may vary according to the product, integration, partner and scope of the contract.
Platform architecture
Four layers. One operation.
The platform combines financial services, intelligence, integration and experience in a unique architecture. The company chooses how much exposure it wants to expose the customer and how much it prefers to keep operating behind its brand.
Interfaces to sell and operate.
Checkouts
Other vehicles
Other equipment
Payment links
Connectivity to your product.
REST APIs
SDKs
E-commerce plugins
Webhooks
Rules that guide the operation.
Compliance & risk engine
Pricing and proposal management
Transactional monitoring
Fraud prevention
The financial layer behind it.
Gateway, acquisition and payments
Recurrence
Account manager
Reconciliation
Orchestra
It's an integration. Various capabilities.
Multi-purchaseConnectivity with multiple payment partners.
RoutingRedundancy and logic of choice between processing routes.
ReconciliationTransactions, settlements and payouts accompanied in a single view.
settlementSplit, automatic transfers and flows of receivables.
From KYC to final operation
A journey of its own, with IOPAY technology behind it at every step.
The white label should preserve your product perception while IOPAY technology operates from the back from onboarding and KYC to payments, events, sellers, split and reconciliation. The aim is to reduce context for the client and complexity for his team.
KYC within your experience.
Cadastre, identification and validation may take place under your mark, supported by IOPAY technology.
Payments within the experiment.
Connect Pix, card and boleto to the flows that make sense to your business model.
Participants and rules connected.
When there are multiple receivers, sellers and split can follow the context of the transaction.
Events to keep everything in sync.
Use webhooks and APIs to reflect status changes in internal systems, ERPs, CRMs and back-office.
Where it makes sense
White-label for businesses where payments are part of the product.
The architecture is especially useful when financial experience needs to be integrated into the software, platform or core business relationship of the company.
Payment, participants and distribution in a connected structure.
Own joints supported by APIs and operational components.
Connect billing and events to the routine the customer has already used.
Preserve IDs, participants and financial rules throughout the flow.
Use infrastructure as a basis for journeys that require greater product control.
Build payment experiences with perfection
From accreditation to reconciliation.
From accreditation to reconciliation.
The whole architecture is integrated and operates under the same processes
Behind the white label experience, the operation can coordinate onboarding, capture channels, integrations, participants, financial rules and post-transaction on a single technological basis, from customer input to reconciliation.
KYCOnboarding, identification and validationEntry
PaymentsPix, cards and boletoCore
Digital channelsPlugins, checkout and payment linksTrade
Other vehiclesOperational portals and consultation roundsThe portal
In personMachinery and NFCsPOS
CorporateCorporate cards and expenditure managementExpenditure
IntegrationREST API & webhooksTech
ParticipantsSellers & receiversThe context
DistributionSplit, transfers and financial rulesRules
FinanceConciliation, settlement and follow-upOperations
For developers
Build I'm not sure what I'm saying.
Use APIs, webhooks and test environments to connect payments and events to your product architecture and leverage the possibilities with Iopay technology
REST APIs
Webhooks
Sandbox
SDKs
Credentials
Example of integration
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
Content of the IOPAY
Less development.
Less development.
More product ready.
Four readings for anyone looking to put payments under their own brand without turning implementation into a long infrastructure project.
Ready to use
Payment link: start charging without relying on the virtual store
A simple way to create digital invoices, share with the customer and track payment without building a new journey from scratch.
Read the article↗
Brand & governance
Local sales without loss of identity and central control
As networks they can distribute the operation between units and sellers while preserving brand identity, attribution, reconciliation and governance.
Read the article↗
Abstract infrastructure
A layer of payments to not rebuild everything to every new need
Understand how a single layer can concentrate checkout, tokenization, means of payment, routing and reconciliation without spreading complexity across the product.
Read the article↗
Reduced operational effort
How to choose a payment partner beyond the fee
An executive vision of simplicity of deployment, support, security, reconciliation and the ability to grow without unnecessarily increasing internal effort.
Read the article↗
Take KYC, payments and operation into the
your effortless brand.
Talk to the IOPAY team to structure a white label experience aligned with your product, architecture and operating model, from onboarding to final operation.