@onramper/onramper-react-native 1.1.0 → 1.2.0

package/src/specs/OnramperNitro.nitro.ts

@@ -42,8 +42,11 @@ export interface OnramperNitro extends HybridObject<{ ios: 'swift' }> {
   // Fetches checkout requirements + quote, stores the SDK's SwiftUI checkout
   // button under a handle, and returns the handle + JSON-encoded quote. The
   // OnramperCheckoutButton Nitro view renders the stored button by handle.
-  // `requestJson` is a JSON CheckoutRequest; `styleJson` a JSON CheckoutButtonStyle.
-  getCheckoutRequirements(requestJson: string, styleJson: string): Promise<PreparedIntentResult>;
+  // `requestJson` is a JSON CheckoutRequest; `prefillJson` a JSON
+  // OnramperUserPrefill (`{}` when the caller supplied none); `styleJson` a JSON
+  // CheckoutButtonStyle. Argument order mirrors the SDK's
+  // `getCheckoutRequirements(_:prefill:buttonStyle:)`.
+  getCheckoutRequirements(requestJson: string, prefillJson: string, styleJson: string): Promise<PreparedIntentResult>;
   cancelPreparedIntent(intentHandle: string): Promise<void>;
 
   // Single native callback per stream; the JS wrapper fans out to multiple listeners.

package/src/types.ts

@@ -69,6 +69,31 @@ export interface QuoteResponse {
   recommendations?: string[];
 }
 
+// Mirrors Swift `OnramperUserPrefill`. Values you already know about the user,
+// used to pre-populate the OnramperID sign-in and additional-info screens.
+// Every field is optional — supply only what you know.
+//
+// Prefill is **best-effort and never blocks sign-in**: if it can't be applied,
+// the login flow opens without it. Nothing surfaces to your app, and there is
+// no error to handle.
+//
+// `email` is the *binding identity*, not merely another prefilled value. When
+// it matches the account that signs in, the remaining values may be applied
+// automatically; when it does not match, the whole prefill is dropped — which
+// is strictly worse than omitting `email`, where the values are still offered
+// to the user for confirmation. Supply it only when you're confident it's the
+// address the user will sign in with.
+//
+// Prefill is enabled per integration — talk to your Onramper representative
+// before relying on it.
+export interface OnramperUserPrefill {
+  email?: string;
+  firstName?: string;
+  lastName?: string;
+  /** E.164 format, e.g. `+3712345678`. Always a candidate — the user still verifies it. */
+  phoneNumber?: string;
+}
+
 export interface CheckoutButtonStyle {
   backgroundColor?: string; // hex #RRGGBB or #RRGGBBAA
   foregroundColor?: string;