@amos.com/react-amos-js 0.6.0 → 0.7.0

package/README.md

@@ -262,7 +262,7 @@ function CheckoutGooglePay() {
 }
 ```
 
-`AmosApplePayButton` uses the same props and express-checkout callbacks. Drop it in the same place (or alongside Google Pay) with the same `amount`, `merchantName`, and `onInitiatePaymentIntentRequest` wiring. The SDK handles Apple Pay's temporary full-viewport iframe overlay for Chrome's QR handoff automatically.
+`AmosApplePayButton` uses the same props and express-checkout callbacks. Drop it in the same place (or alongside Google Pay) with the same `amount`, `merchantName`, and `onInitiatePaymentIntentRequest` wiring. On non-Safari browsers, Apple's QR handoff opens in a popup (`pay.apple.com`); Safari uses the native payment sheet.
 
 ### Saving a payment method with setup intent (credit card)
 
@@ -422,7 +422,7 @@ Renders the secure Google Pay iframe button (express checkout flow).
 
 Renders the secure Apple Pay iframe button (express checkout flow). Same props and callbacks as `AmosGooglePayButton`.
 
-The Apple Pay button and `ApplePaySession` run inside the Amos embed iframe, so only Amos domains need Apple merchant registration. When the embed needs Chrome's in-iframe QR handoff UI, it sends `EXPAND_IFRAME` and the SDK temporarily overlays that iframe full-viewport; `COLLAPSE_IFRAME` restores the button-sized layout. Merchants do not need to handle these messages themselves — they are part of the re-exported `@amos.com/amos-js` `Message` protocol and are handled automatically by `AmosApplePayButton`.
+Only Amos domains need Apple merchant registration. The button and `ApplePaySession` run inside the Amos embed iframe. On Safari, the native payment sheet is used; on other browsers, Apple's QR handoff opens in a popup (`pay.apple.com`).
 
 ### `formatGooglePayPaymentData({ paymentData })`
 
@@ -447,7 +447,6 @@ Re-exports of the same advanced helpers exposed by `@amos.com/amos-js`. Most int
 - **`ref` / `iframeRef`**: for card and bank forms, pass `ref={iframeRef}` to the form component. The same `iframeRef` must be used when calling `validateForm`, `confirmPaymentIntent`, or `confirmSetupIntent`. The component forwards the ref to the inner iframe.
 - **Same components for payment vs setup intents**: `AmosCreditCardPaymentMethodForm` and `AmosBankAccountPaymentMethodForm` support both payment intents and setup intents. The flow differs only by which server call you make and which confirmation function you use (`confirmPaymentIntent` vs `confirmSetupIntent`). You may optionally provide `onPaymentIntentConfirmationSucceeded` and/or `onSetupIntentConfirmationSucceeded`; the appropriate one is invoked based on the flow.
 - **Amount format**: for `AmosGooglePayButton` and `AmosApplePayButton`, `amount` is a string (e.g. `"5000"` for $50.00). For `components["schemas"]["CreatePaymentIntentInput"]` on the server, `amount` is a number in cents (e.g. `5000`).
-- **Apple Pay iframe overlay**: do not clip or trap the Apple Pay iframe in an overflow-hidden container that would prevent the SDK's full-viewport expand. During expand, the SDK sets the iframe to `position: fixed` covering the viewport and hides `document.body` overflow; avoid fighting that with competing fixed overlays of your own at a higher z-index.
 - **Going framework-free**: if you need to use Amos outside of React (vanilla JS, another framework, etc.), use [`@amos.com/amos-js`](../amos-js) directly.
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@amos.com/react-amos-js",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "main": "dist/index.js",
   "repository": {
     "type": "git",
@@ -46,8 +46,8 @@
     "vite-plugin-dts": "5.0.3"
   },
   "dependencies": {
-    "@amos.com/amos-js": "0.6.0",
-    "@amos.com/node": "0.1.31",
+    "@amos.com/amos-js": "0.7.0",
+    "@amos.com/node": "0.1.32",
     "@types/googlepay": "0.7.11"
   },
   "peerDependencies": {