Skip to main content

Cancel a pending charge

POST 

/v1/charges/:chargeId/cancel

Cancels only charges in the pending state. A 202 means the result is not yet authoritative. There is no background reconciliation: replay the same payload with the same Idempotency-Key to continue safely. Before the durable PSP-dispatch fence, provider absence keeps the intent pending; after that fence, lookup absence confirms cancellation without repeating the DELETE.

Request​

Responses​

Cancellation confirmed authoritatively.

Did this page unblock the next step?

Feedback stays inside the docs flow and should never include customer or card data.

mupag / support

How can we help?

Quick answers, AI and our team.

Frequently asked questions

How do I start integrating?

Follow the quickstart, configure the QA environment and create your first test charge.

Read documentation
My PIX payment is pending. What now?

Confirmation is asynchronous. Check the charge status and webhook events before fulfilling the order.

Read documentation
How do I receive payment notifications?

Register a webhook endpoint, verify its signature and handle duplicate events safely.

Read documentation
How do subscriptions work?

Read the subscriptions guide to configure recurring billing and follow the charge lifecycle.

Read documentation
Where can I find authentication help?

See how to use environment credentials in the documentation. Never share your key in chat.

Read documentation