Overview

Boleto.Cloud provides an API-first platform for managing financial transactions within the Brazilian market, focusing on local payment methods. Established in 2014, the service streamlines the issuance and management of Boleto Bancário, a widely used offline payment method in Brazil. Additionally, it supports Pix, Brazil's instant payment system, enabling real-time transactions.

The platform is designed for developers and businesses requiring integration with Brazilian payment infrastructure without handling the underlying complexities of banking protocols directly. Its core offerings include the issuance of Boleto Bancário, processing of Pix payments, generation of payment links for various scenarios, and a robust system for managing recurring payments and subscriptions. This makes it suitable for e-commerce, SaaS businesses, and service providers operating in Brazil who need to automate their billing and collection processes.

Boleto.Cloud's API is RESTful, leveraging JSON for data exchange, which aligns with common web service integration practices. The service provides comprehensive documentation and SDKs for popular programming languages such as PHP, Node.js, Python, Java, Ruby, and .NET. This range of SDKs aims to reduce development effort and accelerate integration timelines for various technology stacks.

The service also emphasizes compliance with Brazilian data protection regulations, specifically the Lei Geral de Proteção de Dados (LGPD). This focus on local compliance is critical for businesses handling personal data and financial transactions in Brazil. By abstracting these regulatory requirements, Boleto.Cloud aims to allow businesses to concentrate on their core operations while maintaining adherence to local legal frameworks. The availability of a free plan for testing and limited usage allows developers to explore the API's capabilities before committing to a paid tier.

Key features

  • Boleto Bancário Issuance: Programmatic creation and management of Boleto Bancário payment slips, including registration, updates, and cancellations.
  • Pix Payment Processing: Facilitates the generation of Pix QR Codes and dynamic Pix charges, supporting real-time payment notifications and reconciliation.
  • Payment Links: Creation of shareable payment links that can incorporate multiple payment methods (Boleto, Pix) for simplified collections.
  • Subscription Management: Tools for managing recurring payments, including automated billing cycles, grace periods, and subscription status tracking for services.
  • Webhooks and Notifications: Provides webhook functionality to notify integrated systems of payment status changes, such as successful payments or cancellations.
  • API for Collections: A dedicated API for managing collection processes, including payment reminders and delinquency handling.
  • Reporting and Analytics: Access to dashboards and reporting features for monitoring transaction volumes, payment statuses, and financial reconciliation.

Pricing

Boleto.Cloud offers a tiered pricing model that includes a free plan for initial testing and limited usage. Paid plans are structured around a monthly fee plus per-transaction charges, with variations based on the volume of Boletos issued and specific features required. The following table outlines the general pricing structure as of 2026-05-28.

Plan Monthly Fee Included Boletos Additional Boleto Fee Pix Fee (per transaction) Key Features
Free R$ 0 10 R$ 2.50 R$ 0.99 API access, test environment, basic reporting
Básico R$ 29.90 50 R$ 1.99 R$ 0.99 All Free features, production environment, basic support
Pro R$ 99.90 250 R$ 1.50 R$ 0.99 All Básico features, advanced reporting, priority support
Enterprise Custom Custom Custom Custom All Pro features, dedicated account manager, custom integrations

For detailed and up-to-date pricing information, including specific features per plan and potential volume discounts, refer to the official Boleto.Cloud pricing page.

Common integrations

Boleto.Cloud is designed to integrate with various business systems through its API and SDKs. Common integration scenarios include:

  • E-commerce Platforms: Integrating payment processing into online stores to accept Boleto Bancário and Pix payments directly at checkout.
  • ERP/CRM Systems: Connecting with enterprise resource planning or customer relationship management platforms to automate billing, invoicing, and payment reconciliation.
  • Subscription Management Platforms: Utilizing Boleto.Cloud's recurring payment features to manage subscriptions and recurring billing for SaaS products or service providers.
  • Financial Management Software: Integrating with accounting software to track incoming payments, reconcile transactions, and generate financial reports.
  • Mobile Applications: Embedding payment functionality within native mobile applications for in-app purchases or service payments.

Alternatives

For businesses seeking alternatives to Boleto.Cloud for Brazilian payment processing, several other providers offer similar services:

  • Gerencianet: Offers a range of payment solutions including Boleto Bancário, Pix, and credit card processing, with a focus on digital accounts.
  • Pagar.me: A payment gateway providing solutions for credit cards, Boleto, and Pix, often used by larger e-commerce operations in Brazil.
  • MundiPagg: Specializes in payment processing for high-volume businesses, offering multi-acquirer and anti-fraud solutions alongside Boleto and Pix.
  • Stripe: While not exclusively focused on Brazil, Stripe's global platform offers localized payment methods, including Pix, for businesses operating internationally.

Getting started

To begin integrating with Boleto.Cloud, developers typically sign up for an account, obtain API credentials (Client ID and Client Secret), and then use one of the available SDKs or make direct HTTP requests to the REST API. The following Node.js example demonstrates how to create a simple Boleto Bancário using the Boleto.Cloud API.


const axios = require('axios');

// Replace with your actual credentials
const CLIENT_ID = 'YOUR_CLIENT_ID';
const CLIENT_SECRET = 'YOUR_CLIENT_SECRET';

const BASE_URL = 'https://api.boleto.cloud';

async function createBoleto() {
  try {
    // Step 1: Obtain an access token
    const tokenResponse = await axios.post(`${BASE_URL}/oauth/token`, {
      grant_type: 'client_credentials',
      client_id: CLIENT_ID,
      client_secret: CLIENT_SECRET,
    });
    const accessToken = tokenResponse.data.access_token;

    // Step 2: Define Boleto data
    const boletoData = {
      beneficiary_name: 'Minha Empresa S.A.',
      beneficiary_document: '12.345.678/0001-90',
      payer_name: 'Cliente Exemplo',
      payer_document: '999.888.777-66',
      payer_zipcode: '01000-000',
      payer_address: 'Rua Exemplo, 123',
      payer_city: 'São Paulo',
      payer_state: 'SP',
      amount: 100.00, // R$ 100.00
      due_date: '2026-06-30',
      description: 'Pagamento de Serviço X',
      instructions: 'Não receber após o vencimento.',
      // Additional fields can be added as per API documentation
    };

    // Step 3: Create the Boleto
    const boletoResponse = await axios.post(`${BASE_URL}/v1/boletos`, boletoData, {
      headers: {
        'Authorization': `Bearer ${accessToken}`,
        'Content-Type': 'application/json',
      },
    });

    console.log('Boleto created successfully:');
    console.log('Boleto ID:', boletoResponse.data.id);
    console.log('Boleto URL:', boletoResponse.data.url);
    console.log('Boleto Barcode:', boletoResponse.data.barcode);

  } catch (error) {
    console.error('Error creating boleto:', error.response ? error.response.data : error.message);
  }
}

createBoleto();

This example first authenticates to obtain an access token, then constructs a JSON payload with the necessary Boleto information, and finally sends a POST request to the Boleto creation endpoint. The response typically includes the Boleto's ID, URL for viewing/printing, and the barcode for payment. Developers should refer to the Boleto.Cloud API reference for complete details on all available endpoints and parameters.