Paytime

Paytime: Omnichannel Payments And White-Label Fintech Infrastructure For Brazil

Paytime is a Brazilian payments and financial technology provider that combines acquiring (payment acceptance) with digital-account capabilities.

Paytime Overview

Paytime operates in two main fronts: acquiring and a digital account, with an omnichannel approach covering in-person and online contexts. The product concept emphasizes a unified operational view through a portal and mobile app, plus optional branding paths that can extend to terminals and the app experience.

Paytime also runs a partner-focused model that enables third parties to launch a branded payments experience. This matters to merchants because pricing, onboarding flow, and account ownership may differ when you are onboarded through a Paytime partner versus a direct commercial relationship.

Paytime Payment Acceptance Options

In-Person Payments With POS Terminals

For face-to-face acceptance, Paytime supports POS hardware models, including SmartPOS devices. One documented SmartPOS option is the PAX A960, which supports:

• Contactless (NFC)
• QR Code payments
• Chip (EMV)
• Magnetic stripe
• Merchant receipt printing (built-in printer)

The A960 is described as PCI PTS 6.x certified, which is relevant for merchants that want clarity on terminal security posture and certification scope.

Online Payments And Remote Collection

For online or remote collection, Paytime’s ecosystem includes payments via Pix, cards, and boleto, and supports flows that can be embedded into partner experiences via APIs. If your use case involves collecting from customers without a staffed checkout counter, Paytime’s tooling is positioned to support “cobrança” (collections) patterns such as payment requests and Pix QR codes, plus boleto issuance.

Payment Methods Supported

Across Paytime’s positioning and its integration documentation, the payment methods that are explicitly supported include:

• Cards (including credit-card transaction creation through APIs)
• Pix (including Pix QR code transaction creation)
• Boleto (including boleto issuance and management)

For merchants operating primarily in Brazil, these rails cover a large share of day-to-day payment needs, especially when you combine in-store acceptance with Pix QR codes for flexible customer-present and customer-not-present scenarios.

Checkout And Billing Workflows

Paytime supports multiple merchant-facing collection workflows, including:

• QR Code payments (notably Pix QR codes)
• Payment links (as part of “Cobranças” in Paytime’s support materials)
• Boleto issuance and boleto management

For platforms (marketplaces, franchisors, or SaaS providers) that need more structured funds flow, Paytime’s API documentation includes split-payment concepts and endpoints, which can be relevant when you need to route proceeds to multiple recipients in one transaction or apply fee logic at the platform level.

Platform Capabilities For Merchants And Partners

Paytime’s documented capabilities go beyond a basic “take card payments” setup and include operational and platform features such as:

• A web portal and mobile app model for managing the business
• Transaction visibility and reporting in the portal
• Dispute and chargeback management functions surfaced as portal capabilities
• Banking-related operations such as transfers via Pix and TED (noted as portal functions)

If you are a platform or partner embedding Paytime, the Paytime API stack is positioned to provide a broader toolkit: payment creation, Pix QR codes, split rules, antifraud hooks, and event-driven integration via webhooks.

Developer Integrations And API Capabilities

Paytime documents an API ecosystem intended for partner integrations. The available scope described in Paytime’s API documentation includes:

• Payments APIs for card, Pix, and boleto
• Card tokenization
• Split payments (including split rules and split operations)
• Antifraud support (including references to session-related antifraud handling)
• 3DS support (with 3DS documentation and implementation paths)
• Webhooks for real-time event notifications
• Banking endpoints for balance, statement, and transfers
• Merchant onboarding and management via API (establishment creation and gateway activation flows)

A practical implication for merchants is that Paytime can support “standard” usage through portals and POS, but it can also be embedded into a broader customer journey if your business runs a platform, app, or commerce stack that needs programmatic control.

Reporting, Reconciliation, And Operations

Operational tooling is a key differentiator for merchants that care about reconciliation, fee transparency, and payout planning.

Paytime’s portal capabilities are described to include:

• Transaction history and sales management
• Real-time reporting, including total revenue, average ticket, fees paid, and net amounts
• A calendar-style view of future receivables (lançamentos futuros)
• Anticipation features (requesting an advance on future balances)
• Dispute and chargeback management
• Support request tracking through a portal module (“Solicitações”)

Onboarding And Support

Onboarding timelines depend on whether you are being onboarded as a merchant user or as a partner building a branded solution. For partner-style deployments, Paytime describes a timeline of up to 30 days after payment of an onboarding fee and submission of required information for delivery of a fintech setup.

For merchant onboarding and account validation steps, Paytime’s support documentation describes internal review stages and service levels for document validation and platform approvals. In practice, merchants should expect that account activation can include:

• Submission of required documents and validation checks
• Risk analysis steps (with the possibility of additional review)
• Platform approvals for specific products/modules depending on the setup

Compliance And Security Considerations

Paytime’s materials surface several compliance and security signals that may matter in procurement and risk reviews:

• ISO 9001 is referenced via a certification badge (QMS certification) on Paytime’s site
• A SmartPOS device option (PAX A960) is described as PCI PTS 6.x certified
• Paytime’s API documentation includes 3DS support pathways and antifraud-related integration concepts
• Paytime provides a dedicated LGPD contact channel (DPO email) for privacy-related communications

Who Paytime Is Best For

Paytime tends to fit best when you need one or more of the following:

• A Brazil-focused stack that supports Pix, boleto, and card payments
• Omnichannel acceptance across in-store and online contexts
• Portal-based operational management with reporting, disputes, and payout planning
• A partner or platform model where you want to embed payments and potentially run split payments
• API-driven integration needs, including webhooks and tokenization

Conclusion

Paytime combines acquiring and digital-account capabilities into an omnichannel payments proposition built for Brazil, with explicit support for Pix, boleto, and card flows. For merchants, the practical value is centered on in-store acceptance (including SmartPOS options), operational tooling through a portal and app, and support structures for disputes and day-to-day transaction management. For platforms and partners, Paytime’s API surface area expands the offering into embedded payments, with documented support for tokenization, split payments, 3DS, antifraud integration concepts, and webhooks.