Skip to main content
POST

Boleto and BolePix

Use BOLETO for a bank boleto or BOLETO_PIX for a boleto with a Pix QR code. BolePix offers two ways to pay the same sale; the customer must pay only once. These methods require merchant enablement, a configured boleto fee, and a complete merchant address. Check available payment methods before offering them. Split payments and recurrence are not supported for either method.

Shopper address

shopper.address is required only for BOLETO and BOLETO_PIX. PIX, credit card and Open Banking (INITIATOR) do not require it. Provide a valid shopper CPF or CNPJ. Shopper bank details are not required for boleto or BolePix. Request examples use illustrative data: replace the document and due date before submitting.

Due date and expiration

dueDate uses yyyy-MM-dd, interpreted in America/Sao_Paulo. The default configuration uses today plus 3 days when omitted and accepts dates from today through today plus 20 days. PayMee can configure these limits. For these two methods, sale expiration is calculated from dueDate plus the configured grace period (default: 2 days), instead of the request’s maxAge. The BolePix QR code expires at the end of dueDate. Use the bank’s returned paymentLimitDate, when present, for the boleto payment limit.

Payment instructions and confirmation

Creation returns boleto fields directly in response.instructions: documentNumber, typeableLine, barcode, dueDate, paymentLimitDate, amountDue, status and pdfUrl. BolePix also returns response.instructions.pix.qrCode with the Pix payload and QR code. Use the returned PDF URL as provided. Successful registration is not payment confirmation. Use the existing payment webhook or transaction query to confirm payment. Transaction queries expose boleto details in the root boleto field; its lifecycle status is separate from the sale’s situation.

Boleto errors

Errors use the existing validation envelope: status: -1, message: "validation failure", errorCount and errors containing field, code and message.

Headers

x-api-key
string
required
Example:

"your-x-api-key"

x-api-token
string
required
Example:

"your-x-api-token"

Body

application/json
paymentMethod
enum<string>
required

Chosen payment method

Available options:
BOLETO,
BOLETO_PIX
Example:

"PIX"

shopper
object
required
currency
string
required

ISO-4217 currency code

Maximum string length: 3
Example:

"BRL"

amount
number<float>
required

Order Amount

Example:

11

referenceCode
string
required

Unique order identifier

Maximum string length: 50
Example:

"019922112127617"

maxAge
number

Sale max age in minutes. For BOLETO and BOLETO_PIX, sale expiration is calculated from dueDate plus the configured grace period (default 2 days), instead of this value. The Pix QR code expires at the end of dueDate.

Required range: x <= 43200
Example:

120

callbackURL
string<uri>

Callback URL for transaction updates

Maximum string length: 255
Example:

"https://foo.bar/paymeeListener"

redirectURL
string<uri>

Confirmation redirect URL

Maximum string length: 255
Example:

"https://foo.bar/paymeeRedirect"

observation
string

Any internal reference

Maximum string length: 255
Example:

"Internal Transaction ID 999"

recurrence
number

Recurrence in months (required when paymentMethod is INITIATOR) Not supported for BOLETO or BOLETO_PIX.

Required range: x <= 999
Example:

12

brand_id
string<uuid>

Brand ID of the bank (required when paymentMethod is INITIATOR)

dueDate
string<date>

Boleto/BolePix only. Due date in yyyy-MM-dd, evaluated in America/Sao_Paulo. Default configuration: today + 3 days; allowed range: today through today + 20 days. These limits are configurable by PayMee. Omit to use the default.

Example:

"2026-09-22"

Response

Checkout created. For boleto, successful registration returns payment instructions; it does not confirm payment.

message
string
Example:

"success"

response
object
status
number
Example:

0