fix(manteca): handle TAX_ID_MISMATCH error code for Brazil CPF by Hugo0 · Pull Request #1619 · peanutprotocol/peanut-ui

Hugo0 · 2026-01-11T19:50:47Z

Problem

Brazilian users withdrawing via Manteca get a generic error instead of a user-friendly message when their bank account CPF doesn't match their identity.

Root Cause

Backend PR #533 only added CUIT (Argentina) mismatch detection. Brazil uses CPF, which wasn't handled. The backend is being updated to return TAX_ID_MISMATCH for both countries.

Changes

Update withdraw error handling to support both error codes:

TAX_ID_MISMATCH (new - covers Argentina CUIT + Brazil CPF)
CUIT_MISMATCH (old - backwards compatibility)

Also removed "In Argentina" from fallback message since it now applies to multiple countries.

Testing

Brazilian users should see user-friendly error for CPF mismatches
Argentine users continue to work as before
Old cached responses with CUIT_MISMATCH still handled correctly

Walkthrough

Extended Manteca withdraw error handling to treat TAX_ID_MISMATCH like CUIT_MISMATCH and updated the name-ownership mismatch user message to use a currency-based country label (ARS → Argentina, BRL → Brazil, otherwise generic) while preserving refund instructions.

Changes

Cohort / File(s)	Summary
Manteca Withdraw Error Handling `src/app/(mobile-ui)/withdraw/manteca/page.tsx`	Treat `TAX_ID_MISMATCH` as equivalent to `CUIT_MISMATCH`; change user-facing name-ownership mismatch message to select country label by currency (ARS → Argentina, BRL → Brazil, else generic) and retain refund guidance.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly addresses the main change: handling TAX_ID_MISMATCH error code to support Brazil CPF mismatch detection in the Manteca withdraw flow.
Description check	✅ Passed	The description clearly explains the problem, root cause, and changes related to supporting TAX_ID_MISMATCH for Brazilian CPF mismatch handling in the withdraw flow.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch fix/manteca-tax-id-mismatch-brazil

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Hugo0 · 2026-01-11T19:51:27Z

@coderabbitai review in depth.

coderabbitai

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/app/(mobile-ui)/withdraw/manteca/page.tsx (1)
242-257: Consider hardening mismatch messaging + de-duplicating error-code literals.

The new TAX_ID_MISMATCH || CUIT_MISMATCH handling matches the PR intent and the more generic fallback copy looks right (and aligns with the “prefer generic error messages for hotfixes” learning). Based on learnings, …

Two small improvements to consider:

If result.message can be a technical/backend string, you may want to always show the UI-owned copy for these mismatch codes (to keep it consistently user-friendly and language-consistent).

Extract the mismatch codes into a constant/set to reduce string-literal drift.
Proposed tweak
+const TAX_ID_MISMATCH_ERRORS = new Set(['TAX_ID_MISMATCH', 'CUIT_MISMATCH'] as const)

             if (result.error) {
                 // Handle specific error types with user-friendly messages
                 // TAX_ID_MISMATCH covers both Argentina (CUIT) and Brazil (CPF)
-                if (result.error === 'TAX_ID_MISMATCH' || result.error === 'CUIT_MISMATCH') {
+                if (TAX_ID_MISMATCH_ERRORS.has(result.error as any)) {
                     setErrorMessage(
-                        result.message ??
-                            'The bank account you entered is not registered under your name. You can only withdraw to accounts linked to your identity. Please contact support to request a refund.'
+                        'The bank account you entered is not registered under your name. You can only withdraw to accounts linked to your identity. Please contact support to request a refund.'
                     )
                     setStep('failure')
                 } else if (result.error === 'Unexpected error') {

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4bdd100 and e7a903a.

📒 Files selected for processing (1)

src/app/(mobile-ui)/withdraw/manteca/page.tsx

🧰 Additional context used

🧠 Learnings (9)

📓 Common learnings

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1094
File: src/components/AddWithdraw/DynamicBankAccountForm.tsx:279-279
Timestamp: 2025-08-14T08:02:26.705Z
Learning: For hotfixes in the peanut-ui codebase, prefer generic error messages over specific validation error details until the copy can be reviewed with the team, even when the validation functions return detailed error messages.

Learnt from: Hugo0
Repo: peanutprotocol/peanut-ui PR: 942
File: src/components/AddMoney/consts/index.ts:2151-2162
Timestamp: 2025-06-30T10:44:08.048Z
Learning: Hugo0 often agrees with refactoring suggestions but defers implementation due to time constraints, preferring to track improvements as follow-up issues when they're part of larger architectural changes.

📚 Learning: 2025-05-22T15:38:48.586Z

Learnt from: kushagrasarathe
Repo: peanutprotocol/peanut-ui PR: 869
File: src/app/(mobile-ui)/withdraw/page.tsx:82-88
Timestamp: 2025-05-22T15:38:48.586Z
Learning: The country-specific withdrawal route exists at src/app/(mobile-ui)/withdraw/[...country]/page.tsx and renders the AddWithdrawCountriesList component with flow="withdraw".

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-09-18T09:30:42.901Z

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1230
File: src/app/(mobile-ui)/withdraw/page.tsx:92-97
Timestamp: 2025-09-18T09:30:42.901Z
Learning: In src/app/(mobile-ui)/withdraw/page.tsx, the useEffect that calls setShowAllWithdrawMethods(true) when amountFromContext exists is intentionally designed to run only on component mount (empty dependency array), not when amountFromContext changes. This is the correct behavior for the withdraw flow where showing all methods should only happen on initial load when an amount is already present.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2024-11-18T21:36:11.486Z

Learnt from: jjramirezn
Repo: peanutprotocol/peanut-ui PR: 535
File: src/components/Claim/Claim.tsx:142-146
Timestamp: 2024-11-18T21:36:11.486Z
Learning: In `src/components/Claim/Claim.tsx`, external calls like token price fetching and cross-chain details retrieval are already encapsulated within existing `try...catch` blocks, so additional error handling may be unnecessary.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-11-06T08:19:05.201Z

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1407
File: src/components/AddWithdraw/DynamicBankAccountForm.tsx:459-475
Timestamp: 2025-11-06T08:19:05.201Z
Learning: In src/components/AddWithdraw/DynamicBankAccountForm.tsx, the street address field has a 35-character maximum length limit because the backend provider enforces this constraint, applicable to both US and Mexican addresses.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-08-26T15:25:53.328Z

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1132
File: src/app/[...recipient]/client.tsx:394-397
Timestamp: 2025-08-26T15:25:53.328Z
Learning: In `src/components/Common/ActionListDaimoPayButton.tsx`, the `handleCompleteDaimoPayment` function should not display error messages to users when DB update fails because the Daimo payment itself has succeeded - showing errors would be confusing since the payment was successful.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-06-22T16:10:53.167Z

Learnt from: kushagrasarathe
Repo: peanutprotocol/peanut-ui PR: 915
File: src/hooks/useKycFlow.ts:96-124
Timestamp: 2025-06-22T16:10:53.167Z
Learning: The `initiateKyc` function in `src/app/actions/users.ts` already includes comprehensive error handling with try-catch blocks and returns structured responses with either `{ data }` or `{ error }` fields, so additional try-catch blocks around its usage are not needed.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2024-10-25T11:33:46.776Z

Learnt from: jjramirezn
Repo: peanutprotocol/peanut-ui PR: 484
File: src/components/Cashout/Components/Initial.view.tsx:273-274
Timestamp: 2024-10-25T11:33:46.776Z
Learning: In the `InitialCashoutView` component (`src/components/Cashout/Components/Initial.view.tsx`), linked bank accounts should not generate error states, and the `ValidatedInput` component will clear any error messages if needed. Therefore, it's unnecessary to manually clear the error state when selecting or clearing linked bank accounts.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2024-10-07T15:28:25.280Z

Learnt from: jjramirezn
Repo: peanutprotocol/peanut-ui PR: 422
File: src/components/Request/Pay/Views/Initial.view.tsx:76-78
Timestamp: 2024-10-07T15:28:25.280Z
Learning: In `src/components/Request/Pay/Views/Initial.view.tsx`, both `txFee` and `utils.formatTokenAmount(estimatedGasCost, 3)` return strings, ensuring consistent return types for `calculatedFee`.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

GitHub Check: Deploy-Preview

coderabbitai · 2026-01-11T19:53:37Z

🧩 Analysis chain

@Hugo0, I'll perform an in-depth review of this PR. Let me gather the code changes first.

🏁 Script executed:

#!/bin/bash

# Get the list of changed files in the PR
gh pr view 1619 --json files --jq '.files[].path'

echo "---SEPARATOR---"

# Get the diff of the PR
gh pr diff 1619

Length of output: 1342

🏁 Script executed:

#!/bin/bash

# Read the full file to understand context better
cat src/app/\(mobile-ui\)/withdraw/manteca/page.tsx

echo "---FILE_SEPARATOR---"

# Search for other occurrences of CUIT_MISMATCH in the codebase
echo "=== Searching for CUIT_MISMATCH ==="
rg -n "CUIT_MISMATCH" --type ts --type tsx -C 2

echo "---SEARCH_SEPARATOR---"

# Search for TAX_ID_MISMATCH in the codebase
echo "=== Searching for TAX_ID_MISMATCH ==="
rg -n "TAX_ID_MISMATCH" --type ts --type tsx -C 2

echo "---SEARCH_SEPARATOR---"

# Search for manteca-related type definitions
echo "=== Searching for manteca error types ==="
rg -n "type.*error|interface.*error" --type ts --type tsx -g "*manteca*" -C 3

echo "---SEARCH_SEPARATOR---"

# Look for test files related to this component
echo "=== Looking for test files ==="
fd -e test.tsx -e test.ts -e spec.tsx -e spec.ts . | grep -i manteca

Length of output: 29773

🏁 Script executed:

#!/bin/bash

# Search for CUIT_MISMATCH and TAX_ID_MISMATCH more broadly
echo "=== Searching for CUIT_MISMATCH ==="
rg -n "CUIT_MISMATCH" -C 2

echo "---SEPARATOR---"

echo "=== Searching for TAX_ID_MISMATCH ==="
rg -n "TAX_ID_MISMATCH" -C 2

echo "---SEPARATOR---"

# Find manteca service/API files
echo "=== Finding manteca service files ==="
fd manteca -e ts -e tsx

echo "---SEPARATOR---"

# Read the manteca API service to understand return types
echo "=== Reading manteca API service ==="
cat src/services/manteca.ts 2>/dev/null || cat src/services/manteca/index.ts 2>/dev/null || echo "File not found"

echo "---SEPARATOR---"

# Look for manteca type definitions
echo "=== Searching for manteca types ==="
rg -n "interface.*Manteca|type.*Manteca" -A 10

echo "---SEPARATOR---"

# Search for other error handling patterns in the codebase
echo "=== Looking for similar error handling patterns ==="
rg -n "result\.error ===" -C 2 | head -50

Length of output: 43598

@Hugo0, I've completed an in-depth review of this PR. Here's my comprehensive analysis:

✅ Strengths

1. Backwards Compatibility

The OR condition (||) elegantly maintains support for both error codes, ensuring graceful handling of:

New backend responses with TAX_ID_MISMATCH
Cached/legacy responses with CUIT_MISMATCH
During backend deployment transition period

2. Improved User Experience

Removing "In Argentina" from the message is appropriate since both CPF (Brazil) and CUIT (Argentina) are tax IDs used for bank account identification, making the error message country-agnostic and scalable.

3. Clear Documentation

The inline comment at line 244 explicitly documents that TAX_ID_MISMATCH covers both countries, making the intent clear for future maintainers.

4. Proper Error Handling

Correctly prioritizes backend result.message over hardcoded fallback
Transitions to failure state appropriately
Provides user with recovery options (retry/support)

⚠️ Areas for Improvement

1. Type Safety Concerns

Issue: Error codes are magic strings without type safety.

// Current (from types/manteca.types.ts)
export type MantecaWithdrawResponse = {
    data?: MantecaWithdrawResponseData
    error?: string  // ❌ Any string is valid
    message?: string
}

Recommendation: Define error codes as constants or enum:

// types/manteca.types.ts
export const MANTECA_ERROR_CODES = {
    TAX_ID_MISMATCH: 'TAX_ID_MISMATCH',
    CUIT_MISMATCH: 'CUIT_MISMATCH',  // Deprecated
    UNEXPECTED_ERROR: 'Unexpected error',
    // ... other codes
} as const

export type MantecaErrorCode = typeof MANTECA_ERROR_CODES[keyof typeof MANTECA_ERROR_CODES]

export type MantecaWithdrawResponse = {
    data?: MantecaWithdrawResponseData
    error?: MantecaErrorCode
    message?: string
}

Then update the component:

if (result.error === MANTECA_ERROR_CODES.TAX_ID_MISMATCH || 
    result.error === MANTECA_ERROR_CODES.CUIT_MISMATCH) {
    // ...
}

Benefits:

Compile-time error detection
IDE autocomplete
Easier refactoring
Self-documenting code
Prevents typos

2. Missing Test Coverage

Issue: No test files found for this critical error handling path.

Recommendation: Add tests for:

describe('MantecaWithdrawFlow - Tax ID Mismatch Handling', () => {
  it('should handle TAX_ID_MISMATCH error', () => {
    // Test new error code
  })
  
  it('should handle CUIT_MISMATCH error (backwards compatibility)', () => {
    // Test legacy error code
  })
  
  it('should prioritize backend message over fallback', () => {
    // Test message priority
  })
  
  it('should display generic message when no backend message', () => {
    // Test fallback message
  })
})

3. Error Monitoring

Issue: No logging/monitoring for this specific error case.

Recommendation: Add error tracking:

if (result.error === 'TAX_ID_MISMATCH' || result.error === 'CUIT_MISMATCH') {
    // Add monitoring
    captureException(new Error('Tax ID mismatch during withdrawal'), {
        extra: {
            errorCode: result.error,
            country: countryPath,
            hasBackendMessage: !!result.message
        }
    })
    
    setErrorMessage(result.message ?? 'The bank account...')
    setStep('failure')
}

This helps track:

Frequency of tax ID mismatches by country
Backend message coverage
User pain points

4. Maintainability Concern

Issue: As more countries are added, the error handling could become complex.

Recommendation: Consider extracting error handling logic:

const handleWithdrawError = (
  result: MantecaWithdrawResponse, 
  countryPath: string
): { shouldFail: boolean; message: string } => {
  if (!result.error) return { shouldFail: false, message: '' }
  
  // Tax ID mismatch errors (country-agnostic)
  if (result.error === 'TAX_ID_MISMATCH' || result.error === 'CUIT_MISMATCH') {
    return {
      shouldFail: true,
      message: result.message ?? 
        'The bank account you entered is not registered under your name...'
    }
  }
  
  // Unexpected errors
  if (result.error === 'Unexpected error') {
    return {
      shouldFail: true,
      message: 'Withdraw failed unexpectedly. If problem persists contact support'
    }
  }
  
  // Generic errors
  return {
    shouldFail: false,
    message: result.message ?? result.error
  }
}

5. Backend Dependency

Observation: This change depends on backend PR #536 being deployed.

Questions:

Has the backend PR been merged and deployed?
Is there a feature flag controlling the new error code?
What happens if backend isn't updated yet? (Answer: Backwards compatibility handles this ✅)

📋 Testing Checklist

Before merging, verify:

Backend PR chore: run knip #536 is deployed
Brazilian users see friendly error for CPF mismatches
Argentine users still work correctly
Old cached responses with CUIT_MISMATCH handled
Backend message properly displayed when provided
Fallback message shown when backend doesn't provide one
Error is tracked in Sentry/monitoring
Support team is aware of the new error code

🎯 Implementation Quality

Overall, this is a well-executed change that:

✅ Solves the immediate problem (Brazil CPF support)
✅ Maintains backwards compatibility
✅ Improves user experience
✅ Follows existing patterns
✅ Is properly documented

The suggestions above are for future improvements to make the codebase more robust and maintainable as you expand to more countries.

Verdict: ✅ Approved

The implementation is correct and production-ready. Consider the type safety and testing recommendations as follow-up improvements.

🧠 Learnings used

Learnt from: Hugo0
Repo: peanutprotocol/peanut-ui PR: 823
File: src/context/kernelClient.context.tsx:79-86
Timestamp: 2025-04-29T19:36:38.121Z
Learning: When Hugo0 asks to "resolve coderabbit comments", they want to acknowledge the comment without necessarily implementing the suggested changes, as the current implementation might be intentional for their specific use case.

Learnt from: Hugo0
Repo: peanutprotocol/peanut-ui PR: 594
File: src/components/Request/Pay/Views/Initial.view.tsx:188-213
Timestamp: 2024-12-31T15:08:15.640Z
Learning: Always resolve coderabbit comments when reviewing code, since they can contain useful suggestions.

Learnt from: Hugo0
Repo: peanutprotocol/peanut-ui PR: 852
File: src/hooks/useTransactionHistory.ts:177-239
Timestamp: 2025-05-14T21:16:06.369Z
Learning: When reviewing code, pay attention to and resolve CodeRabbit comments as they can contain useful refactoring suggestions and insights.

Learnt from: Hugo0
Repo: peanutprotocol/peanut-ui PR: 942
File: src/components/AddMoney/consts/index.ts:2151-2162
Timestamp: 2025-06-30T10:44:08.048Z
Learning: Hugo0 often agrees with refactoring suggestions but defers implementation due to time constraints, preferring to track improvements as follow-up issues when they're part of larger architectural changes.

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1094
File: src/components/AddWithdraw/DynamicBankAccountForm.tsx:279-279
Timestamp: 2025-08-14T08:02:26.705Z
Learning: For hotfixes in the peanut-ui codebase, prefer generic error messages over specific validation error details until the copy can be reviewed with the team, even when the validation functions return detailed error messages.

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

… messages Update withdraw error handling: - Support both TAX_ID_MISMATCH (new) and CUIT_MISMATCH (old) error codes - Show country-specific message based on currency (Argentina/Brazil) - Clarify this is due to local regulations, not a Peanut limitation Related backend PR: peanutprotocol/peanut-api-ts#536

coderabbitai

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @src/app/(mobile-ui)/withdraw/manteca/page.tsx:
- Around line 258-261: The current else branch only calls
setErrorMessage(result.message ?? result.error) leaving the user on the review
screen with a disabled button; update that branch to also transition the flow to
the failure state by calling setStep('failure') so users see the same recovery
options ("Contact Support", etc.) as other failure paths—modify the code around
the existing setErrorMessage call (the else handling where result.message ??
result.error is used) to invoke setStep('failure') immediately after setting the
error message.

🧹 Nitpick comments (1)

src/app/(mobile-ui)/withdraw/manteca/page.tsx (1)
244-253: LGTM! Backwards-compatible error handling for Brazil CPF.

The implementation correctly handles both TAX_ID_MISMATCH and CUIT_MISMATCH error codes, dynamically derives the country name from the currency, and transitions to the failure state with appropriate messaging. The backwards compatibility ensures old cached responses continue to work.

As noted in the PR review, consider these follow-up improvements:
Add error monitoring: Track tax ID mismatch events with metadata for support analysis:
 if (result.error === 'TAX_ID_MISMATCH' || result.error === 'CUIT_MISMATCH') {
+    captureException(new Error('Tax ID mismatch detected'), {
+        extra: { errorCode: result.error, currency: currencyCode, hasBackendMessage: !!result.message }
+    })
     const countryName =
Type safety: Define error code constants to prevent typos and enable autocomplete:
// In constants file
export const MANTECA_ERROR_CODES = {
    TAX_ID_MISMATCH: 'TAX_ID_MISMATCH',
    CUIT_MISMATCH: 'CUIT_MISMATCH',
    // ...
} as const
Test coverage: Add unit tests for the error handling paths (both error codes, backend message priority, and fallback behavior).
Based on learnings, Hugo0 often agrees with architectural improvements but defers them due to time constraints—consider tracking these as follow-up issues.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e7a903a and fbe10d3.

📒 Files selected for processing (1)

src/app/(mobile-ui)/withdraw/manteca/page.tsx

🧰 Additional context used

🧠 Learnings (9)

📓 Common learnings

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1094
File: src/components/AddWithdraw/DynamicBankAccountForm.tsx:279-279
Timestamp: 2025-08-14T08:02:26.705Z
Learning: For hotfixes in the peanut-ui codebase, prefer generic error messages over specific validation error details until the copy can be reviewed with the team, even when the validation functions return detailed error messages.

Learnt from: Hugo0
Repo: peanutprotocol/peanut-ui PR: 942
File: src/components/AddMoney/consts/index.ts:2151-2162
Timestamp: 2025-06-30T10:44:08.048Z
Learning: Hugo0 often agrees with refactoring suggestions but defers implementation due to time constraints, preferring to track improvements as follow-up issues when they're part of larger architectural changes.

📚 Learning: 2025-05-22T15:38:48.586Z

Learnt from: kushagrasarathe
Repo: peanutprotocol/peanut-ui PR: 869
File: src/app/(mobile-ui)/withdraw/page.tsx:82-88
Timestamp: 2025-05-22T15:38:48.586Z
Learning: The country-specific withdrawal route exists at src/app/(mobile-ui)/withdraw/[...country]/page.tsx and renders the AddWithdrawCountriesList component with flow="withdraw".

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-09-18T09:30:42.901Z

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1230
File: src/app/(mobile-ui)/withdraw/page.tsx:92-97
Timestamp: 2025-09-18T09:30:42.901Z
Learning: In src/app/(mobile-ui)/withdraw/page.tsx, the useEffect that calls setShowAllWithdrawMethods(true) when amountFromContext exists is intentionally designed to run only on component mount (empty dependency array), not when amountFromContext changes. This is the correct behavior for the withdraw flow where showing all methods should only happen on initial load when an amount is already present.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-08-14T14:42:54.411Z

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1094
File: src/utils/withdraw.utils.ts:181-191
Timestamp: 2025-08-14T14:42:54.411Z
Learning: The countryCodeMap in src/components/AddMoney/consts/index.ts uses uppercase 3-letter country codes as keys (like 'AUT', 'BEL', 'CZE') that map to 2-letter country codes, requiring input normalization to uppercase for proper lookups.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-08-26T15:25:53.328Z

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1132
File: src/app/[...recipient]/client.tsx:394-397
Timestamp: 2025-08-26T15:25:53.328Z
Learning: In `src/components/Common/ActionListDaimoPayButton.tsx`, the `handleCompleteDaimoPayment` function should not display error messages to users when DB update fails because the Daimo payment itself has succeeded - showing errors would be confusing since the payment was successful.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2024-11-18T21:36:11.486Z

Learnt from: jjramirezn
Repo: peanutprotocol/peanut-ui PR: 535
File: src/components/Claim/Claim.tsx:142-146
Timestamp: 2024-11-18T21:36:11.486Z
Learning: In `src/components/Claim/Claim.tsx`, external calls like token price fetching and cross-chain details retrieval are already encapsulated within existing `try...catch` blocks, so additional error handling may be unnecessary.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-10-02T15:23:01.513Z

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1266
File: src/app/(mobile-ui)/withdraw/[country]/bank/page.tsx:46-57
Timestamp: 2025-10-02T15:23:01.513Z
Learning: In the withdraw flow at src/app/(mobile-ui)/withdraw/[country]/bank/page.tsx, the points calculation query intentionally uses crypto.randomUUID() in the queryKey dependency array to bypass React Query caching, ensuring fresh points estimates on every render. This is the intended behavior.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-11-06T08:19:05.201Z

Learnt from: Zishan-7
Repo: peanutprotocol/peanut-ui PR: 1407
File: src/components/AddWithdraw/DynamicBankAccountForm.tsx:459-475
Timestamp: 2025-11-06T08:19:05.201Z
Learning: In src/components/AddWithdraw/DynamicBankAccountForm.tsx, the street address field has a 35-character maximum length limit because the backend provider enforces this constraint, applicable to both US and Mexican addresses.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

📚 Learning: 2025-06-22T16:10:53.167Z

Learnt from: kushagrasarathe
Repo: peanutprotocol/peanut-ui PR: 915
File: src/hooks/useKycFlow.ts:96-124
Timestamp: 2025-06-22T16:10:53.167Z
Learning: The `initiateKyc` function in `src/app/actions/users.ts` already includes comprehensive error handling with try-catch blocks and returns structured responses with either `{ data }` or `{ error }` fields, so additional try-catch blocks around its usage are not needed.

Applied to files:

src/app/(mobile-ui)/withdraw/manteca/page.tsx

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

GitHub Check: Deploy-Preview

coderabbitai · 2026-01-11T20:01:22Z

src/app/(mobile-ui)/withdraw/manteca/page.tsx

+                    // @dev TODO: Should this call setStep('failure')? Currently user sees error on review
+                    // screen but withdraw button is disabled and there's no "Contact Support" option.
+                    // Funds are already at Manteca's address at this point.
                    setErrorMessage(result.message ?? result.error)


⚠️ Potential issue | 🟠 Major

Valid TODO: Inconsistent error flow leaves users without recovery options.

The TODO correctly identifies a UX issue: when a generic error occurs after funds have been sent to Manteca, users remain on the review screen with a disabled withdraw button and no "Contact Support" option, unlike the tax ID mismatch and "Unexpected error" paths that transition to the failure state with recovery actions.

This affects all non-specific error cases (e.g., rate limiting, temporary API failures). For consistency and better UX, the else branch should also transition to the failure state:

Suggested fix

} else { - // @dev TODO: Should this call setStep('failure')? Currently user sees error on review - // screen but withdraw button is disabled and there's no "Contact Support" option. - // Funds are already at Manteca's address at this point. setErrorMessage(result.message ?? result.error) + setStep('failure') }

This change is outside the scope of the tax ID mismatch fix but should be addressed to provide users with consistent recovery options. Would you like me to open a follow-up issue to track this improvement?

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

// @dev TODO: Should this call setStep('failure')? Currently user sees error on review

// screen but withdraw button is disabled and there's no "Contact Support" option.

// Funds are already at Manteca's address at this point.

setErrorMessage(result.message ?? result.error)

} else {

setErrorMessage(result.message ?? result.error)

setStep('failure')

}

🤖 Prompt for AI Agents

In @src/app/(mobile-ui)/withdraw/manteca/page.tsx around lines 258 - 261, The current else branch only calls setErrorMessage(result.message ?? result.error) leaving the user on the review screen with a disabled button; update that branch to also transition the flow to the failure state by calling setStep('failure') so users see the same recovery options ("Contact Support", etc.) as other failure paths—modify the code around the existing setErrorMessage call (the else handling where result.message ?? result.error is used) to invoke setStep('failure') immediately after setting the error message.

Hugo0 · 2026-01-11T20:02:26Z

@coderabbitai do a final review

coderabbitai bot reviewed Jan 11, 2026

View reviewed changes

vercel bot deployed to Preview – peanut-wallet January 11, 2026 19:54 View deployment

Hugo0 force-pushed the fix/manteca-tax-id-mismatch-brazil branch from e7a903a to fbe10d3 Compare January 11, 2026 19:58

vercel bot deployed to Preview – peanut-wallet January 11, 2026 20:01 View deployment

coderabbitai bot reviewed Jan 11, 2026

View reviewed changes

Hugo0 merged commit ffe7654 into peanut-wallet Jan 11, 2026
8 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(manteca): handle TAX_ID_MISMATCH error code for Brazil CPF#1619

fix(manteca): handle TAX_ID_MISMATCH error code for Brazil CPF#1619
Hugo0 merged 1 commit intopeanut-walletfrom
fix/manteca-tax-id-mismatch-brazil

Hugo0 commented Jan 11, 2026

Uh oh!

vercel bot commented Jan 11, 2026 •

edited

Loading

Uh oh!

coderabbitai bot commented Jan 11, 2026 •

edited

Loading

Uh oh!

Hugo0 commented Jan 11, 2026

Uh oh!

coderabbitai bot left a comment

Uh oh!

coderabbitai bot commented Jan 11, 2026

Uh oh!

coderabbitai bot left a comment

Uh oh!

coderabbitai bot Jan 11, 2026

Uh oh!

Hugo0 commented Jan 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

Hugo0 commented Jan 11, 2026

Problem

Root Cause

Changes

Testing

Related

Uh oh!

vercel bot commented Jan 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai bot commented Jan 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Uh oh!

Hugo0 commented Jan 11, 2026

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot commented Jan 11, 2026

✅ Strengths

1. Backwards Compatibility

2. Improved User Experience

3. Clear Documentation

4. Proper Error Handling

⚠️ Areas for Improvement

1. Type Safety Concerns

2. Missing Test Coverage

3. Error Monitoring

4. Maintainability Concern

5. Backend Dependency

📋 Testing Checklist

🎯 Implementation Quality

Verdict: ✅ Approved

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 11, 2026

Choose a reason for hiding this comment

Uh oh!

Hugo0 commented Jan 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

vercel bot commented Jan 11, 2026 •

edited

Loading

coderabbitai bot commented Jan 11, 2026 •

edited

Loading