Payment LinksUncodified copper
IOPAY Platform
One platform to accept, process and manage payments.
Centralize sales channels, transactions, receivables, sellers, integrations and financial context into a single operational layer — by connecting payment to the company's routine.
The portal IOPAYFuture balanceR$ 288.612
Approval60,4%
TPVR$ 2,58M
Consolidated vision
A common layer for channels, operations and finance.
The IOPAY Platform brings together different products and journeys in a single management experience. The aim is to reduce fragmentation between who sells, who integrates, who follows the operation and who needs to reconcile or anticipate receipts.
Acceptance
Payments on different channels.
Orchestrate digital and in-person payments within the same infrastructure.
- Pix, card and boleto
- Checkout, links and payment buttons
- Plugins for e-commerce and payment terminals
Operations
Transactional visibility.
Check out what happened with each payment without relying on multiple systems.
- Status, method, customer and value
- Approval and chargeback indicators
- Reports and operational context
Finance
Receivables and reconciliation.
Connect sales, receipts and settlement schedules for a more consistent reading of the box.
- Current and future balance
- Calendar of receipts
- Conciliation and monitoring of the payment split
Platforms
Sellers, split and marketplaces.
Structure operations with multiple receivers while maintaining centralized governance.
- Register and manage sellers
- The following rules shall apply:
- Consolidated view of the platform
Technology
APIs, credentials and webhooks.
Product and operation remain connected to the technical layer used by your team.
- Credentials and Seller ID
- REST APIs, webhooks and sandbox
- Documentation and Central Developer
Management of the
A bill to evolve the operation.
Start with a specific need and expand the use of infrastructure as the business grows.
- New channels and products
- Expense management & corporate cards
- White-label and customized operations
The portal IOPAY
A central infrastructure.
A central infrastructure.
Multiple connected flows.
Sell through different channels and track operations, finance and technology in one layer. Move the mouse through the ecosystem to explore the flows.
How You Sell
APIs & Customized integrationsFor your tech team
Payment buttonembed into any website
Payment terminalsIO PRO and IO Pocket · in person
E-commerceOfficial and free plugins
The portal IOPAYminhaconta.iopay.com.br
How You Work
Real-time reconciliationEach sale comes to its financial context
Transaction and extract reportsconsult, filter and export your operation
Full dashboardsa consolidated reading of the operation
Conversion Reportsapproval, refusal and transaction performance
Advanced settingsPayment Split, withdrawals and operation rules
Webhooks & Payment Splitevents and automations on the same portal
Operational day
From payment to settlement, each step remains connected.
The IOPAY Platform organises the operational cycle for product, service, finance and technology to work in the same context.
01CapturePayment is made at the checkout, link, button, API, plugin or in person channel.
02ProcessingThe transaction shall follow the appropriate flow to the payment instrument and to the authorised partners.
03Status of theApproved, pending, failed, cancelled or disputed shall constitute the transactional view.
04EventsWebhooks and updates allow external systems to keep track of the payment cycle.
05ReceivableThe sale shall be entered in the financial calendar according to the applicable time and manner.
06settlementReceives, Payment Split and reconciliation close the operational cycle.
Operations and finance
Executive context without losing the detail.
The portal connects consolidated indicators to the view of each transaction, enabling performance monitoring and investigation of specific events in the same environment.
01
The following table summarizes the results of the calculations:Balance, TPV, approval, chargeback and relevant indicators of the operation.
02
TransactionsCheck by ID, client, document, method, status and period.
03
ReceivablesCalendar of receipts and reading of the future balance of the operation.
04
ReconciliationConnect what's been sold to what needs to be received, distributed via Payment Split or reconciled.
The portal IOPAY
An interface to the operational routine.
A visual example of the consolidated reading the platform offers for different areas of the company.
Vision of the operationSeptember / 2026
TPVR$ 2,58M
Approval60,4%
Future balanceR$ 288k
TransactionMethodStatus of theAmount
#8f71...2c90CardApprovedR$ 4.078
#44d2...9044PixOtherR$ 3.482
#a732…2421CardApprovedR$ 2.545
Marketplaces & platforms
Governance for operations with multiple sellers and recipients.
When the business model involves sellers, partners or different financial participants, the platform extends the individual view of the transaction to a structured management of the transaction.
Sellers and Payment Split at the center of the operation.
Organize the relationship between platform, seller and payment without losing the context of who sold, how much to receive and how the value should be distributed.
01
Seller IDconsistent identification of participants within the operational and technical flows.
02
Payment SplitDistribution according to the rules defined for the transaction or business model.
03
Payment SplitMore clarity to track the distribution of values between sellers and partners.
04
Conciliation by participantOperational context to identify the origin, destination and financial situation of each flow.
White-label and personal experiments.
For digital products, marketplaces and platforms that need to maintain their own brand and experience, IOPAY infrastructure can act as the technological layer behind the journey.
01
Your mark on the frontCommercial and product experience aligned with customer identity.
02
IOPAY in the infrastructureAPIs, processing, sellers, Payment Split and operational management integrated into the product.
03
Customized architecturesMore complex models can combine different platform features.
Technology
The platform is also a layer of integration.
The operational vision shall be consistent with the credentials, APIs, webhooks and documentation. This reduces the distance between what the technical team implements and what the operation needs to follow after the payment goes into production.
Credentials
Environment and identifiers.
Centralize data needed to integrate apps and sellers.
- Seller ID and credentials
- Segregated environments
- Management of the integration cycle
Events
Webhooks and automation.
Update orders, internal products and financial routines as the transaction events.
- The following is the list of transactions:
- Integration with ERP, CRM or fulfillment
- Event-oriented operation
Central developer
Documentation and technical reference.
It takes the developer from the initial configuration to the production operation with more context.
- Technical documentation
- API Reference
- Sandbox and integration support
Business models
A platform that follows different operations.
The same technological base can be used by companies with different needs without requiring the operating home to be fragmented into various suppliers and systems.
E-commerce
Online sales with operational vision.
Checkout, plugins, links, APIs, receivers and reconciliation connected to the same account.
Knowing e-commerce →Marketplace
Seller management and payment split.
Estruture Payment Split, Sellers, Integrations and Financial Monitoring in a Single Infrastructure
Knowing marketplaces →Enterprise
Customized operations.
Combine channels, APIs, white label and operational flows according to the business design.
Knowing white-label →Commercial
Charges outside the checkout.
Links and payment buttons for inside sales, service, campaigns and assisted sales.
Know the links →Omnichannel
Digital and face-to-face connected.
Combine online and machine payments while maintaining a more integrated reading of the transaction.
Meet the little girlsCorporate management
Payments and expenses in the same ecosystem.
Extend the relationship with IOPAY to corporate cards, policies for use and expenditure management.
Knowledge of expenditure management →Security & control
Controls incorporated into the infrastructure.
Security, tokenization, anti-fraud and traceability are part of the platform's operational architecture and support the ongoing monitoring of payment flows.
01PCI DSS 4.0.1
Technical and operational controls applied to the payment environment.
02Tokenization
Reduction of exposure to sensitive data throughout transactional periods.
03Fraud prevention
Risk analysis integrated with authorisation flows according to the configuration of the operation.
04Observability
Status, events, webhooks and operational context for monitoring and response.
The availability of resources, means of payment and functionalities may vary according to product, partner, registration analysis and business configuration.
IOPAY Platform
Centralize payments, operations and finance into a single infrastructure.
Open your account or talk to our team to structure the products and integrations that best fit your business model.