Reject a Payment Batch
PUT/v2/payment/batches/:uid/reprove
Asynchronous Processing: This endpoint is processed asynchronously and creates a rejection command for the Payment Batch. The rejection of a Payment Batch is done asynchronously, that is, upon receiving the request, our API saves the request and creates a Command. This command is processed in the background and after confirmation, the Batch has its status changed to Rejected. You receive in the response of this request the ID of the created command and can consult it at any time.
Webhook Events
When the request is made, a payment.payment_batch.reprove.requested event is triggered.
Our server then begins attempts to send the release to the financial institution.
Only after confirmation from the financial institution is the batch marked as approved in our database.
At this moment the payment.payment_batch.reprove.confirmed event is triggered.
⚠️ Attention to Rejected Status: The Rejected status is terminal. When the financial institution cancels the payments, they will have their status changed to Rejected
Request
Responses
- 200
- 422
Command created successfully
Payment Batch is not awaiting release