# apple-pay Published articles for apple-pay. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Managing Recurring Payments with Apple Pay Using PayPal DevFeed: [Managing Recurring Payments with Apple Pay Using PayPal]() Original publisher: [Read original article]() Author: PayPal Tech Blog Team Published: 2023-11-20T14:41:42Z Content type: article Language: en Sources: [PayPal Technology]() Topics: [SDKs](), [Mobile](), [Transactions](), [Authorization]() Tags: [apple](), [apple-pay](), [authorization](), [js-sdk](), [mobile-web](), [payments](), [subscriptions](), [token](), [transactions]() ### AI overview This article explains how merchants can support recurring payments with Apple Pay through PayPal's JS SDK and V3 Vault experience on mobile websites. It covers fixed or variable billing, consent details, authentication, transaction outcomes, and persistent tokens for future purchases. ### Source excerpt Recurring payments have become an integral part of the modern digital economy, offering convenience and predictability for both consumers and businesses. Our previous post highlighted different methods of integrating Apple Pay® with PayPal. This blog explores recurring payments using PayPal and Apple Pay, showing how using it can streamline transactions and benefits end users. How Recurring Payments with PayPal and Apple Pay Work A recurring payment is an agreement between a buyer and a merchant. It allows the merchant to charge the buyer's chosen payment instrument (typically a credit card) for a pre-approved amount at pre-approved intervals, which can be either fixed or variable. Consumers visiting a merchant's mobile website integrated with PayPal JS SDK and V3 Vault experience will find Apple Pay as one of the available payment methods for recurring payments. Once the consumer taps the Apple Pay button on the mobile website, the Apple Pay payment sheet is presented. This process mirrors the one-time Apple Pay experience for mobile web transactions. The merchant's website plays a crucial role in detailing the billing frequency and other terms of service. These details can also be reiterated on the payment sheet for added clarity. Recurring fees can take two forms: fixed amounts, such as monthly movie ticket subscriptions, or variable amounts like weekly grocery orders. The variability is subject to local authorizations. Depending on the specific merchant use case, customers may be presented with line items that reiterate billing frequency, discounts, and any additional upfront fees on the consent screen. To ensure transparency, the final payment amount is prominently outlined on the total line, making customers fully aware of the charge they are authorizing. The consumer can review the transaction details on the Apple Pay payment sheet. Once the consumer is ready, they authenticate using Face ID® or Touch ID®. When the transaction is complete, the consumer is sho ## The future of the App Store DevFeed: [The future of the App Store]() Original publisher: [Read original article]() Author: Marco Arment Published: 2021-09-13T21:18:11Z Content type: opinion Language: en Sources: [Marco.org]() Topics: [App](), [browser](), [Payment Fraud]() Tags: [apple](), [apple-pay](), [browser](), [fraud-prevention](), [payment](), [payment-fraud](), [processors]() ### AI overview An opinion article predicts that changes to Apple's App Store payment rules will preserve in-app purchases while allowing external purchase links. It argues that most apps will need to offer both options, with reader apps receiving an exemption, and that external payments could increase competition and enable new business models. ### Source excerpt After the dust settles from the developer class-action settlement, the South Korean law, the JFTC announcement, and the Apple v. Epic decision, I think the most likely long-term outcome isn't very different from the status quo -- and that's a good thing. Allowing external purchases Here's what I think we'll end up with: Apple will still require apps to use their IAP system for any qualifying purchases that occur in the apps themselves. All app types will be allowed to link out to a browser for other purchase methods. Most apps will be required to also offer IAP side-by-side with any external methods.1 Only "Reader apps" will be exempt from this requirement.2 Apple will have many rules regarding the display, descriptions, and behavior of external purchases, many of which will be unpublished and ever-changing. App Review will be extremely harsh, inconsistent, capricious, petty, and punitive with their enforcement.3 Apple won't require price-matching between IAP and external purchases. These few but important corrections reduce Apple's worst behavior and should relieve most regulatory pressure. The result won't look much different than the status quo: Most big media apps (qualifying as "reader" apps) won't offer IAP, but will finally be allowed to link to their websites from their apps and offer purchases there. Many games will offer both IAP and external purchases, with the external choice offering a discount, bonus gems, extra loot boxes, or other manipulative tricks to optimize the profitability of casino games for children (commissions from which have been the largest portion of Apple's "services revenue" to date). Most importantly, many products, services, and business models will become possible that previously weren't, leading to more apps, more competition, and more money going to more places. External purchase methods will evolve to be almost as convenient as IAP (especially if Apple Pay is permitted in this context), and payment processors will reduce the burd ## Streamline Checkout with Shipping Options in Apple Pay DevFeed: [Streamline Checkout with Shipping Options in Apple Pay]() Original publisher: [Read original article]() Author: Ajay Anandan Published: 2019-03-28T18:12:50Z Content type: release Language: en Sources: [Square Corner Blog - Medium]() Topics: [API](), [web applications](), [Web]() Tags: [api](), [apple-pay](), [applications](), [checkout](), [developer](), [ecommerce](), [payments](), [platform](), [square](), [update](), [web](), [web-development]() ### AI overview Square's Online Payments API now supports shipping options in Apple Pay on the Web. Developers can collect and validate shipping addresses, update shipping options, fees, taxes, line items, and totals during checkout, and receive the final shipping details after authorization. ### Source excerpt Use Apple Pay to Handle Selecting Shipping OptionsHeads up, we've moved! If you'd like to continue keeping up with the latest technical content from Square please visit us at our new home https://developer.squareup.com/blog A little over a year ago, we added support for Apple Pay on the Web in our Online Payments APIs to help developers easily integrate Apple Pay into their websites. However, we know eCommerce checkouts don't stop with payments -- you also need to collect additional details for fulfilling and shipping orders. Specifically, you need to collect a shipping address and offer different shipping options based on that address. You might provide a free shipping option and a paid shipping option, for those who need a faster delivery. Even though our Online Payments APIs supported collecting a shipping address from within Apple Pay, you had to handle shipping options outside the Apple Pay experience. With today's update, Square's API now supports the entire checkout experience for Apple Pay on the Web, including support for shipping options. You can take payments, ask for and validate the shipping address, and provide various shipping options, all within Apple Pay's web experience. This speeds up checkout, which in turn increases conversions, with easy to use checkout flows via Apple Pay on web. How Apple Pay Shipping Options Work:Add shipping options You can define any number of shipping options in the PaymentRequest object. The first shipping option will be the default value shown. https://medium.com/media/78471b15e4db3e80ebda3c7748597d30/hrefValidate a shipping address When your customer chooses a shipping address, the shippingContactChanged callback will be invoked. You can use this callback to validate the shipping address, add new fees and/or taxes based on the shipping address, and update the shipping options. Errors shown when a shipping address isn't supported by that merchantShipping options and taxes are updated when they choose a Canadian addressht