Apple Pay

Apple Pay allows customers to complete Shoppable Ads purchases using Apple Pay directly within the Rokt placement. The Rokt SDK handles Apple Pay session creation, payment sheet presentation, and payment processing. The Rokt Catalog brand is the Merchant of Record (MoR).

Apple Pay is supported on web and iOS, with additional platform support planned.

Sequence overview

1. Placement loads. After the customer completes their transaction, the Rokt Shoppable Ads placement renders on the confirmation page.
2. Eligibility check. The Rokt SDK determines whether Apple Pay is available on the customer's device. If not supported, the placement falls back to other eligible payment methods (e.g., card forwarding).
3. Offer displayed. The placement displays the offer with the appropriate payment CTA based on available payment methods.
4. Customer taps "Pay with Apple Pay". The Apple Pay payment sheet is presented, showing item details, price (including tax and shipping), and the brand's merchant name.
5. Customer authorizes. The customer authenticates via Face ID, Touch ID, or device passcode.
6. Payment processed. Rokt processes the payment with the brand as MoR. A confirmation screen is displayed within the placement.
7. Placement closes. The partner's standard post-confirmation flow continues.

NOTE: If no eligible offer is available or no supported payment method is detected, the placement closes without displaying an offer.

Required attributes

Apple Pay uses the standard attributes passed during SDK initialization. For the full list, see the recommended attributes in the SDK Integration Guide.

The following attribute is used for Apple Pay payment method selection:

Attribute	Type	Required	Description
paymenttype	string	Yes	The payment method the customer used for their original transaction (e.g., visa, mastercard, amex, apple_pay, paypal). Rokt uses this to determine payment method priority. If the customer paid with Apple Pay, it is shown as the primary CTA.

NOTE: If your platform does not have shipping address details available (e.g., ticket or digital goods purchases), pass billing address details instead. Rokt will provide a UI for the customer to confirm or edit their shipping address before completing the purchase.

Web setup

Rokt manages domain registration, merchant configuration, and payment processing for Apple Pay end-to-end. Partners using the Joint SDK do not need any additional setup. Partners on the legacy SDK must enable the Apple Pay extension as described below.

SDK extensions (Legacy SDK only)

If you are using the legacy Rokt Web SDK (launcher.js), add payments-stripe-applepay to the extensions query parameter when loading the SDK script. If you also use card forwarding, include both extensions:

script.src = "https://apps.rokt.com/wsdk/integrations/launcher.js?extensions=instant-purchase,payments-stripe-applepay";

• payments-stripe-applepay - enables Apple Pay as a payment method on Shoppable Ads placements.
• instant-purchase - enables card forwarding as a payment method on Shoppable Ads placements.

NOTE: If you are using the Joint SDK (versions after 2.5926.0), extensions are enabled automatically and no script changes are required.

Browser and device compatibility

Browser	Platform	Apple Pay Support	Notes
Safari 17+	iOS 17+, macOS 12+	Supported	Native Apple Pay.
Safari (older)	iOS, macOS	Limited	Same-origin only.
Chrome	iOS	Supported	Apple Pay is device-based on iOS. Works the same as Safari.
Chrome	Desktop (macOS)	Not supported	Rokt falls back to other payment methods.
Chrome / Firefox	Windows, Android	Not supported	Rokt falls back to other payment methods.

Rokt automatically detects browser and device compatibility and will only display the Apple Pay button where it is supported. No additional gating logic is required from the partner.

NOTE: Shoppable Ads placements are typically rendered directly on the page, not within an iframe. This is required for Apple Pay to function correctly. If your integration renders the Rokt placement inside an iframe, contact your Rokt account manager to discuss additional configuration requirements.

iOS setup

To enable Apple Pay in your iOS app, install the Rokt PaymentKit module and configure Apple Pay entitlements. See the iOS SDK Integration guide for general SDK setup.

Step 1: Install PaymentKit

When adding the Rokt iOS SDK via Swift Package Manager, select both Rokt_Widget and Rokt_Payment_Kit as package products for your target.

https://github.com/ROKT/rokt-sdk-ios.git

Step 2: Configure Apple Pay entitlements

1. Register Merchant ID: In your Apple Developer portal, register the merchant ID merchant.com.rokt.payments.
2. Add Entitlement: In your Xcode project, enable the Apple Pay capability and add the merchant.com.rokt.payments merchant ID.
3. Payment Processing Certificate: Generate a Certificate Signing Request (CSR) from Stripe (Rokt will provide this). Upload the CSR to Apple to create a Payment Processing Certificate, and share the resulting .cer file with Rokt.

IMPORTANT: The merchant ID merchant.com.rokt.payments is Rokt's shared merchant identifier. Do not use your own merchant ID - the brand (MoR) processes the payment through Rokt's payment infrastructure.

Step 3: Register PaymentKit

After initializing the Rokt SDK (see iOS SDK Integration), register the PaymentKit:

import Rokt_Widget
import Rokt_Payment_Kit

Rokt.initWith(roktTagId: "<ROKT_TAG_ID>") { status in
    // Register PaymentKit for Apple Pay
    if let paymentKit = RoktPaymentKit(
        applePayMerchantId: "merchant.com.rokt.payments"
    ) {
        Rokt.registerPaymentKit(paymentKit)
    }
}

Checklist

Web

• If using the legacy SDK: payments-stripe-applepay added to the extensions query parameter
• paymenttype attribute passed on every Rokt experience launch
• End-to-end testing completed on Safari 17+ (iOS or macOS)

iOS

• Rokt_Payment_Kit added via Swift Package Manager
• merchant.com.rokt.payments registered in Apple Developer portal
• Apple Pay entitlement enabled in Xcode
• Payment Processing Certificate generated and shared with Rokt
• RoktPaymentKit registered after SDK initialization
• End-to-end testing completed on a physical iOS device