I like the original commit message:

fix(infinite): redirect to KYC webview for PENDING customers

When a customer with PENDING KYC status already exists, skip the KYC
form and redirect directly to the KYC webview. The form is now only
shown for new customers without a customerId.

Extract openKycWebView helper to reuse webview logic in both the
PENDING status handling and new customer form submission flows.

It explained "why" this change.

I realize during this review turn that no localized errors should be implemented in the infiniteApi.

How we've handle localization and plan to handle localization is a the ramp plugin level, not the API library level. For example we translate duplicate_record errors in kycWorkflow.ts:

          if ('error' in customerResponse) {
            if (
              customerResponse.error instanceof InfiniteApiError &&
              customerResponse.error.detail.includes('duplicate_record')
            ) {
              throw new I18nError(
                lstrings.ramp_signup_failed_title,
                lstrings.ramp_signup_failed_account_existsmessage
              )
            }

            throw customerResponse.error
          }

This means we should always throw an InfiniteApiError from the HTTP response with no translations. Then we handle and translate errors in the workflows using I18nError.

This design is intentional. Localization strings are a GUI concern and ramp plugins are GUI plugins.

We already have asInfiniteErrorResponse why is this needed? It only seems needed cause we have a special handling for errors for localization? Well if we don't do localization here, then we can perhaps omit this additional cleaner?

Because the type differs from asInfiniteErrorResponse.

These HTTP errors were failing the cleaner previously in fetchInfinite so I was unable to catch it later as a recognized InfiniteApiError error to display the appropriate message. Previously, if fetchInfinite did not recognize the error, it only returns a generic Error with response.status, obfuscating the other required data.

Ah. I see.

So what we want is to extend asInfiniteErrorResponse with the new type information. It'd be a union of of the two shapes. Then we'd treat each shape the same (return a infinite error object).

We still want to move the special handling of the verify-otp error at the workflow level.

ExitError shows unfriendly message when user cancels OTP

Medium Severity

When the user cancels the OTP verification modal, an ExitError with the message "User cancelled OTP verification" is thrown from inside the onSubmit callback. This error is caught by RampKycFormScene's try/catch and displayed to the user via ErrorCard. The result is a non-localized, developer-facing message shown for a deliberate user action. ExitError is intended for graceful workflow exits (handled by handleExitErrorsGracefully), but here it's being caught by the form's error handler instead, causing poor UX.

User cancellation shows unexpected error in form

Medium Severity

When the user cancels OTP verification, ExitError is thrown inside the form's onSubmit callback. The RampKycFormScene catches all errors and displays them via ErrorCard. Since ExitError is not an I18nError, it triggers the generic "Unexpected error" message with a "Report Error" button. User cancellation is a normal flow and shouldn't show an error. The ExitError pattern expects errors to bubble up to handleExitErrorsGracefully in the plugin, but form scene error handling intercepts it first.

Hardcoded address country inconsistent with countryCode parameter

Low Severity

The address.country field is hardcoded to 'US' while the top-level countryCode parameter uses the dynamically passed value from request.regionCode.countryCode. This creates an inconsistency in the createCustomer API request where the top-level countryCode could differ from the nested address.country. If the ramp is extended to support other countries, this would cause the API request to have mismatched country values. The address.country should use the countryCode parameter instead of the hardcoded 'US' string.