Test Apple Pay with Maestro on BrowserStack

Upload your app and test suite

Upload your app and your zipped Maestro test suite, then note the app_url and test_suite_url that each response returns. You need both values to start a build. For the upload commands, see Execute Maestro tests.

Add the BrowserStack executor script to your test suite

Maestro doesn’t use the WebDriver protocol, so Maestro flows have no JavaScript executor of the kind that Appium tests use. BrowserStack provides a script that your flow calls with the runScript command instead. If you already added this script for another scenario, such as biometric authentication, reuse the same file.

At the root of your test suite’s parent folder, create a folder named bstack and save the following script as browserstack_executor.js:

Your test suite now has the following structure:

sample_parent_folder/
├── bstack/
│   └── browserstack_executor.js
├── flow1.yaml
└── flow2.yaml

Don’t edit browserstack_executor.js. The script reads the values that BrowserStack sets on the test session. Everything that varies between calls comes from the env block in your flow.

Complete the Apple Pay payment from your flow

To complete an Apple Pay payment, your flow runs the following steps in order:

1. Optional: The prefill_apple_pay_detail action adds shipping, billing, or contact details to the payment.
2. Your flow opens the screen in your app that starts the Apple Pay payment.
3. The apple_pay_confirm action confirms the payment through the Apple Pay option in the AssistiveTouch menu. The action stops at Pay with Passcode and doesn’t enter the passcode.
4. Your flow taps each digit of the device passcode 123456 to complete the payment.
5. Your flow checks that your app responds to the completed payment.

The passcode prompt is a keypad, not a text field, so inputText doesn’t work. Tap each digit instead. Below iOS 26, tap each digit by its label.

The following flow completes an Apple Pay payment on a checkout screen on a device below iOS 26:

On iOS 26, the passcode keypad isn’t in the Maestro view hierarchy, so you can’t tap the digits by label. After the apple_pay_confirm step, wait for the keypad to appear, then tap each digit by its screen position with tapOn: point:. The positions differ between iPhone and iPad. Replace the apple_pay_confirm step and the passcode steps in the previous flow with the steps for your device:

The env block of each runScript step sets the following values:

• BROWSERSTACK_EXECUTOR_ACTION names the action to run. Use prefill_apple_pay_detail to add payment details and apple_pay_confirm to confirm the payment.
• DATA is a JSON string with the shipping, billing, or contact details. Only the prefill_apple_pay_detail action uses DATA.

Add payment details with the prefill action

If your checkout asks for a shipping address, billing address, or contact details, add a prefill_apple_pay_detail step before the step that opens the payment sheet. The prefill action adds the details through Settings > Wallet and then returns to the home screen, which closes an open payment sheet. Pass the details as a single-line JSON string in the DATA key of the env block. If your checkout doesn’t need these details, leave out the prefill step.

The DATA JSON takes the following objects. Include only the objects that your checkout needs:

The shippingDetails and billingDetails objects take the following fields:

The following JSON shows all three objects. Before you add it to your flow, remove the line breaks so that the JSON fits on one line inside the single quotes of the DATA value:

When you add payment details, make sure they meet the following conditions:

• Include only the address fields that apply to your test address. For example, if your address has no province, remove the province field.
• For the geographical code in each address, use only one of postalCode, postCode, or zip, based on what your address requires and the device accepts.
• Start the phone number with the country code and the + character. For example, +1-212-456-7890 or +12124567890.
• Set every value as a string.
• Use only the objects and fields listed in the previous tables. An unknown field or invalid JSON fails the prefill step with an invalid-argument error.

Run your test with Apple Pay

Set enableApplePay to true and resignApp to false when you start the build. Before your test starts, BrowserStack completes the following actions on the device:

• Sets a passcode on the device.
• Adds a sample test card to the Wallet app.
• Turns on AssistiveTouch.
• Adds Apple Pay to the AssistiveTouch menu.

The following table describes the Apple Pay parameters:

Check the result in your logs

Every call to browserstack_executor.js writes a status line to your Maestro logs. A successful call shows a line such as the following:

[EXECUTOR] action=apple_pay_confirm status=200

A failed call adds a reason to the same line and stops the flow. To read these lines, see Maestro logs.