One reference per payment
Keep the invoice identifier connected to each transaction and retrieve its history when your finance team needs to review it.
Add Pix collections to your SaaS, ERP or business management system. Link each payment to a customer and invoice, receive updates and connect confirmation to your own access or service delivery rules.
Illustrative flow
Keep the invoice identifier connected to each transaction and retrieve its history when your finance team needs to review it.
Signed notifications report payment changes. Your application decides how to update the invoice and the customer's status.
Start with a BRL balance and Pix withdrawals. Add crypto conversion later if it fits your business.
Your software defines the amount, customer and reference. The integration requests a payment and receives its QR and copy-and-paste code.
Show the amount and expiry in your interface. For production transactions, the customer pays through their banking app.
Check payment confirmation and settlement, update the invoice and query the transaction to recover from missed notifications.
Your team can integrate through code, or use AI agents with OpenAPI, MCP and Lunium Mesh. Organize your account’s sandbox and production keys in the dashboard.
Your software creates a Pix payment request for the customer to pay each billing cycle. Pix Automático is not part of this flow.
Use a stable reference for each transaction. After a communication failure, recover the original payment and follow the API's retry rules.
Yes. The sandbox simulates payment, expiry and failure without moving funds. Documentation and examples remain open to developers and AI agents.
Start with an account and test in the sandbox. If you want to discuss your operation, our team can help map the flow.