Apple Pay offers a frictionless payment experience in Safari based browsers on iOS and macOS. Apple Pay can be activated in the Optimize Administration and only requires a card acquiring agreement supporting Apple Pay.

Frisbii Payments Checkout determines if Apple Pay is supported for the browser and OS used, and presents Apple Pay as a payment method if no payment_methods argument has been given when creating the session, or applepay has been defined in the list of payment methods.

📘

Notice

Apply Pay does not allow to be run within an iframe, thus Apple Pay is only supported in a window mode.

To determine on the own site if Apple Pay is supported, the following SDK method can be used.

<script src="https://checkout.reepay.com/checkout.js"></script>

<script>
const isAvailable = Reepay.isApplePayAvailable();
// e.g. hide/show Apple Pay option
</script>

Liability shift

Apple Pay supports liability shift for American Express, Discover, JCB, Mastercard, and Visa cards issued in Europe. For non-European Visa cards, there is no liability shift for Apple Pay.

Liability shift means that the financial risk in case of fraud is put on the card acquirer or cardholder, instead of the merchant.

Apple Pay recurring

Apple Pay can also be used as a recurring payment method if enabled in the Configuration → Payment Methods section. A saved payment method can be obtained either by a recurring session or a charge session with the recurring flag set recurring=true.

To control the data shown by Apple Pay the following parameters can be given in the optional session_data object.

*- Only available for Version 2 agreements. See the notice below.

Checkout customization

⚠️

Notice

Full customization is currently experimental and only available for Version 2 agreements. Contact support if you want an early adoption of this feature.

When populating the above session_data fields for recurring payments or subscription sessions, the user will be presented with a screen similar to the one below. See legend below to customize your customer's experience.

• Setting text_on_statement when creating the session will populate fields [1] and [9]. In case it's missing, the display name set on the agreement will be used.
• applepay_recurring_trial_label will populate [2]. Defaults to Trial.
• applepay_recurring_trial_amount will populate [3]. Defaults to 0.00, which causes ApplePay to show Free.
• If both applepay_recurring_trial_label and applepay_recurring_trial_amount are missing, the trial line will be populated using information from the subscription plan. If missing, no trial will be shown.
• applepay_recurring_label will populate [5]. Defaults to Recurring.
• applepay_recurring_payment_start_date will populate [4] (effectively acting as a trial end date) and [6]. If missing, the start date will be the next period on the subscription.
• applepay_recurring_amount will populate [7]. Defaults to the subscription or subscription's plan amount, or Free in case of a recurring session.
• applepay_recurring_payment_interval_unit and applepay_recurring_payment_interval_count will populate the first half of [8]. Note that these fields are shared with the trial duration label [4]. Defaults to 1 month.
• applepay_recurring_payment_end_date will populate the second part of [8]. Defaults to the subscription's end date.
• The amount of the charge will populate [10]. In case there is no associated charge, this will show 0.00.