PIX PISP

This flow allows users to initiate a Pix payment by redirecting them to their financial institution, where they authenticate and approve the payment using their bank's app or website.

No prior enrolment is required. The user only needs to authenticate and authorize the payment during the session via their bank.

Yes. Since the user authorizes each payment within the bank's environment, redirection is a core part of the flow.

Yes. Under Open Finance, each payment requires explicit consent from the user, typically given during the redirection to their bank.

No. Open Finance mandates that all available participant institutions be displayed to the user. Restricting or pre-selecting banks is not supported.

The transaction will remain in a pending state until timeout, after which it is marked as failed or expired. 

Yes. Limits are determined by the user’s bank and their personal pix settings (e.g., per transaction and daily caps). Merchants should surface appropriate error messages if limits are hit.

Yes. The merchant can offer a retry option by re-initiating the payment request and redirecting the user again.

No. Juspay abstracts bank-level integrations and provides a unified API layer across all Open Finance participants.

Set up proper polling or webhook handling to detect if the user did not complete the payment.