--- page_title: PISP (Standard Redirection) product: Express Checkout SDK Global platform: Android page_source: https://juspay.io/br/docs/express-checkout-sdk-brazil/android/pix-via-open-finance/pisp-standard-redirection llms_txt: https://juspay.io/br/docs/llms.txt product_llms_txt: https://juspay.io/br/docs/express-checkout-sdk-brazil/llms.txt --- # 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. ![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/pix-payment-flows-br/PIX%20PISP.png) *PIX PISP Flow* ## **Integration Guide:** --- ### Step 1 Create Order API Call This is a Server-to-Server [API](https://juspay.io/br/docs/pix-payment-flows-br/android/pix-iniciao/step-1-create-order-api#Create-Order-API-) that takes order parameters as an input and creates an order in the Juspay system and fetches the corresponding `client_auth_token`. > **Note** > For PIX PISP: `identity_credentials` field is a required field, this takes customer’s `cpf/cnpj/pix_key` as input ### Step 3 Process Transaction via Juspay SDK [Retrieve Information](https://juspay.io/br/docs/express-checkout-sdk-brazil/android/payloads/display-payment-options) about all the configured payment method via `Get Payment Methods`. Then once the customer selects the preferred Payment Method as PISP (Pague no seu banco), call process function of Juspay SDK with payload given in the example **.** Juspay will show the list of bank institutions and complete the PISP transaction via selected bank. > **Note** > **Important** parameters. > > action**: pixPISP** > > service**: in.juspay.hyperpay** ### Step 5.1. Handle Payment Events from SDK All payment responses are sent by the SDK in the HyperPaymentCallbackHandler under the `process_result` event. Implement the highlighted code snippet in your app for proper handling of all events and status ### Step 5.2. Check Payment Status After receiving `process_result` from SDK, it is mandatory to do a Server-to-Server [Order Status API](https://juspay.io/br/docs/pix-payment-flows-br/android/pix-iniciao/step-4-order-status-api#Order-Status-API) call to determine the final payment status. Please ensure that you verify the order ID and amount transaction. ### Step 5.3. Display Payment Status Once the payment status is determined via the API, the final status should be displayed to the user. This screen needs to be handled by the merchant, it is not provided by the SDK ## **FAQs:** ## FAQs: ### What is the PIX Redirect flow via Open Finance? 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. ### Does the user need to enroll or register in advance? No prior enrolment is required. The user only needs to authenticate and authorize the payment during the session via their bank. ### Is redirection required in every transaction? Yes. Since the user authorizes each payment within the bank's environment, redirection is a core part of the flow. ### Is user consent required for each payment? Yes. Under Open Finance, each payment requires explicit consent from the user, typically given during the redirection to their bank. ### Can we pre-select a user’s bank or restrict the list of available banks? No. Open Finance mandates that all available participant institutions be displayed to the user. Restricting or pre-selecting banks is not supported. ### What happens if the user abandons the flow or does not complete payment at the bank? The transaction will remain in a pending state until timeout, after which it is marked as failed or expired.  ### Are there limits to how much can be paid via this flow? 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. ### Is it possible to retry a failed transaction? Yes. The merchant can offer a retry option by re-initiating the payment request and redirecting the user again. ### Do we need to integrate with each bank separately? No. Juspay abstracts bank-level integrations and provides a unified API layer across all Open Finance participants. ### How do we handle timeouts or incomplete payments? Set up proper polling or webhook handling to detect if the user did not complete the payment.  ## Sample Code Snippets: ### PISP Process Payload: #### Request Code Snippet: ```request { "requestId": "94c8d2505d424ed6a10ef6bad9ce326f", "service": "in.juspay.hyperpay", "payload": { "action": "pixPISP", "billingAddressLine1": "line", "shippingAddressState": "AU", "billingAddressCountryCodeIso": "AU", "firstName": "John", "clientId": "yourClientId", "billingAddressFirstName": "default", "billingAddressLastName": "al", "identityCredentials": "{\"cpf\":\"***86771***\"}", "customerId": "testcustomer", "shippingAddressCountryCodeIso": "AU", "billingAddressPostalCode": "24124141", "orderId": "ORD1751875443", "currency": "BRL", "customerEmail": "taza@gmail.com", "customerPhone": "7760250078", "service": "in.juspay.hyperpay", "description": "Complete your payment", "shippingAddressLastName": "default", "environment": "sandbox", "billingAddressCity": "city", "lastName": "wick", "merchantId": "yourMerchantId", "amount": "10.0", "billingAddressCountry": "AU", "clientAuthTokenExpiry": "2025-07-07T08:19:03Z", "shippingAddressCountry": "AU", "billingAddressState": "AU", "clientAuthToken": "tkn_b203ccc1493942e8bf7934ea6dcd299e" } } ``` --- ## See Also - [Annexure](https://juspay.io/br/docs/express-checkout-sdk-brazil/android/preauth-and-capture/annexure) - [Biometric](https://juspay.io/br/docs/express-checkout-sdk-brazil/android/pix-via-open-finance/biometric)