All four models drive the same backend order — minted once with
pulse.collectionSessions.create (see Create a session)
— and all four settle the same way: credit a customer only from a verified
disbursement.completed webhook, never from a client callback (see
Webhooks).
In-app component
Render
<PulseCheckout> directly in your React tree, driven by your API key — for trusted runtimes only.Embedded iframe (Tier A)
Mount the payment surface inside a Pulse-controlled iframe on your page, driven by a session token.
Hosted page (Tier B)
Redirect to a white-label, Pulse-hosted page you can serve from your own subdomain.
Headless / API (Tier C)
Build your own UI end to end against the order object — no Pulse-rendered surface at all.