Skip to main content

​
What is PIX OUT?

PIX OUT is the feature that allows you to send PIX payments from your Owem account to any PIX key in Brazil. Ideal for supplier payments, cashback, and general transfers.

Instant

Transfers in seconds, 24/7.

Any Key

CPF, CNPJ, email, phone, or random key.

Idempotency

Use externalId to avoid duplicate transfers.

Webhooks

Success or failure notification.

​
How It Works

1

Send Request

Your application calls the API with the PIX key, amount, and description.
2

Owem Validates

We validate balance, limits, and recipient data.
3

PIX Processed

The PIX system processes the transfer.
4

Confirmation

Webhook is triggered with final status (success or failure).

​
Use Cases

Use CaseDescription
Supplier paymentsPay suppliers automatically
CashbackReturn part of the value to the customer
WithdrawalsAllow users to withdraw balance
PayrollPay employees via PIX
CommissionsPay affiliate commissions

​
PIX Key Types

The PIX key is the most common way to identify the recipient. Using the key, you don’t need to provide complete bank details.
TypeDescriptionValidation (Regex)
CPFRecipient’s CPF (tax ID)^[0-9]{11}$
CNPJRecipient’s CNPJ (business tax ID)^[0-9]{14}$
PhoneNumber with country code^\+[1-9][0-9]\d{1,14}$
EmailEmail addressValid email
EVPRandom key (generated by BACEN)^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$

​
Valid Key Examples

TypeExample
CPF12345678901
CNPJ12345678000190
Phone+5511999999999
Emailuser@email.com
EVPa1b2c3d4-e5f6-7890-abcd-ef1234567890
Besides PIX key, you can also make payments via QR Code (Copy and Paste) or by providing the recipient’s bank details directly.

​
Lifecycle

PROCESSING → SUCCEEDED
         ↓
       FAILED
StatusDescription
processingTransfer in processing
succeededTransfer completed successfully
failedTransfer failed

​
Idempotency

Use externalId to ensure the same transfer is not executed twice: 
{
  "pixKey": "user@email.com",
  "amount": 150.0,
  "description": "Supplier payment",
  "externalId": "sup-pay-2025-001"
}
If you send the same request with the same externalId, the API will return the result of the original transfer without creating a new one.

​
Validations

Before processing, the API validates:
ValidationError if fails
Available balanceINSUFFICIENT_BALANCE
Daily limitDAILY_LIMIT_EXCEEDED
PIX key existsPIX_KEY_NOT_FOUND
Recipient not blockedBLOCKED_RECIPIENT
Allowed timeTRANSFER_NOT_ALLOWED

Send PIX

POST /v4/i/bank-accounts/{accountId}/transfer/external

Pay QR Code

POST /v4/i/bank-accounts/{accountId}/transfer/pay

Query Transfer

GET /v4/i/bank-accounts/{accountId}/transfer/external/{endToEnd}

​
Webhooks

​
Transfer Completed

{
  "event": "pix_out:succeeded",
  "data": {
    "endToEndId": "E37839059202512261234567890abcdef",
    "externalId": "sup-pay-2025-001",
    "amount": 150.0,
    "status": "succeeded",
    "completedAt": "2025-12-26T15:30:45.000Z",
    "recipient": {
      "name": "SUPPLIER COMPANY LTD",
      "pixKey": "user@email.com"
    }
  }
}

​
Transfer Failed

{
  "event": "pix_out:failed",
  "data": {
    "endToEndId": null,
    "externalId": "sup-pay-2025-001",
    "amount": 150.0,
    "status": "failed",
    "failedAt": "2025-12-26T15:30:45.000Z",
    "reason": "PIX_KEY_NOT_FOUND"
  }
}

​
Best Practices

Always use externalId

Ensure idempotency and avoid duplicate transfers.

Validate key first

Check the PIX key format before sending.

Implement webhooks

Don’t rely only on polling; use webhooks.

Monitor failures

Track failure rate to identify issues.