feat: pix automatico by aritro2002 · Pull Request #1435 · juspay/hyperswitch-web

aritro2002 · 2026-03-23T12:07:51Z

Type of Change

Description

This PR introduces comprehensive support for Pix Automatico payments (both QR and Push variants) in the Hyperswitch Web SDK by implementing a new wait_screen_information next action flow. This enables Brazilian merchants to offer seamless Pix payment experiences where users can complete transactions through their banking applications with real-time status polling and customizable waiting screen messaging.

What Changed

1. Wait Screen Information Flow Implementation

The core of this PR is the implementation of the wait_screen_information next action type, which provides a robust mechanism for handling asynchronous payment confirmations that require user action outside the SDK iframe.

Key Components:

Enhanced Type System: Extended the nextAction type to support poll_config with configurable delay_in_secs and frequency parameters, along with display_to_timestamp for timeout management.
Intelligent Polling Mechanism: Implemented a sophisticated polling system in pollRetrievePaymentIntent that:
- Respects configurable delays between status checks
- Uses nanosecond-precision timestamps for accurate timeout calculation
- Gracefully handles timeout by performing a final status retrieval
- Continues polling until either payment completion or timeout
Metadata-Driven Loader: The payment loader now receives payment method information through metadata, enabling contextual messaging based on the specific payment method being used.

Flow Architecture:

When a payment returns wait_screen_information as the next action:

The SDK displays a fullscreen payment loader with method-specific messaging
Begins polling the payment intent status at intervals defined by poll_config.delay_in_secs
Each poll checks if the payment has reached a terminal state (succeeded or failed)
Polling continues until either:
- Payment status becomes terminal (success/failure)
- Current time exceeds display_to_timestamp
Upon timeout, a final retrievePaymentIntent call fetches the latest status
The loader closes and the final result is communicated back to the merchant

2. Contextual Loader Messaging

A significant UX improvement in this PR is the introduction of payment-method-specific loader messages. Rather than showing generic "Processing payment" text for all flows, the loader now displays contextual information based on the payment method.

For Pix Automatico Push:

Title: "Please confirm the payment in your banking app"
Subtitle: "Open your banking application and authorize the payment request. The status will be updated automatically once confirmed."

This approach:

Sets clear expectations for users about what action they need to take
Reduces confusion by explaining the external authorization flow

How did you test it?

I have tested it locally by hardcoding confirm and PML response
PML

Screen.Recording.2026-03-23.at.5.13.33.pm.mov

Checklist

I ran npm run re:build
I reviewed submitted code
I added unit tests for my changes where possible

semanticdiff-com · 2026-03-23T12:07:54Z

Review changes with

claude-code-pr-reviewer · 2026-03-23T21:41:02Z

src/Utilities/PaymentHelpers.res

                  ]->getJsonFromArrayOfJson
                resolve(response)
+              } else if intent.nextAction.type_ === "wait_screen_information" {
+                let displayToTimestamp = intent.nextAction.display_to_timestamp->Option.getOr(0.0)


When display_to_timestamp is None, it defaults to 0.0. Since currentTime >= 0.0 is always true, the polling terminates immediately on the first check, defeating the purpose of the wait screen.

Suggested Fix:

let displayToTimestamp = intent.nextAction.display_to_timestamp->Option.getOr( Date.now() *. 1000000.0 +. 300000000000.0 // 5 minutes from now in nanoseconds )

posted by PR reviewer bot

claude-code-pr-reviewer · 2026-03-23T21:43:39Z

src/Utilities/PaymentHelpers.res

+                  )
+                  ->ignore
+                }
+                resolve(data)


resolve(data) executes immediately after starting the async polling chain (line 909), not waiting for polling to complete. The promise resolves before the polling result is known.

Suggested Fix:

if !isPaymentSession { let metaData = [("paymentMethod", paymentMethod->JSON.Encode.string)]->getJsonFromArrayOfJson messageParentWindow([ ("fullscreen", true->JSON.Encode.bool), ("param", `paymentloader`->JSON.Encode.string), ("iframeId", iframeId->JSON.Encode.string), ("metadata", metaData), ]) pollRetrievePaymentIntent( clientSecret, ~headers=headersDict, ~publishableKey=confirmParam.publishableKey, ~logger=optLogger->Option.getOr(LoggerUtils.defaultLoggerConfig), ~customPodUri, ~sdkAuthorization, ~delayInMs=pollConfig.delay_in_secs * 1000, ~endTimestamp=Some(displayToTimestamp), ) ->Promise.then(retrievedData => { closePaymentLoaderIfAny() postSubmitResponse(~jsonData=retrievedData, ~url=url.href) resolve(retrievedData) Promise.resolve() }) ->Promise.catch(_ => { closePaymentLoaderIfAny() postSubmitResponse(~jsonData=data, ~url=url.href) resolve(data) Promise.resolve() }) ->ignore } else { resolve(data) }

posted by PR reviewer bot

claude-code-pr-reviewer · 2026-03-23T21:44:32Z

src/Components/Loader.res

+
+let parsePaymentMethod = methodString => {
+  switch methodString {
+  | "pix_automatico_push" => PixAutomaticoPush


The loader checks for "pix_automatico_push", but PaymentMethodsRecord.res and DynamicFieldsUtils.res use "pix_automatico_push_transfer". The loader will never match and always show generic "Other" text for Pix Automatico Push payments.

Suggested Fix:

let parsePaymentMethod = methodString => { switch methodString { | "pix_automatico_push_transfer" => PixAutomaticoPush | _ => Other } }

posted by PR reviewer bot

claude-code-pr-reviewer · 2026-03-23T21:45:17Z

src/Types/PaymentConfirmTypes.res

  reference: string,
 }

+type pollConfig = {


The frequency field is parsed from the API response but never referenced in the polling logic. This is either dead code or a missing implementation.

Suggested Fix:
Either implement frequency-based polling limits or remove the field:

// If intended to limit poll count, add to pollRetrievePaymentIntent: if pollConfig.frequency > 0 && currentAttempt >= pollConfig.frequency { // Stop polling, return current status }

posted by PR reviewer bot

claude-code-pr-reviewer · 2026-03-23T21:46:09Z

src/Utilities/PaymentHelpers.res


-    if status === "succeeded" || status === "failed" {
-      resolve(json)
+  switch endTimestamp {


The Some(timestamp) and None branches contain ~50 lines of nearly identical polling logic, violating DRY principle.

Suggested Fix:

let rec pollRetrievePaymentIntent = (...) => { open Promise let isExpired = switch endTimestamp { | Some(timestamp) => let currentTime = Date.now() *. 1000000.0 currentTime >= timestamp | None => false } if isExpired { retrievePaymentIntent(...) ->then(json => resolve(json)) ->catch(_ => resolve(JSON.Encode.null)) } else { retrievePaymentIntent(...) ->then(json => { let dict = json->getDictFromJson let status = dict->getString("status", "") if status === "succeeded" || status === "failed" { resolve(json) } else { delay(delayInMs) ->then(_val => pollRetrievePaymentIntent(..., ~endTimestamp)) } }) ->catch(e => { Console.error2("Unable to retrieve payment due to following error", e) pollRetrievePaymentIntent(..., ~endTimestamp) }) } }

posted by PR reviewer bot

claude-code-pr-reviewer · 2026-03-23T21:46:38Z

src/Components/Loader.res

+
+let getLoaderTextConfig = (paymentMethod: loaderPaymentMethod) => {
+  switch paymentMethod {
+  | PixAutomaticoPush => {


User-facing loader text is hardcoded in English, violating the codebase's i18n pattern used elsewhere (see PaymentMethodsRecord.res and locale files).

Suggested Fix:
Add to LocaleStringTypes.res:

type localeStrings = { ... loaderProcessingTitle: string, loaderProcessingSubtitle: string, loaderPixPushTitle: string, loaderPixPushSubtitle: string, }

Then pass localeString prop to Loader component.

posted by PR reviewer bot

claude-code-pr-reviewer · 2026-03-23T21:46:56Z

src/Components/Loader.res

+  }
+}
+
+let getLoaderTextConfig = (paymentMethod: loaderPaymentMethod) => {


ReScript can infer the type from pattern matching; explicit annotation is unnecessary per best practices.

Suggested Fix:

let getLoaderTextConfig = paymentMethod => {

posted by PR reviewer bot

claude-code-pr-reviewer · 2026-03-23T21:47:17Z

src/Utilities/PaymentHelpers.res

                resolve(response)
+              } else if intent.nextAction.type_ === "wait_screen_information" {
+                let displayToTimestamp = intent.nextAction.display_to_timestamp->Option.getOr(0.0)
+                let pollConfig =


The default {delay_in_secs: 2, frequency: 0} duplicates PaymentConfirmTypes.defaultPollConfig.

Suggested Fix:

let pollConfig = intent.nextAction.poll_config->Option.getOr(PaymentConfirmTypes.defaultPollConfig)

posted by PR reviewer bot

claude-code-pr-reviewer · 2026-03-23T21:58:35Z

src/Utilities/PaymentHelpers.res

-  ->catch(e => {
-    Console.error2("Unable to retrieve payment due to following error", e)
-    pollRetrievePaymentIntent(
+  | None =>


The None branch has no termination condition. If payment status never becomes "succeeded" or "failed", the function recurses indefinitely, causing a stack overflow or hanging the browser.

Suggested Fix:

| None => // Add max retries or require endTimestamp to always be Some let maxRetries = 30 let calculatedEndTimestamp = Date.now() *. 1000.0 +. maxRetries *. delayInMs pollRetrievePaymentIntent( clientSecret, ~headers, ~publishableKey, ~logger, ~customPodUri, ~isForceSync, ~sdkAuthorization, ~delayInMs, ~endTimestamp=Some(calculatedEndTimestamp), )

posted by PR reviewer bot

feat: pix automatio

5efa391

aritro2002 self-assigned this Mar 23, 2026

aritro2002 requested review from AbhishekChorotiya, ArushKapoorJuspay, sakksham7 and seekshiva as code owners March 23, 2026 12:07

aritro2002 added the Ready for Review PR with label Ready for Review should only be reviewed. label Mar 23, 2026

aritro2002 had a problem deploying to Testing March 23, 2026 12:07 — with GitHub Actions Failure

aritro2002 linked an issue Mar 23, 2026 that may be closed by this pull request

feat: pix automatico #1434

Open

claude-code-pr-reviewer reviewed Mar 23, 2026

View reviewed changes

refactor: apply suggested changes

f85da1a

aritro2002 had a problem deploying to Testing April 3, 2026 15:52 — with GitHub Actions Failure

refactor: apply suggested changes

2f1689e

aritro2002 force-pushed the pix-automatico branch from 7887105 to 2f1689e Compare April 4, 2026 14:03

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: pix automatico#1435

feat: pix automatico#1435
aritro2002 wants to merge 3 commits intomainfrom
pix-automatico

aritro2002 commented Mar 23, 2026

Uh oh!

semanticdiff-com bot commented Mar 23, 2026

Uh oh!

claude-code-pr-reviewer Mar 23, 2026

Uh oh!

claude-code-pr-reviewer Mar 23, 2026

Uh oh!

claude-code-pr-reviewer Mar 23, 2026

Uh oh!

claude-code-pr-reviewer Mar 23, 2026

Uh oh!

claude-code-pr-reviewer Mar 23, 2026

Uh oh!

claude-code-pr-reviewer Mar 23, 2026

Uh oh!

claude-code-pr-reviewer Mar 23, 2026

Uh oh!

claude-code-pr-reviewer Mar 23, 2026

Uh oh!

claude-code-pr-reviewer Mar 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

aritro2002 commented Mar 23, 2026

Type of Change

Description

What Changed

1. Wait Screen Information Flow Implementation

2. Contextual Loader Messaging

How did you test it?

Checklist

Uh oh!

semanticdiff-com bot commented Mar 23, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants