Callback Charge
Callback Charge
Receive updates about your payin
POST
Callback Charge
Endpoint:
POST https://your.endpoint.to.notifyThis is your endpoint where WEpayments will send notifications about payin status changes.Response
You should respond with 200 OK to acknowledge receipt of the webhook.Body
The webhook payload contains the following fields:Payin IDExample:
49339Payin invoiceExample:
eb21ce52-2897-475b-85af-a5201f4035bfPayin end-to-endExample:
END-TO-END-IDObject that contains the current status of your payin.
This object will only be returned if the payin is rejected/canceled and the merchant is using the “Account Mismatch” functionality. It provides more details on the reason for the rejection.
Last update of your payin.Format:
<date-time>Example: 2024-09-09T20:55:56.000000ZAdditional metadata about the payment.
Webhook Payload Example
Status Codes
Common payin status codes:| Status ID | Status Name | Description |
|---|---|---|
| 1 | Created | Charge has been created |
| 2 | Canceled | Charge canceled due to expiration |
| 3 | Rejected | Charge rejected due to compliance |
| 4 | Paid | Charge successfully paid |
| 5 | Credited | Amount is paid and available for withdrawal |
| 6 | Drop_requested | Cancellation requested |
Status Detail Codes
When a PIX transaction is rejected/canceled, thestatus_detail.code field provides specific information about the rejection reason:
| Code | Description |
|---|---|
reason_payer_divergence | CPF mismatch |
reason_payer_restriction_deceased_holder | CPF restriction: deceased holder |
reason_payer_restriction_canceled | CPF restriction: canceled document |
reason_payer_restriction_suspended | CPF restriction: suspended document |
reason_payer_pending_regularization | CPF restriction: pending regularization |
reason_payer_restriction_unknown | CPF restriction: unknown document |
gl_cpf_payer_restriction_underage | CPF restriction: underage (Brazilian law) |
reason_payer_restriction_age_above_limit | Restriction: age above limit (> 80 years) |
pending_challenge | Pending challenge |
reason_payer_restriction_receita | CPF restriction (Tax Authority) |
payer_restriction_high_risk | CPF high risk |
pending_review_manual | Payment created; awaiting manual review |
payer_restriction | Rejected per compliance policy |
reason_payer_restriction_pep | PEP (Politically Exposed Person) |
reason_payer_restriction_list_restrict | CPF on restriction list |
reason_payer_restriction_cpf_irregular | Irregular CPF |
reason_payer_restriction_judicial_block | Judicial block |
reason_payer_restriction_partners_and_ownership | Certified restriction (partners/ownership) |
reason_payer_restriction_ofac | CPF on OFAC list |
reason_payer_restriction_interpol | CPF on INTERPOL list |
reason_payer_restriction_onu | CPF on UN list |
reason_payer_restriction_euro | CPF on European restriction list |
WE0001 | The payment was made from an unregistered account |
WE0002 | The payment was made from an unauthorized institution |
reason_payer_restriction_pld | KYC restriction |
These codes are only returned when the payin status is Rejected/Canceled and the merchant has the “Account Mismatch” functionality enabled.
Best Practices
Always Respond 200 OK: Your endpoint must respond with HTTP 200 to acknowledge receipt.
Related Resources
Create Charge
Create PIX or Boleto charges
Status Flow
Understand payin status lifecycle
Rejection Reasons
Learn about rejection codes
Get Charge
Query charge details
Webhook Signature
Validate webhook signatures

