Payments / RailsPIX
PIX
Brazilian instant payment system. Used for pay-in and pay-out in Brazil.
Rail overview
Use PIX for Brazilian instant payments. As an origin, Conomy returns QR and copy-paste data; as a destination, it routes funds to the recipient key or account.
Pay-ins wait for payer action and provider confirmation. Pay-outs move from an internal ACCOUNT through capture into the PIX network.
For pay-ins, display both the QR code and copy-paste string and listen for payment webhooks instead of polling the banking app state.
Required fields
Section titled “Required fields”| Field | Type | Description |
|---|---|---|
type | string | Must be "PIX" |
currency | string | Must be "BRL" |
pix.customer.firstName | string | Payer’s first name |
pix.customer.lastName | string | Payer’s last name |
pix.customer.email | string | Payer’s email |
pix.customer.documentNumber | string | Brazilian CPF (11 digits) |
pix.successUrl | string | Redirect URL on success |
pix.failedUrl | string | Redirect URL on failure |
Example
Section titled “Example”{ "type": "PIX", "currency": "BRL", "pix": { "successUrl": "https://yourapp.com/success", "failedUrl": "https://yourapp.com/failed", "customer": { "firstName": "João", "lastName": "Silva", "email": "joao@example.com", "documentNumber": "12345678901" } }}Response fields
Section titled “Response fields”After the payment is created, the pix object in the response includes:
| Field | Description |
|---|---|
qrCode | Base64-encoded QR code image |
data | PIX copy-paste code (EMV string) |
expiredAt | Expiration timestamp (UTC) |
Show the qrCode or data to your user so they can complete the payment in their banking app.
Object
Section titled “Object”The actual PIX code (EMV-compliant string) that represents the payment. This is what is known as the 'PIX' in Brazil and can be copied and pasted instead of scanning.
The rendered QR code string that can be scanned for PIX payments.
The expiration date and time of the QR code. UTC format.
Optional instructions displayed to the user for completing the PIX payment.
Details of the customer initiating the payment.
idstringUnique identifier for the internal service.
firstNamestringrequiredPayer's name
emailstringPayer's email
lastNamestringPayer's last name
phoneNumberstringPayer's phone number without prefix
phoneNumberPrefixstringPhone number prefix (e.g., +57)
documentTypestringDocumeny type of the entity (e.g., RUT, CURP, CURL). Go to the Supported Identity document types page for the complete list of supported values.
documentNumberstringThe document number associated with the documentType
addressobjectThe entity’s address information.
administrativeAreaLevel1stringThe first-level administrative division.
administrativeAreaLevel2stringThe second-level administrative division.
administrativeAreaLevel3stringThe third-level administrative division.
streetstringThe name of the street.
streetNumberstringThe street number.
optionalAddressstringAdditional address details.
countrystringCountry of operations for the entity, specified using the ISO 3166-1 alpha-3 standard (e.g., CHL, USA, MEX). Go to the countries page for the complete list of supported values.
zipcodestringZipcode f the address
Redirect url in case of success
Redirect url in case of failure