[Payments] Add IPP support for Puerto Rico

[iamgabrielma]

Closes: #14646

Description

As with the Android counterpart this PR adds IPP support for Puerto Rico by not blocking nor preventing to process a card payment in the mobile client when the store address is set to PR.

Testing information

• In wp-admin > WooCommerce > Settings. Set the store Country/State to Puerto Rico
• Attempt to process an IPP payment

I was unable to test the full payment flow due to zip code error despite trying multiple PR zip codes (00600, 00940, 00681), which I believe is expected without a fully-functional PR account setup in Stripe/WCPay (context p1737715359181589-slack-C025A8VV728).

Before the changes, we were blocked upon onboarding under a "non-supported country" error through in the client, after the changes we bypass this block and the invalidPostalCode (which I'm assuming we can only resolve with a fully-functional PR account) comes from the server:

Before	After

In the same nature, there is no specific /PR/ URL to acquire a card reader, upon navigating to Payments > Order Card Reader it will fallback to the M2 reader:

---

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Reviewer (or Author, in the case of optional code reviews):

Please make sure these conditions are met before approving the PR, or request changes if the PR needs improvement:

• The PR is small and has a clear, single focus, or a valid explanation is provided in the description. If needed, please request to split it into smaller PRs.
• Ensure Adequate Unit Test Coverage: The changes are reasonably covered by unit tests or an explanation is provided in the PR description.
• Manual Testing: The author listed all the tests they ran, including smoke tests when needed (e.g., for refactorings). The reviewer confirmed that the PR works as expected on all devices (phone/tablet) and no regressions are added.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce iOS by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce iOS
	Build Number	pr14972-7fa6956
	Version	21.4
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	7fa6956
	App Center Build	WooCommerce - Prototype Builds #12691

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[staskus]

Unfortunately, it doesn't work for me as well. I tried to:

• Change existing store address to Puerto Rico
• Create a new store with Puerto Rico address and onboard to WooPayments with Puerto Rico address

Both result in connection failures.

💳 Stripe Error Code: SCPError(rawValue: 9020)
💳 Card Reader Service Error: connection(underlyingError: Hardware.UnderlyingError.processorAPIError)
CoreData: debug: PostSaveMaintenance: incremental_vacuum with freelist_count - 9 and pages_to_free 1
🔵 Tracked card_reader_discovery_failed, properties: [is_wpcom_store: false, was_ecommerce_trial: false, plan: jetpack_free, site_url: https://obvious-toad-bobolink.jurassic.ninja, site_id: 241124518, country: PR, store_id: e783a36f-e98e-4cf2-ac73-bced35b3c4be, error_description: Sorry, this payment couldn’t be processed., connection_type: user_initiated, plugin_slug: woocommerce-payments, blog_id: 241124518]
🔵 Tracked card_reader_connection_failed, properties: [is_wpcom_store: false, was_ecommerce_trial: false, card_reader_model: STRIPE_M2, plan: jetpack_free, site_id: 241124518, site_url: https://obvious-toad-bobolink.jurassic.ninja, country: PR, store_id: e783a36f-e98e-4cf2-ac73-bced35b3c4be, error_description: The payment can not be processed by the payment processor., connection_type: user_initiated, plugin_slug: woocommerce-payments, blog_id: 241124518]

There could be an additional step missing to make it work 🤔

[iamgabrielma]

Thanks for testing, the 9020 seems to indicate an API error, but it's pretty generic. I'll take a further look 🤔

 /**
     The underlying request returned an API error.
     */
    SCPErrorStripeAPIError = 9020,

[wpmobilebot]

Version 21.7 has now entered code-freeze, so the milestone of this PR has been updated to 21.8.