Skip to main content

Decide KYB for the authenticated merchant in sandbox

POST 

/v1/_test/merchant/kyb-decision

This authenticated helper is available only when customer-service starts with the local, sandbox, or test profile. The route does not exist in the prd environment, nor with an empty or unknown profile. The merchant is the one from the API key; merchant_id in the body is optional and rejected when it diverges. It emits the same outbox audit as the backoffice KYB decision, with environment=sandbox. documents_pending remains in go-live and is published on the event as requires_additional_info, a non-eligible state accepted by the contract.

Request​

Responses​

Authenticated merchant KYB applied or original response returned.

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