Semi-transparent PIX, boleto, BolePix, credit card and Open Banking checkout
Creates a semi-transparent checkout. BOLETO and BOLETO_PIX require merchant enablement, a configured boleto fee, a complete merchant address, and the shopper document and address. Shopper address is required only for these two methods. Split payments and recurrence are not supported for boleto. Bank transfers and cash deposits are unavailable. Requests using these methods return HTTP 400 with code bank_transfer.discontinued.
Boleto and BolePix
UseBOLETO 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.
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 inresponse.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
"your-x-api-key"
"your-x-api-token"
Body
- Boleto or BolePix
- Other payment methods
Chosen payment method
BOLETO, BOLETO_PIX "PIX"
ISO-4217 currency code
3"BRL"
Order Amount
11
Unique order identifier
50"019922112127617"
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.
x <= 43200120
Callback URL for transaction updates
255"https://foo.bar/paymeeListener"
Confirmation redirect URL
255"https://foo.bar/paymeeRedirect"
Any internal reference
255"Internal Transaction ID 999"
Recurrence in months (required when paymentMethod is INITIATOR) Not supported for BOLETO or BOLETO_PIX.
x <= 99912
Brand ID of the bank (required when paymentMethod is INITIATOR)
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.
"2026-09-22"

