In the United States, there are no longer regulatory restrictions that require enrollment in an External Link Account Entitlement. The same applies to any similar program for linking to external payment flows. This is valid as long as the payment flow occurs outside the app itself. SFSafariViewController is, according to Apple’s documentation, a component that runs Safari in isolation from the host app. For this reason, it qualifies as an external browser, even when shown within the app’s interface. Apple states clearly in its documentation: “when you present this view controller, it must visibly present information to users. You may not hide or obscure the view controller…”. This means the primary requirement is user transparency. There is no restriction on using this component. Many of the largest companies in the industry, including major global platforms, use this exact model. They follow the same interpretation. Under current U.S. rules, SFSafariViewController meets the definition of an external browser. This allows the sale of digital goods without activating entitlement programs or incurring fees. These requirements still apply in Europe and other regions. Based on the current policy and the court ruling, it is allowed to use SFSafariViewController in the U.S. for selling goods outside of IAP. This is permitted as long as Apple’s key requirement is met: the user must clearly understand that they are interacting with a browser interface.

​
U.S. Compliance

To configure the checkout according to U.S. compliance guidelines, add the following to your code:
  • Set useExternalBrowser = true to open the checkout in the device’s default external browser, such as Safari.
  • Set useExternalBrowser = false to open the checkout using SFSafariViewController. This is also permitted in the U.S. and qualifies as an external browser.