@spring-payments/payments-react-native 0.1.0 → 0.1.1

package/README.md

@@ -19,7 +19,7 @@ For Expo SDK 57 / React Native 0.86:
 npx expo install @spring-payments/payments-react-native @stripe/stripe-react-native@0.64.0
 ```
 
-For a local pre-release build, run `npm ci && npm pack` in the package source directory, then install the resulting tarball with `npx expo install /path/to/spring-payments-payments-react-native-0.1.0.tgz @stripe/stripe-react-native@0.64.0`. Registry consumers do not need access to Spring's private repository. Use the compatible Stripe version above rather than assuming an arbitrary latest version is supported.
+The published npm package is the only supported partner distribution. Partners do not need access to Spring's private repository and should not copy source or install supplied tarballs. Use the compatible Stripe version above rather than assuming an arbitrary latest version is supported. Browser apps must likewise install `@spring-payments/payments-js` from npm; direct Gateway module imports and no-build integrations are not supported.
 
 Configure your dedicated return scheme, then create/rebuild your development app:
 
@@ -135,11 +135,17 @@ The dedicated return URL must be `<your-scheme>://safepay` in this SDK version:
 
 After process death there is no retained JS promise/session. Restore partner login, reconcile/replay the operation through `createSession`, and let Spring determine completion; URL arrival is not payment success. Partners remain responsible for consent to future off-session charges and prompting absent customers to return.
 
+## Spring-hosted payment recovery (preferred)
+
+For a customer returning to finish an existing payment, Spring's hosted browser recovery page remains the preferred option. This is a Spring-owned application, not a hosted SDK distribution. Embedded native card entry and in-app authentication still use this npm package.
+
+Send the customer to your authenticated web handoff page. Its backend authorizes the original payment and creates a **web** authentication session using the Gateway origin and `{gatewayOrigin}/payment-components/recover` as the return URL. The handoff submits `sessionId` and `sessionToken` in a browser form POST body to that page. Never put capabilities in a deep link, query string or fragment, and never send a native session to the web recovery page. A browser redirect or return to the app is not proof of payment; reconcile the original payment through your backend. Partners choosing in-app recovery instead can use `authenticatePayment(paymentId)` as described above.
+
 ## Verification
 
 `npm test` compiles against the actual RN/Stripe types and tests backend-confirmed completion, bounded pending, unknown submission/dismissal, scope mismatch, safe errors, replay/concurrent operations and plugin behavior. `npm pack` verifies the distributable includes compiled JS/types and the Expo plugin. Before release, verify fresh Expo installation and native builds on both platforms, actual card-only PaymentSheet (no saved cards/Link/wallets), issuer 3DS success/cancellation, app switching/process death, accessibility/text scaling and real Gateway webhook timing.
 
-Version 0.1.0 is an initial integration release, not certification of a live payment flow. iOS simulator Release build and styled/unstyled UI checks have passed; actual PaymentSheet/3DS with a configured backend and Android native verification remain outstanding. Complete those checks before a production integration.
+The 0.1.x releases are initial integration releases, not certification of a live payment flow. iOS simulator Release build and styled/unstyled UI checks have passed; actual PaymentSheet/3DS with a configured backend and Android native verification remain outstanding. Complete those checks before a production integration.
 
 ## License
 
@@ -147,7 +153,7 @@ MIT; see [LICENSE](./LICENSE). This license covers the Spring code in this SDK p
 
 ## Maintaining and publishing (Spring maintainers)
 
-Source of truth: `packages/spring-payments-react-native/` in the private `ktechgit/spring-payments` repository. Edit `src/`, `app.plugin.js` and this README here. `dist/` is generated; do not edit it. The repository's `examples/embedded-partner-expo/` is the integration consumer, not the package source.
+Source of truth: `packages/spring-payments-react-native/` in the private `ktechgit/spring-payments` repository. Edit `src/`, `app.plugin.js` and this README here. `dist/` is generated; do not edit it. The repository's `examples/embedded-partner-expo/` is the integration consumer, not the package source. Local tarballs below are for maintainer release validation only, not an alternative partner installation route.
 
 From this directory:
 
@@ -165,8 +171,8 @@ For subsequent releases, choose a semantic version and run `npm version patch --
 Authenticate interactively with `npm login --registry=https://registry.npmjs.org/`; confirm the account with `npm whoami` and its publish access to `@spring-payments`. Keep npm credentials in the maintainer/build environment only. With release authorization, publish the exact inspected tarball (replace the version in its filename):
 
 ```sh
-npm publish ./spring-payments-payments-react-native-0.1.0.tgz --access public --registry=https://registry.npmjs.org/
-npm view @spring-payments/payments-react-native@0.1.0 version license dist.integrity --registry=https://registry.npmjs.org/
+npm publish ./spring-payments-payments-react-native-0.1.1.tgz --access public --registry=https://registry.npmjs.org/
+npm view @spring-payments/payments-react-native@0.1.1 version license dist.integrity --registry=https://registry.npmjs.org/
 ```
 
 For a preview release, use a prerelease version and `--tag next`; do not move `latest` inadvertently. After registry verification, install the published version in the Expo demo, regenerate its lockfile, run its typecheck and Expo configuration check, and update partner installation instructions. An npm release does not deploy Gateway configuration, authorize a native application or complete device/processor certification.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spring-payments/payments-react-native",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "license": "MIT",
   "description": "Spring-managed native card saving and payment authentication",
   "publishConfig": {