If you already have the Person Payment expansion (QT) manually through API and you want to attach the Company Payment flow, you only have to consider the following points:

• The flow to initiate the payment is identical to the Person one.
• For Company Payment, the JWT issued in the redirection notification and webhook will have a few parameters different to those used for Person Payment flow; in addition to a an extra “payment_step”, which notifies what step of the payment validation is taking place. (You will receive a JWT format for Company Payment and another for Person Payment, to see the complete details of each of these please refer to the following section: Single Flow
• You will receive more than one webhook notification for the Company Payment each time theres a change that can have the “payment_step” input.

Development of each stage / Company Payment

<aside> <img src="/icons/warning_yellow.svg" alt="/icons/warning_yellow.svg" width="40px" /> Remember that the format of the JWT in both the redirect and webhook notifications for the QT will continue to arrive to you in the same form in which you are capturing it.

</aside>

Redirection success - current Payment Status / Error

When a successful payment is made or the payer explicitly cancels the payment process, the browser will redirect to the URL indicated by the merchant, the success_url or error_url specified inBasic Pre-requirements will be used, consider that the same URL can be used for both and differentiate the behavior according to the payment_status and payment_step parameters.

<aside> ⚠️ In the case of payment by any method, whether Company Payment or Person Payment, a transaction in which the banking institution for payment is not chosen is not considered as an initiated transaction and therefore is never reported as failed (since it only exists as a session within the system and not as a payment in progress).

</aside>

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> It is possible to define the redirection and notification URLs at the time of create the session, this is specified in the additional customization, redirection and dynamic notification.

</aside>

🟢 Payment success - Current payment status

In the case of a transfer through Pago Empresa, the payment will be updated depending on the permissions of each user (Add recipient, add transfer, enroll or authorize), the funnel will redirect to the success_url through a GET type request that will include the JWT as a parameter within the url, it will be named "jwt" as shown in the example. The JWT will have the payment information described in the JSON below.

*It should be noted that the redirection will only take place if the user started the process from the merchant's website, if the user continues the process through a link via email, there is no redirection.

The following URL is an example of a redirect:

GET request:
https://[SUCCESS_URL]?jwt=eyJhbGciOiJIU[...]MQpdNsnAIl_TU2Y

• JWT example to test Company Payment: