Skip to main content
The widget is the offer experience for an external partner website. The signed-in Already business portal renders its own offer screen. A partner can place the widget in an iframe after Already provisions its publishable embed key and configures the permitted host origin. The iframe URL carries the publishable key as ?key=.... This key identifies the embed configuration and branding; it is not a partner API credential and does not authorize offer acceptance. The API validates the configured origin for embed configuration requests. Partner API keys must never appear in the iframe URL or browser JavaScript.

Sign-in options

The business can sign in inside the widget with a six-digit email code sent to a beneficiary email enrolled for that program. Where the business is already signed in to the Already portal, the portal can issue a short-lived, one-time widget handoff code scoped to the embed. The widget exchanges that code for its own verified session. A partner cannot create an authenticated business session with its server API key. The parent page and widget exchange readiness and handoff messages through postMessage; the receiver checks the message source and known parent origin. Only issue handoff codes from an authenticated business session. If your partner needs single sign-on from its own identity system, discuss an explicit trust and identity-mapping design with Already before implementation.

Offer behavior

The widget shows the exact published amount, fee, net proceeds, expiry, terms, and selected payout bank. The business must confirm the terms. Acceptance creates a payment request; the UI should distinguish accepted from provider-confirmed paid. The widget does not move money simply because the iframe loaded. For an embed key, host allowlisting, and a test obligation, contact your Already integration owner. See the payment flow and security controls.