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:integer
Payin IDExample:
49339string
Payin invoiceExample:
eb21ce52-2897-475b-85af-a5201f4035bfstring
Payin end-to-endExample:
END-TO-END-IDobject
Object that contains the current status of your payin.
object
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.
string
Last update of your payin.Format:
<date-time>Example: 2024-09-09T20:55:56.000000Zobject
Additional metadata about the payment.
Webhook Payload Example
Status Codes
Common payin status codes:
See Payin Status Flow for detailed status information.
Status Detail Codes
When a PIX transaction is rejected/canceled, thestatus_detail.code field provides specific information about the rejection reason:
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

