JavaScript is disabled. Some features may not work. You can also read the static version: View text version

PIX PISP

Pix Initiation empowers merchants and wallet providers to offer seamless, embedded payment experiences directly from within their applications. Built on Open Finance standards, it allows users to initiate Pix transactions securely and instantly—directly redirecting the user to Bank environment and improve conversion by elevating the User Experience.

Integration Guide:

Step 1

Session API Call

This is a Server-to-Server API that takes order parameters as an input and returns the SDK payload and the payment link. This also creates order in the Juspay system.

For PIX PISP: identity_credentials field is a required field, this takes customer’s cpf/cnpj as input. For the PJ segment, cnpj along with cpf is mandatory.

Step 2

Open HyperCheckout Screen

Once the Hypercheckout screen is opened, your users can proceed with the transactions. Opening Hypercheckout requires the SDK Payload from Step 1. The response of this should be forwarded to the Hypercheckout SDK in order to open the payment screen.

Alternatively, payment link given in session api response can be launched directly in the browser that will handle the complete flow end to end.

Step 3.

Handle Payment Events

Step 4.

Check Payment Status

Step 5.

Display Payment Status

PIX PISP

Integration Guide:

FAQs

What is the PIX Redirect flow via Open Finance?

Does the user need to enroll or register in advance?

Is redirection required in every transaction?

Is user consent required for each payment?

Can we pre-select a user’s bank or restrict the list of available banks?

What happens if the user abandons the flow or does not complete payment at the bank?

Are there limits to how much can be paid via this flow?

Is it possible to retry a failed transaction?

Do we need to integrate with each bank separately?

How do we handle timeouts or incomplete payments?