@onramper/onramper-react-native 1.2.2 → 1.3.0

package/CHANGELOG.md

@@ -2,6 +2,220 @@
 
 All notable changes to this project are documented in this file.
 
+## [1.3.0]
+
+Bundles the published, checksum-verified `OnramperSDK@1.3.0` for iOS.
+
+Most checkout changes in this release come from
+[OnramperSDK for iOS 1.3.0](https://github.com/onramper/onramper-ios/releases/tag/v1.3.0):
+MoonPay Apple Pay, pending payments, customer-facing errors, structured logging, and
+credential isolation. The React Native wrapper exposes these native capabilities in
+JavaScript and adds prepared-checkout cleanup and client-lifecycle fixes. The demo adds
+log-file management and checkout recovery.
+
+### Before you upgrade
+
+- **Handle the new error, state and event cases.** Update exhaustive switches for the
+  additions below. Keep `paymentPending` separate from completion and failure; an
+  accepted payment may still be settling.
+- **Previously signed-in users will sign in to OnramperID again.** The native SDK now
+  stores credentials separately by environment and removes the old shared entries once.
+  SDK session setup remains automatic; the next checkout requiring login presents
+  sign-in again.
+- **Rebuild the native app.** After updating the package, run `pod install` in your iOS
+  project and rebuild. A JavaScript-only update cannot replace the bundled iOS SDK.
+
+Existing checkout, prefill, button-rendering and session-refresh signatures are
+unchanged. Minimum React Native and iOS versions are unchanged.
+
+### Included from iOS SDK 1.3.0
+
+**MoonPay Apple Pay checkout.** When MoonPay is selected for an available Apple Pay
+quote, the native checkout button handles MoonPay's Frames flow: guest checkout or
+account onboarding, required payment disclosures, Apple Pay, and 3-D Secure verification
+when needed. Integrators continue rendering the returned `button`; no separate MoonPay
+WebView is required. The MoonPay sheet opens at a compact height and expands when the
+provider needs more room. Required disclosures appear next to the Apple Pay button and
+cannot be hidden. Coinbase and Paybis continue through the same API.
+
+**Pending-payment outcome and UI.** The native SDK distinguishes an accepted payment
+awaiting settlement from a completed payment. Its sheet shows **Payment processing**
+with the transaction ID; dismissing the sheet preserves the pending outcome.
+
+**Customer-facing errors and failure UI.** The native SDK supplies `userMessage` and
+`supportCode`, and distinguishes confirmed payment failure from a checkout-surface error
+with an unknown payment outcome. Its failure screen displays that copy and support
+code. **Try Again** closes the sheet and starts a fresh checkout. The RN API below
+exposes the same error categories and messages for the integrator's own UI.
+
+**Structured, sanitized logging.** The native SDK produces structured records and
+supports a custom log sink. HTTP paths use route templates, URLs are reduced to hosts,
+and sensitive-looking values are redacted. Native `errorDescription` and `debugInfo`
+also exclude URLs, response bodies, and tokens. Provider messages receive best-effort
+redaction, so exported logs may still contain personal data. Logging remains off by
+default; the RN wrapper forwards these native records to JavaScript.
+
+**Environment-specific credentials.** The native SDK now keeps credentials separate
+for development and production, preventing a session from carrying across environments.
+The one-time sign-in requirement is described above.
+
+### React Native API additions
+
+The following APIs expose the bundled native SDK's states, events, errors, logging, and
+provider metadata to JavaScript.
+
+**Pending-payment handling.** `OnramperState.kind` and `CheckoutEvent.type` now include
+`paymentPending`. It means payment was accepted but settlement is pending, and does not
+emit `completed`. Show a processing state and retain `currentTransactionId` to track the
+transaction through your backend and webhooks. Do not start another payment just because
+the first is pending.
+
+```ts
+client.addEventListener('paymentPending', () => {
+  showProcessing(client.currentTransactionId);
+});
+```
+
+**Customer-facing errors and support codes.** The JavaScript `OnramperError` now exposes
+the native SDK's `userMessage` for customer copy and `supportCode` for diagnostics.
+Existing `code`, `message` and `info` fields remain available. These fields are preserved
+across both failed events and rejected native SDK calls.
+
+```ts
+client.addEventListener('failed', ({ error }) => {
+  const failure = OnramperError.from(error);
+  showError(failure.userMessage, failure.supportCode);
+});
+
+try {
+  await client.getCheckoutRequirements(request);
+} catch (error) {
+  const failure = OnramperError.from(error);
+  showError(failure.userMessage, failure.supportCode);
+}
+```
+
+New JavaScript error codes mirroring iOS SDK 1.3.0:
+
+- `paymentFailed`: the provider confirmed the payment failed.
+- `providerFailed`: the checkout surface failed without confirming the payment outcome.
+  This does not prove that no payment was taken; follow `userMessage` and check
+  transaction status before offering another payment attempt.
+- `applePayNotConfigured`: Apple Pay needs to be set up on the device.
+
+`OnramperError.from()` supplies fallback customer copy and a support code for older or
+manually constructed payloads. The new fields are optional on `OnramperErrorPayload` to
+preserve compatibility with existing fixtures and callers.
+
+**Structured SDK logs in JavaScript.** Configure `logLevel` and an optional `logHandler`
+to receive native `OnramperLogRecord` values. Records contain a Unix-millisecond
+timestamp, level, category, event, string-valued context and formatted message. The RN
+bridge preserves native Console output while forwarding records to the callback.
+
+```ts
+const client = new OnramperClient({
+  apiKey,
+  clientId,
+  environment: 'production',
+  onSessionExpired,
+  logLevel: 'info',
+  logHandler: record => diagnosticStore.append(record),
+});
+```
+
+Library logging defaults to `off`. Callbacks run in JavaScript, stop after `destroy()`,
+and should do little work; callback exceptions do not interrupt checkout. Native
+sanitization is preserved; choose appropriate retention and sharing controls for your
+app's exported logs.
+
+**Provider lifecycle events and metadata.** The wrapper exposes the native SDK's new
+`challengeStarted`, `challengeCompleted` and `customerOnboardingRequired` events. These
+describe progress, not payment completion. Optional `QuoteResponse.providerContext` preserves JSON values,
+including executable flags and limits where supplied. `ProviderJSONValue` and
+`PaymentDisclosure` are exported types, and finalized data types the optional
+`providerBootstrap`. Provider metadata may contain tokens; avoid logging it or payment
+URLs.
+
+**Opt-in provider-event diagnostics.** The wrapper also exposes the native configuration
+flags: `isEventLoggingEnabled` enables SDK event telemetry to the BFF.
+`isEventConsoleLoggingEnabled` emits provider events at info level even when `logLevel`
+is lower. Both default to `false`.
+
+### React Native wrapper fixes
+
+- **Superseded quote preparations release abandoned buttons.** A newer preparation
+  invalidates older unmounted handles owned by that client, even if the newer request
+  fails. Superseded in-flight calls reject with `intentInvalidated`; ignore those when
+  waiting for the latest quote. Reset, sign-out and destruction clear owned handles, and
+  expired handles cannot mount. Other clients are unaffected. This cleans up local
+  views; it does not cancel a submitted payment or guarantee cancellation of a backend
+  request.
+- **Client destruction is safe and explicit.** Repeated `destroy()` calls are harmless.
+  Subsequent operations reject, and listener subscriptions throw, with the typed
+  `clientDestroyed` error instead of Nitro's `NativeState is null`. Late results, events
+  and logs cannot update a destroyed JS client. Unmount the old button and create a new
+  client to start another session.
+- **Native errors retain their context across Nitro.** Promise rejections preserve the
+  structured error code, customer message, support code and associated information,
+  matching failed-event payloads. Previously, exceptions could be reduced to a message
+  and classified as `unrecoverable`.
+
+### Demo app changes
+
+- The bare RN demo offers **Get a new quote** after a failure before finalization,
+  replacing the disabled Buy button while preserving login. It fetches fresh
+  requirements without automatically retrying payment. Failures after finalization
+  retain the native outcome sheet.
+- Pending payments appear separately from completion, and error displays use
+  customer-friendly messages and support codes.
+- Settings now lists daily UTC log files with previews, sizes, individual sharing and
+  confirmed deletion. Demo recording is on by default and respects a saved off choice.
+  Files are excluded from backups, capped at 5 MiB in total and pruned after seven days
+  during use. The event panel remains an in-memory view.
+- The Expo example demonstrates the new events, customer-facing errors and log callback.
+
+### Upgrading from stable 1.2.2
+
+This stable release also includes the self-sizing checkout button and demo improvements
+previously published in `1.2.2-1`. The native button reports its content height,
+including its Terms of Service text. Style the button's container; `cloneElement(button,
+{ style })` does not style the native button.
+
+Keep transaction webhooks configured for every provider and payment flow. In-app SDK
+events complement backend transaction tracking.
+
+### Known issue in the Expo example
+
+The Expo demo's native build on the tested Xcode 27 toolchain remains blocked by the
+existing `ExpoModulesJSI` compiler error in `JavaScriptRuntime.swift:219`: “a C function
+pointer can only be formed from a reference to a 'func' or a literal closure.” This was
+reproduced before these changes. Expo JavaScript tests and type checking pass; the bare
+RN app's Release build has been validated.
+
+[iOS SDK 1.3.0 changelog](https://github.com/onramper/onramper-ios/blob/master/CHANGELOG.md#130)
+· [React Native changes since 1.2.2-1](https://github.com/onramper/onramper-react-native/compare/v1.2.2-1...v1.3.0)
+
+## [1.2.2-1]
+
+Wrapper-only change; still bundles `OnramperSDK@1.2.2`.
+
+### Fixed
+
+- The native checkout button no longer draws over neighbouring views. It reports its content height
+  (for example when ToS text appears under the Buy button) and sizes itself to match, and clips any
+  overflow as a backstop.
+- A checkout button given an intent that has expired or was already used now shows nothing, instead of
+  keeping the previous quote's button on screen.
+
+### Changed
+
+- No public TypeScript type changes. Containers around `button` no longer need a `minHeight`.
+- `button` is now an element of a small sizing wrapper rather than the native view itself, and it
+  manages its own `style`. Style passed with `cloneElement(button, { style })` is no longer applied;
+  style the containing `View` instead.
+- The bare example app is now a demo app: environment switching, automatic SDK initialization,
+  currency / payment / country selection, and a settings sheet.
+
 ## [1.2.2]
 
 Bundles `OnramperSDK@1.2.2`.

package/README.md

@@ -19,7 +19,7 @@ Requires React Native 0.79+, `react-native-nitro-modules` 0.35+, the **New Archi
 { "expo": { "plugins": ["@onramper/onramper-react-native"] } }
 ```
 
-The plugin applies the required iOS build flag (it does not change your deployment target). Set your app's deployment target to **16.4+** — Expo SDK 56's own minimum (bare RN only needs 16.0). For bare-RN Podfile setup (Xcode 16+/26) and full details, see the [integration guide](docs/INTEGRATION.md).
+The plugin applies the required iOS build flag (it does not change your deployment target). Set your app's deployment target to **16.4+** — Expo SDK 56's own minimum (bare RN only needs 16.0). For bare-RN Podfile setup (Xcode 16+/26) and full details, see the [integration guide](docs/GETTING_STARTED.md).
 
 ## Quick start
 
@@ -56,7 +56,7 @@ return (
 );
 ```
 
-The button renders natively and presents login + payment sheets internally. ToS is rendered inside the button view.
+The button renders natively and presents login + payment sheets internally. ToS is rendered inside the button view, and the button sizes its own height to fit it — don't give its container a fixed height.
 
 Already know the user? Pass a third `prefill` argument (`email`, `firstName`, `lastName`, `phoneNumber` — all optional) to have the OnramperID screens arrive pre-populated. It's best-effort and never blocks sign-in. See [prefilling known user values](docs/GETTING_STARTED.md#prefilling-known-user-values) — note the caveat on `email` before supplying it.
 
@@ -65,6 +65,8 @@ Already know the user? Pass a third `prefill` argument (`email`, `firstName`, `l
 The SwiftUI `OnramperCheckoutButton` does not expose external callback hooks; checkout outcomes flow via the module-level event stream:
 
 ```ts
+import { OnramperError } from '@onramper/onramper-react-native';
+
 const onFinalized = client.addEventListener('checkoutFinalized', ({ response }) => {
   // Durable transaction identifier: store this for support/reconciliation.
   persistTransactionId(response.onramperTransactionId);
@@ -75,7 +77,8 @@ const unsub = client.addEventListener('completed', (e) => {
 });
 
 const onFailed = client.addEventListener('failed', (e) => {
-  console.log('failed:', e.error.code, e.error.message);
+  const failure = OnramperError.from(e.error);
+  showError(failure.userMessage, failure.supportCode);
 });
 ```
 
@@ -83,6 +86,12 @@ const onFailed = client.addEventListener('failed', (e) => {
 `onramperTransactionId` identifies the transaction and is available before payment rendering.
 `client.currentTransactionId` mirrors the same value; `reset()` clears it.
 
+`paymentPending` means accepted but awaiting settlement. Show processing and track
+`currentTransactionId`; do not treat it as completion or automatically restart payment.
+The native button also handles MoonPay onboarding and 3-D Secure. Observe
+`customerOnboardingRequired`, `challengeStarted`, and `challengeCompleted` for progress.
+These events do not establish payment success. All flows still require backend webhooks.
+
 ## Error handling
 
 All native errors arrive as `OnramperError` with a typed `code`:
@@ -103,8 +112,41 @@ try {
 }
 ```
 
+Use `error.userMessage` for customer copy and `error.supportCode` for support.
+`paymentFailed` confirms payment failure; `providerFailed` does not confirm the
+payment outcome. The same fields survive native Promise rejections and failed events.
 Full code list in `src/errors.ts`.
 
+## Client lifecycle
+
+Each client keeps only its latest unmounted checkout button. A new
+`getCheckoutRequirements()` call, `reset()`, or `signOut()` invalidates older
+preparations; an in-flight request that becomes obsolete rejects with
+`intentInvalidated`. When replacing a quote, remove the previous button and
+ignore that obsolete request's rejection while waiting for the current request.
+Do not treat it as a payment failure. Other clients are unaffected.
+
+Call `destroy()` when disposing of a client and unmount its checkout button.
+Repeated destruction is safe. Further operations reject with `clientDestroyed`;
+new listener subscriptions throw the same typed error. Pending results and late
+callbacks cannot update the destroyed JS client. Create a new `OnramperClient`
+to start again; calling `initialize()` on a destroyed instance does not revive it.
+
+These rules release local prepared views; they do not cancel an already submitted
+payment or guarantee cancellation of a request already sent to the backend.
+
+## Diagnostic logs
+
+Pass `logLevel: 'info'` (or `'debug'`) and `logHandler: record => yourStore.append(record)`
+to receive structured `OnramperLogRecord`s in JavaScript. Native Console output is
+preserved. Logging defaults to off; storage and export are owned by your app.
+The bare demo records by default: Settings → Diagnostic logs lists daily files
+with previews, individual sharing, and confirmed deletion.
+See [debugging](docs/DEBUGGING.md) for the record shape and retention guidance.
+
+For migration details, including new enum cases and one-time OnramperID sign-in,
+see [1.3.0 release notes](CHANGELOG.md#130).
+
 ## Versioning
 
 `@onramper/onramper-react-native@X.Y.Z` always bundles `OnramperSDK@X.Y.Z` (iOS). Wrapper-only patches are published as `X.Y.Z-N` pre-releases (`npm install @onramper/onramper-react-native@next` to opt in).
@@ -120,6 +162,6 @@ The vendored `OnramperSDK.xcframework` already ships its own `PrivacyInfo.xcpriv
 ## Troubleshooting
 
 - **`pod install` fails finding the xcframework** — confirm `node_modules/@onramper/onramper-react-native/ios/Frameworks/OnramperSDK.xcframework/` exists.
-- **Bare RN build fails with `module map file ... not found` (Xcode 16+/26)** — disable explicit Swift modules in your `Podfile` `post_install` (`SWIFT_ENABLE_EXPLICIT_MODULES = NO`). Expo apps get this automatically via the config plugin. See the [integration guide](docs/INTEGRATION.md).
+- **Bare RN build fails with `module map file ... not found` (Xcode 16+/26)** — disable explicit Swift modules in your `Podfile` `post_install` (`SWIFT_ENABLE_EXPLICIT_MODULES = NO`). Expo apps get this automatically via the config plugin. See the [integration guide](docs/GETTING_STARTED.md).
 - **App Attest errors in simulator** — expected. App Attest only works on real devices. The SDK surfaces this as `attestationFailed`.
 - **Buttons appear but sheets don't open** — the host RN screen must be inside a normal `UIViewController` (the default). Modal-presented screens may need extra care; report an issue with a repro.

package/ios/Frameworks/OnramperSDK.xcframework/ios-arm64/OnramperSDK.framework/Modules/OnramperSDK.swiftmodule/arm64-apple-ios.swiftinterface

@@ -9,12 +9,14 @@ import Foundation
 import Foundation/*.Bundle*/
 import Foundation/*.ProcessInfo*/
 import Foundation/*.URL*/
+import PassKit
 import Security
 import Swift
 import SwiftUI
 import UIKit
 import WebKit
 import _Concurrency
+import _PassKit_SwiftUI
 import _StringProcessing
 import _SwiftConcurrencyShims
 import _WebKit_SwiftUI
@@ -33,6 +35,24 @@ extension OnramperSDK.ToSRequirement {
   public func consentSentencePlainText(buttonLabel: Swift.String) -> Swift.String?
   #endif
 }
+public struct OnramperLogRecord : Swift.Sendable, Swift.Equatable {
+  public let timestamp: Foundation.Date
+  public let level: OnramperSDK.LogLevel
+  public let category: Swift.String
+  public let event: Swift.String
+  public let context: [Swift.String : Swift.String]
+  public var message: Swift.String {
+    get
+  }
+  public init(timestamp: Foundation.Date = Date(), level: OnramperSDK.LogLevel, category: Swift.String, event: Swift.String, context: [Swift.String : Swift.String])
+  public static func == (a: OnramperSDK.OnramperLogRecord, b: OnramperSDK.OnramperLogRecord) -> Swift.Bool
+}
+public typealias OnramperLogHandler = @Sendable (OnramperSDK.OnramperLogRecord) -> Swift.Void
+public enum OnramperLog {
+  public static let subsystem: Swift.String
+  public static let isVerboseBuild: Swift.Bool
+  public static let systemHandler: @Sendable (_ record: OnramperSDK.OnramperLogRecord) -> Swift.Void
+}
 public enum LogLevel : Swift.Int, Swift.Sendable, Swift.Comparable {
   case off
   case error
@@ -47,6 +67,14 @@ public enum LogLevel : Swift.Int, Swift.Sendable, Swift.Comparable {
     get
   }
 }
+extension OnramperSDK.OnramperError {
+  public var userMessage: Swift.String {
+    get
+  }
+  public var supportCode: Swift.String {
+    get
+  }
+}
 public enum OnramperError : Foundation.LocalizedError, Swift.Equatable, Swift.Sendable {
   case notInitialized
   case initializationFailed(Swift.String)
@@ -56,6 +84,7 @@ public enum OnramperError : Foundation.LocalizedError, Swift.Equatable, Swift.Se
   case networkError(code: Swift.Int, message: Swift.String)
   case decodingError(Swift.String)
   case timeout
+  case paymentFailed(Swift.String)
   case requirementNotSatisfied(Swift.String)
   case amountOutOfRange(min: Swift.Double, max: Swift.Double)
   case oidcFlowCancelled
@@ -65,6 +94,7 @@ public enum OnramperError : Foundation.LocalizedError, Swift.Equatable, Swift.Se
   case userTokenRefreshFailed(Swift.String)
   case webviewLoadFailed(Swift.String)
   case deepLinkFailed(Swift.String)
+  case providerFailed(Swift.String)
   case invalidRequest(field: Swift.String?, debugInfo: Swift.String?)
   case quoteUnavailable(debugInfo: Swift.String?)
   case checkoutForbidden(debugInfo: Swift.String?)
@@ -74,6 +104,7 @@ public enum OnramperError : Foundation.LocalizedError, Swift.Equatable, Swift.Se
   case deviceBlocked
   case securityStorageFailed(status: Swift.Int32)
   case securityTrustFailed(host: Swift.String)
+  case applePayNotConfigured
   #if compiler(>=5.3) && $NonescapableTypes
   public var errorDescription: Swift.String? {
     get
@@ -95,8 +126,12 @@ public enum CheckoutEvent : Swift.Sendable {
   case providerReady
   case paymentAuthorized
   case paymentProcessing
+  case paymentPending
   case paymentCancelled
   case providerError(reason: Swift.String)
+  case challengeStarted
+  case challengeCompleted
+  case customerOnboardingRequired
 }
 @_Concurrency.MainActor public protocol OnramperDelegate : AnyObject {
   @_Concurrency.MainActor func onramperClient(_ client: OnramperSDK.OnramperClient, didChangeState state: OnramperSDK.OnramperState)
@@ -123,12 +158,20 @@ public struct CheckoutFinalizeRequest : Swift.Codable, Swift.Sendable {
   public let onramperTransactionData: OnramperSDK.OnramperTransactionData
   public var requirementCompletions: [OnramperSDK.RequirementCompletion]?
   public var partnerContext: Swift.String?
+  public var providerBootstrap: OnramperSDK.ProviderBootstrapRequest?
   #if compiler(>=5.3) && $NonescapableTypes
-  public init(headlessCheckoutId: Swift.String, quote: OnramperSDK.QuoteResponse, encryption: OnramperSDK.EncryptedPayload, onramperTransactionData: OnramperSDK.OnramperTransactionData, requirementCompletions: [OnramperSDK.RequirementCompletion]? = nil, partnerContext: Swift.String? = nil)
+  public init(headlessCheckoutId: Swift.String, quote: OnramperSDK.QuoteResponse, encryption: OnramperSDK.EncryptedPayload, onramperTransactionData: OnramperSDK.OnramperTransactionData, requirementCompletions: [OnramperSDK.RequirementCompletion]? = nil, partnerContext: Swift.String? = nil, providerBootstrap: OnramperSDK.ProviderBootstrapRequest? = nil)
   #endif
   public func encode(to encoder: any Swift.Encoder) throws
   public init(from decoder: any Swift.Decoder) throws
 }
+public struct ProviderBootstrapRequest : Swift.Codable, Swift.Sendable {
+  public let publicKey: Swift.String
+  public let channelId: Swift.String
+  public init(publicKey: Swift.String, channelId: Swift.String)
+  public func encode(to encoder: any Swift.Encoder) throws
+  public init(from decoder: any Swift.Decoder) throws
+}
 public enum CompletionRequirementType : Swift.String, Swift.Codable, Swift.Sendable {
   case tos
   case privacyPolicy
@@ -171,7 +214,18 @@ public struct HeadlessCheckoutData : Swift.Codable, Swift.Sendable {
   public let checkoutPaymentType: OnramperSDK.CheckoutPaymentType
   public let url: Swift.String
   public let renderType: OnramperSDK.RenderType
-  public init(checkoutPaymentType: OnramperSDK.CheckoutPaymentType, url: Swift.String, renderType: OnramperSDK.RenderType)
+  public let providerBootstrap: OnramperSDK.ProviderBootstrapResponse?
+  #if compiler(>=5.3) && $NonescapableTypes
+  public init(checkoutPaymentType: OnramperSDK.CheckoutPaymentType, url: Swift.String, renderType: OnramperSDK.RenderType, providerBootstrap: OnramperSDK.ProviderBootstrapResponse? = nil)
+  #endif
+  public func encode(to encoder: any Swift.Encoder) throws
+  public init(from decoder: any Swift.Decoder) throws
+}
+public struct ProviderBootstrapResponse : Swift.Codable, Swift.Sendable {
+  public let framesBaseUrl: Swift.String?
+  #if compiler(>=5.3) && $NonescapableTypes
+  public init(framesBaseUrl: Swift.String? = nil)
+  #endif
   public func encode(to encoder: any Swift.Encoder) throws
   public init(from decoder: any Swift.Decoder) throws
 }
@@ -365,6 +419,22 @@ public struct EncryptedPayload : Swift.Codable, Swift.Sendable, Swift.Equatable
   public func encode(to encoder: any Swift.Encoder) throws
   public init(from decoder: any Swift.Decoder) throws
 }
+public struct QuoteQuery : Swift.Codable, Swift.Sendable {
+  public let headlessCheckoutId: Swift.String
+  public let onramperTransactionData: OnramperSDK.OnramperTransactionData
+  public let providerContext: OnramperSDK.QuoteProviderContext?
+  #if compiler(>=5.3) && $NonescapableTypes
+  public init(headlessCheckoutId: Swift.String, onramperTransactionData: OnramperSDK.OnramperTransactionData, providerContext: OnramperSDK.QuoteProviderContext? = nil)
+  #endif
+  public func encode(to encoder: any Swift.Encoder) throws
+  public init(from decoder: any Swift.Decoder) throws
+}
+public struct HeadlessQuoteResponse : Swift.Codable, Swift.Sendable {
+  public let quote: OnramperSDK.QuoteResponse
+  public init(quote: OnramperSDK.QuoteResponse)
+  public func encode(to encoder: any Swift.Encoder) throws
+  public init(from decoder: any Swift.Decoder) throws
+}
 public struct OnramperUserPrefill : Swift.Sendable, Swift.Equatable {
   public var email: Swift.String?
   public var firstName: Swift.String?
@@ -384,13 +454,42 @@ public struct QuoteResponse : Swift.Codable, Swift.Sendable, Swift.Equatable {
   public let networkFee: Swift.Double
   public let transactionFee: Swift.Double
   public let recommendations: [Swift.String]?
+  public let providerContext: OnramperSDK.QuoteResponseProviderContext?
   #if compiler(>=5.3) && $NonescapableTypes
-  public init(quoteId: Swift.String, ramp: Swift.String, rate: Swift.Double, payout: Swift.Double, paymentMethod: Swift.String, networkFee: Swift.Double, transactionFee: Swift.Double, recommendations: [Swift.String]? = nil)
+  public init(quoteId: Swift.String, ramp: Swift.String, rate: Swift.Double, payout: Swift.Double, paymentMethod: Swift.String, networkFee: Swift.Double, transactionFee: Swift.Double, recommendations: [Swift.String]? = nil, providerContext: OnramperSDK.QuoteResponseProviderContext? = nil)
   #endif
   public static func == (a: OnramperSDK.QuoteResponse, b: OnramperSDK.QuoteResponse) -> Swift.Bool
   public func encode(to encoder: any Swift.Encoder) throws
   public init(from decoder: any Swift.Decoder) throws
 }
+public typealias QuoteProviderContext = [Swift.String : Swift.String]
+public typealias QuoteResponseProviderContext = [Swift.String : OnramperSDK.ProviderJSONValue]
+public enum ProviderJSONValue : Swift.Codable, Swift.Sendable, Swift.Equatable, Swift.ExpressibleByStringLiteral {
+  case string(Swift.String), number(Swift.Double), bool(Swift.Bool), null
+  case array([OnramperSDK.ProviderJSONValue]), object([Swift.String : OnramperSDK.ProviderJSONValue])
+  public init(stringLiteral value: Swift.String)
+  #if compiler(>=5.3) && $NonescapableTypes
+  public var stringValue: Swift.String? {
+    get
+  }
+  #endif
+  public init(from decoder: any Swift.Decoder) throws
+  public func encode(to encoder: any Swift.Encoder) throws
+  public static func == (a: OnramperSDK.ProviderJSONValue, b: OnramperSDK.ProviderJSONValue) -> Swift.Bool
+  public typealias ExtendedGraphemeClusterLiteralType = Swift.String
+  public typealias StringLiteralType = Swift.String
+  public typealias UnicodeScalarLiteralType = Swift.String
+}
+public struct PaymentDisclosure : Swift.Codable, Swift.Sendable, Swift.Equatable {
+  public let code: Swift.String
+  public let version: Swift.String
+  public let contentMarkdown: Swift.String
+  public let contentHtml: Swift.String
+  public init(code: Swift.String, version: Swift.String, contentMarkdown: Swift.String, contentHtml: Swift.String)
+  public static func == (a: OnramperSDK.PaymentDisclosure, b: OnramperSDK.PaymentDisclosure) -> Swift.Bool
+  public func encode(to encoder: any Swift.Encoder) throws
+  public init(from decoder: any Swift.Decoder) throws
+}
 public enum TransactionType : Swift.String, Swift.Codable, Swift.Sendable {
   case buy
   case sell
@@ -490,6 +589,7 @@ public struct OnramperConfiguration : Swift.Sendable {
   public let environment: OnramperSDK.OnramperConfiguration.Environment
   public let theme: OnramperSDK.OnramperConfiguration.Theme
   public let logLevel: OnramperSDK.LogLevel
+  public let logHandler: OnramperSDK.OnramperLogHandler?
   public let isEventLoggingEnabled: Swift.Bool
   public let isEventConsoleLoggingEnabled: Swift.Bool
   public let sessionExpirationHandler: @Sendable () async throws -> OnramperSDK.SessionCredentials
@@ -517,7 +617,9 @@ public struct OnramperConfiguration : Swift.Sendable {
       get
     }
   }
-  public init(apiKey: Swift.String, clientId: Swift.String, environment: OnramperSDK.OnramperConfiguration.Environment = .production, theme: OnramperSDK.OnramperConfiguration.Theme = .system, logLevel: OnramperSDK.LogLevel = .off, isEventLoggingEnabled: Swift.Bool = false, isEventConsoleLoggingEnabled: Swift.Bool = false, sessionExpirationHandler: @escaping @Sendable () async throws -> OnramperSDK.SessionCredentials)
+  #if compiler(>=5.3) && $NonescapableTypes
+  public init(apiKey: Swift.String, clientId: Swift.String, environment: OnramperSDK.OnramperConfiguration.Environment = .production, theme: OnramperSDK.OnramperConfiguration.Theme = .system, logLevel: OnramperSDK.LogLevel = .off, logHandler: OnramperSDK.OnramperLogHandler? = nil, isEventLoggingEnabled: Swift.Bool = false, isEventConsoleLoggingEnabled: Swift.Bool = false, sessionExpirationHandler: @escaping @Sendable () async throws -> OnramperSDK.SessionCredentials)
+  #endif
 }
 public enum OnramperState : Swift.Sendable {
   case idle
@@ -529,6 +631,7 @@ public enum OnramperState : Swift.Sendable {
   case readyToCheckout
   case finalizing
   case rendering(OnramperSDK.OnramperState.RenderContext)
+  case paymentPending
   case completed
   case failed(OnramperSDK.OnramperError)
   public struct RenderContext : Swift.Sendable {