Cash-in Status Flow
We will show the life cycle for PIX payins, regarding the status. The notification sent to the payin will be based on the final status. The final status represents when the payment is completed, approved by compliance, and with the value available for withdrawal. The status will follow the cycle below:Cash-in pix
PIX notifications will be completed shortly after the payment is done.
PIX Status Flow Explanation
- CREATED: Initial status when the payin is created
- CANCELED: Canceled by operator or expired
- PAID: Payment paid
- CREDITED: Payment credited, final status
- REJECTED: Blocked by compliance review
Cash-in boleto
Note: refunds done to customers must be done apart the api
Boleto Status Flow Explanation
- CREATED: Initial status when the payin is created
- CANCELED: Canceled by operator or expired
- PAID: Payment paid
- CREDITED: Payment credited, final status
- DROP_REQUESTED: Cancellation requested (when boleto expires)
- REJECTED: Blocked by compliance review
Possible charge (payin) status
| ENUM_CODE | STATUS | EXPLANATION | |
|---|---|---|---|
| 1 | Created | The first status when the payin is created | |
| 2 | Canceled | Cash-in canceled due to expiration | |
| 3 | Paid | Cash-in successfully paid | |
| 4 | Credited | The amount is paid and available for withdrawal / settlement | |
| 5 | Drop_requested | Cash-in transaction canceled at the user’s request | |
| 7 | Rejected | Cash-in rejected due to compliance reason |
Status Details
1 - Created
1 - Created
Initial StatusThis is the first status when a payin is created. The charge is active and waiting for payment.
- PIX: QR Code is generated and ready to be scanned
- Boleto: Boleto is generated and ready to be paid
2 - Canceled
2 - Canceled
Final StatusCash-in was canceled due to expiration or operator action.Reasons:
- Expiration date reached without payment
- Manual cancellation by operator
- Automatic cancellation after drop_requested
3 - Paid
3 - Paid
Intermediate StatusPayment was successfully received but is under compliance review.
- PIX: Payment confirmed in seconds
- Boleto: Payment confirmed after bank processing (D+1)
4 - Credited
4 - Credited
Final StatusThe amount is paid, approved by compliance, and available for withdrawal/settlement.This is the final success status:
- Funds are available in your wallet
- Webhook notification is sent
- Ready for withdrawal or settlement
5 - Drop_requested
5 - Drop_requested
Intermediate StatusCash-in transaction cancellation was requested.
- PIX: Canceled immediately
- Boleto: Enters cancellation queue, takes 1 working day
7 - Rejected
7 - Rejected
Final StatusCash-in was rejected due to compliance validation.Reasons:
- Failed compliance checks
- Document restrictions
- Blocked by fraud prevention
Webhook Notifications
Webhooks are sent only for final statuses: Credited, Canceled, Rejected
When to Expect Webhooks
- PIX
- Boleto
Fast NotificationsPIX webhooks are sent shortly after payment completion:
- Credited: Within seconds after payment approval
- Rejected: Within seconds if compliance fails
- Canceled: Immediately after cancellation
Status Monitoring
1
Create Charge
Use Create Charge to generate a PIX or Boleto.Initial status: Created (1)
2
Customer Pays
Customer completes payment using PIX QR Code or Boleto.Status changes to: Paid (4)
3
Compliance Check
System performs compliance validation (PIX only).
- If approved: Credited (5)
- If rejected: Rejected (3)
4
Receive Webhook
Webhook notification is sent with final status.Your system receives the notification and processes accordingly.
Best Practices
Implement Webhooks
Always use webhooks instead of polling to receive status updates efficiently.
Handle All Statuses
Implement logic to handle all possible statuses in your application.
Check Final Status
Only consider Credited (5) as successful payment. Paid (4) is still under review.
Monitor Expiration
Set appropriate expiration dates and handle Canceled status gracefully.
Integration Example
Related Resources
Create Charge
Create PIX or Boleto charges
Get Charge
Check charge status
Webhook Setup
Configure webhook notifications
Rejection Reasons
Understand rejection codes
About Charges
Learn about Payin solutions
Refunds
Process PIX refunds
Additional Notes
You can check the reasons why our compliance team will reject a payment in our article Rejection reasons payin.
For more information about webhook, check our article Webhook Signature Documentation.

