Invalid 11-Digit Account Validation

[SarahSync]

Describe the bug
The system successfully validates 11-digit account numbers (e.g., OPay phone numbers) on the Swap screen, even though the NUBAN standard only support 10 digits. This leads to transaction failures after the user has already been given a "Success" confirmation.

**Steps to reproduce **

1. Navigate to the Swap screen.
2. Select a Fintech provider (e.g., OPay or PalmPay) as the destination.
3. Input an 11-digit phone number (e.g., 08012345678) into the Account Number field.
4. Observe the validation response.

Expected behavior
The UI should prevent submission or show an error message: "Invalid account number. Please enter a 10-digit NUBAN." Validation should fail before the system attempts to resolve the account name.

Actual Result
The account is validated as "Successful," the account name is fetched (or the user is allowed to proceed), but the actual transaction fails at the point of execution.

Screenshots

Environment:

• All environments

Additional context
Add any other context about the problem here.