WhatsApp Pix Integration in Brazil 2026: How to Accept Pix Payments Inside WhatsApp Conversations

Pix accounts for over 40% of digital payments in Brazil and more than 90% of P2P transfers. For Brazilian businesses operating on WhatsApp, integrating Pix directly into the conversation eliminates the single biggest friction point in conversational commerce: the redirect to a website or banking app to complete payment. With native Pix integration through a Brazilian BSP, customers pay inside WhatsApp via QR code or copy-paste code, confirmation arrives automatically via PSP webhook, and the post-purchase flow continues in the same conversation. This guide walks through the architecture, the seven Brazilian PSP integrations, the developer flow, the LGPD considerations, and the conversion math. For the full platform, see our WhatsApp Business API in Brazil page.

Quick Answer: How Does WhatsApp Pix Integration Work in Brazil?

When a Brazilian customer expresses purchase intent inside a WhatsApp Business conversation, the platform integrated with a Brazilian PSP generates a Pix charge inside the conversation as a QR code and copy-paste Pix code. The customer opens their banking app, pays via Pix, and the PSP webhook confirms payment to your backend within seconds. The same WhatsApp conversation continues with order confirmation, NF-e delivery, shipping update, and support. No redirect to a website. No separate checkout page. Conversion vs traditional redirect checkout lifts 2-3x. Supports PagSeguro, Mercado Pago, Stripe BR, Asaas, Iugu, Pagar.me, and Stark Bank natively through Message Central. See the WhatsApp Business API in Brazil platform for full integration.

Why Native Pix in WhatsApp Matters for Brazilian Businesses

Three reasons Pix-in-WhatsApp is the single most important conversion lever for Brazilian conversational commerce in 2026:

1. Eliminates the redirect-to-website friction. Traditional e-commerce checkout requires the customer to leave the conversation, navigate to a website, log in, enter address, choose payment method, and complete the transaction. Each step loses 5-15% of intent. Pix-in-WhatsApp collapses all of that into one tap on a QR code inside the conversation. Conversion lift vs redirect checkout: 2-3x.

2. Aligns with Brazilian payment behavior. Pix is the dominant Brazilian digital payment method (>40% of digital payments per BACEN Pix data). Asking a customer to checkout with credit card when they prefer Pix increases abandonment. WhatsApp Pix integration lets you accept the customer's preferred payment method in the channel they already use.

3. Closes the abandoned cart loop instantly. When you send an abandoned cart recovery message via WhatsApp and the customer wants to complete the purchase, you can serve a Pix charge inside the same conversation. Combined cart recovery + Pix-in-WhatsApp flow recovers 18-28% of abandoned carts in Brazilian e-commerce vs 4-7% via email. See our WhatsApp abandoned cart recovery guide.

The Seven Brazilian PSPs Supported for WhatsApp Pix Integration

VerifyNow and WhatsApp Business API integrations through Message Central support seven major Brazilian payment service providers (PSPs) for Pix charge generation and webhook confirmation. Each has different strengths:

PagSeguro UOL

One of the largest Brazilian PSPs by volume. Native Pix support with QR code generation, copy-paste code, instant confirmation webhook. Best fit for mid-market e-commerce and retail. PagSeguro Pix API documentation.

Mercado Pago

The PSP arm of Mercado Livre, Brazil's largest e-commerce platform. Native Pix support with rich webhook telemetry. Best fit for businesses already on the Mercado Livre ecosystem.

Stripe BR

Stripe's Brazilian operation with full Pix support. Best fit for businesses already on Stripe globally that want one PSP across markets.

Asaas

Brazilian PSP focused on SMB and SaaS recurring billing. Native Pix support with subscription billing capability. Best fit for SaaS, education, and recurring-payment businesses.

Iugu

Brazilian PSP with strong split-payment capability. Native Pix support. Best fit for marketplaces and platforms that need to split a single Pix payment across multiple receivers.

Pagar.me

Stone's PSP operation. Native Pix support with enterprise-grade SLA. Best fit for high-volume Brazilian e-commerce.

Stark Bank

Brazilian banking-as-a-service platform with native Pix support. Best fit for fintechs that need both PSP capability and banking primitives.

The Pix-in-WhatsApp Conversation Flow

A typical Brazilian e-commerce conversation flow with Pix integration:

Step 1 — Customer expresses purchase intent. Could be inbound (customer messages first), abandoned cart recovery (your campaign reaches them), Click-to-WhatsApp Ads (they clicked an Instagram or Facebook ad), or in-conversation upsell.

Step 2 — Bot or agent qualifies the order. Confirms product, size/variant, delivery address, total amount. This is conversational. The customer can ask questions, request photos, change their mind.

Step 3 — System triggers Pix charge generation. Your backend calls the BSP API with order details. BSP calls the PSP API. PSP returns a Pix BR Code (the copy-paste string) and a QR code image.

Step 4 — WhatsApp message with Pix BR Code and QR is delivered. Customer sees the QR code (can be scanned with their phone camera) and the copy-paste code (can be pasted into their banking app).

Step 5 — Customer pays via their banking app. Opens Nubank, Inter, Itaú, Bradesco, or any Pix-enabled banking app, pastes the code or scans the QR, confirms payment. Pix settles instantly.

Step 6 — PSP webhook fires payment confirmation. Your backend receives a signed webhook within seconds of Pix settlement.

Step 7 — Post-purchase flow continues in the same WhatsApp conversation. Order confirmation, NF-e delivery, tracking code, follow-up support — all in the same conversation. The customer never leaves WhatsApp.

Code Example: Generate a Pix Charge via Message Central API (Node.js)

const axios = require('axios');

const generatePixChargeInWhatsApp = async (customerPhone, amount, description) => {
  // 1. Generate Pix charge through the BSP-PSP integration
  const pixResponse = await axios.post(
    'https://api.messagecentral.com/whatsapp/v1/pix/charge',
    {
      to: customerPhone,
      amount: amount,           // amount in centavos: 24990 = R$249.90
      currency: 'BRL',
      description: description,
      expiration_seconds: 600,  // 10-minute Pix code expiry
      psp: 'mercado_pago'       // or pagseguro, stripe_br, asaas, iugu, pagarme, stark_bank
    },
    {
      headers: {
        'Authorization': 'Bearer YOUR_API_KEY',
        'Content-Type': 'application/json'
      }
    }
  );

  // 2. The BSP automatically sends the Pix QR + copy-paste code
  //    inside the WhatsApp conversation
  return pixResponse.data;
  // Returns: { charge_id, br_code, qr_code_url, expires_at }
};

// Example: generate R$249.90 Pix charge
generatePixChargeInWhatsApp(
  '5511999999999',
  24990,
  'Pedido #PEDIDO12345 - Camiseta Azul M'
);

Code Example: Webhook Handler for Pix Payment Confirmation (Python)

from flask import Flask, request, jsonify
import hmac
import hashlib

app = Flask(__name__)
WEBHOOK_SECRET = 'YOUR_WEBHOOK_SECRET'

@app.route('/webhook/pix-confirmation', methods=['POST'])
def pix_webhook():
    # 1. Verify webhook signature
    signature = request.headers.get('X-Signature')
    payload = request.get_data()
    expected = hmac.new(
        WEBHOOK_SECRET.encode(),
        payload,
        hashlib.sha256
    ).hexdigest()
    if not hmac.compare_digest(signature, expected):
        return jsonify({'error': 'invalid signature'}), 401

    # 2. Parse event
    event = request.get_json()
    if event['type'] == 'pix.paid':
        charge_id = event['data']['charge_id']
        amount = event['data']['amount']
        customer_phone = event['data']['customer_phone']

        # 3. Trigger post-purchase flow in same WhatsApp conversation
        send_order_confirmation(customer_phone, charge_id)
        generate_and_send_nfe(charge_id)
        schedule_shipping_notification(charge_id)

    return jsonify({'received': True}), 200

LGPD Considerations for Pix-in-WhatsApp

Pix payment confirmations are transactional, which falls under LGPD legal basis of contract execution (Article 7, V) — not consent. This means you do not need separate opt-in to send Pix confirmation messages to a customer who has just paid. However:

• The initial WhatsApp marketing or service message that led to the Pix charge generation must have valid opt-in
• Pix charge generation and confirmation messages should be logged for at least 5 years to meet Brazilian Consumer Defense Code (CDC) limitation period
• NF-e delivery via WhatsApp counts as a tax obligation — retain delivery proof in your audit log

See our LGPD WhatsApp Business compliance guide for the full framework.

Pix Code Expiration and Retry Architecture

Pix BR Codes have an expiration time configurable per charge — typical Brazilian e-commerce uses 10-15 minute expiry. If the customer does not pay within that window:

• The PSP marks the charge as expired
• Your bot or agent can offer a fresh Pix charge in the same conversation (one tap)
• Alternatively, offer credit card checkout if Pix is consistently failing

For abandoned-cart-with-Pix flows, configure the retry sequence at 1 hour (gentle reminder, fresh Pix charge), 24 hours (with 5% discount), 72 hours (with 10% discount). Recovery rates of 18-28% are typical when Pix is the checkout method.

Conversion Impact Benchmarks

Brazilian e-commerce platforms running Pix-in-WhatsApp typically observe:

• Cart recovery rate: 18-28% vs 4-7% on email-only recovery (3-5x improvement)
• Click-to-WhatsApp Ads conversion: 25-45% vs 8-15% on traditional ad-to-landing-page (2-3x improvement)
• Time from conversation to payment: Average 90 seconds vs 5-8 minutes on website checkout
• Pix preference share: 50-70% of customers offered Pix-or-card via WhatsApp choose Pix

Common Implementation Mistakes

Mistake 1: Generating Pix charge without confirming the order details first. Customers click the QR and pay before they realize the address or product is wrong. Fix: bot confirms product, address, and total before triggering charge.

Mistake 2: Pix expiration too short (under 5 minutes). Customer opens the QR but needs to switch banking apps or check balance. Fix: 10-15 minute expiry is the sweet spot.

Mistake 3: Not verifying webhook signatures. Without HMAC verification, your endpoint can be spoofed to fake payment confirmations. Fix: always verify the signature (sample code above).

Mistake 4: Sending NF-e immediately on Pix confirmation without delay. Pix settles in seconds but your fulfillment system may not have written the order yet. Fix: 30-60 second buffer before NF-e generation.

External Authority References

BACEN official Pix portal and specifications. BACEN Pix initiation standards manual. Meta WhatsApp Cloud API documentation. ANPD official portal for LGPD compliance.

Frequently Asked Questions

How does WhatsApp Pix integration work in Brazil?

When a Brazilian customer expresses purchase intent inside a WhatsApp Business conversation, your platform (integrated with a Brazilian PSP via a Meta-authorized BSP like Message Central) generates a Pix charge as a QR code and copy-paste BR Code inside the conversation. The customer pays via their banking app, the PSP webhook confirms payment within seconds, and the same WhatsApp conversation continues with order confirmation, NF-e delivery, and shipping updates.

Which Brazilian PSPs support Pix in WhatsApp via Message Central?

Message Central's WhatsApp Business API in Brazil supports seven Brazilian PSPs for native Pix integration: PagSeguro, Mercado Pago, Stripe BR, Asaas, Iugu, Pagar.me, and Stark Bank. Each is integrated with full Pix charge generation, QR code rendering inside WhatsApp, copy-paste BR Code, and webhook payment confirmation.

What is the conversion lift from Pix-in-WhatsApp vs traditional website checkout in Brazil?

Brazilian e-commerce platforms typically observe 2-3x conversion lift when accepting Pix inside the WhatsApp conversation vs redirecting to a website checkout. Click-to-WhatsApp Ads conversion lifts from 8-15% to 25-45%. Cart recovery rate lifts from 4-7% (email only) to 18-28% (WhatsApp with Pix). Time from conversation to payment drops from 5-8 minutes to about 90 seconds.

Do I need separate LGPD opt-in for Pix payment confirmation messages?

No. Pix payment confirmation, order confirmation, and NF-e delivery messages fall under LGPD legal basis of contract execution (Article 7, V) — not consent. You need valid opt-in for the initial WhatsApp marketing message that led to the conversation, but the transactional messages after payment do not require separate consent. Always retain logs for the Brazilian Consumer Defense Code (CDC) 5-year limitation period.

What is the typical Pix BR Code expiration time for WhatsApp checkout?

Brazilian e-commerce typically configures Pix BR Code expiration at 10-15 minutes for WhatsApp checkout flows. Shorter (under 5 minutes) creates friction when customers switch between apps or check their balance. Longer (over 30 minutes) increases the risk of price-change or stock-change between charge generation and payment. Configure per use case.

Next Steps

To launch Pix-in-WhatsApp for your Brazilian business, start with the WhatsApp Business API in Brazil platform page. For BSP selection, see the best WhatsApp Business API providers in Brazil comparison. For setup walkthrough, see the setup guide. For abandoned cart strategy, see the abandoned cart recovery guide. For LGPD compliance, see the LGPD compliance guide.