[Feature] Allow specifying merchant code when initiating a payment

[acollins-wep]

Related Problem

The Web API supports specifying a merchant_code when creating a checkout, but this option is not available in the iOS SDK. This limitation makes it difficult to test payment flows against a sandbox merchant account when using a single profile with both production and sandbox environments.

Proposed Solution

Add support for a merchantCode parameter in the iOS SDK’s payment initiation flow, aligning it with the Web API capabilities.

Alternatives Considered

Using the Web API for sandbox testing instead of the iOS SDK. However, this prevents proper validation of the native mobile integration.

Additional Context

• API Reference – Create a Checkout — documents the merchant_code field available in the Web API

[giulio92]

Thank you for raising this.

However, this feature cannot be implemented due to the architectural design and hardware binding of the iOS SDK.

Unlike the Web API (which acts server-to-server), the iOS SDK tightly couples the merchantCode to the active authentication state of the application.

The merchantCode is determined globally upon a successful login via:

1. + (void)loginWithToken:(NSString *)token completion:(SMPCompletionBlock)block

2. + (void)presentLoginFromViewController:(UIViewController *)viewController
                                 animated:(BOOL)animated
                               completion:(SMPCompletionBlock)block;
   

Approach for Sandbox testing

To test multiple environments (Production vs. Sandbox), you should login using a dedicated Sandbox token/account during the authentication phase, rather than attempting to override the merchant code at the checkout level.