- Sign a short-lived user JWT with the flow’s
scope. - Have the user’s browser POST it to
/auth/launchwith the flow’starget.
scope and target change between launches — the mechanism is identical and is documented once in JWT User Authentication.
Launch lives on the app host (
https://app.etherfuse.com, or https://sandbox.etherfuse.com in sandbox), not the API host. Prefer not to POST a form? Hand the credentials to the launch page over postMessage instead. Pass an optional return_url to send the user back to your app when they finish.Available launches
| Launch | scope | target | What the user does |
|---|---|---|---|
| Sign agreements | agreements | /agreements | Reviews and signs the three required agreements: electronic signature, terms and conditions, and customer agreement. |
| Business KYB | kyb | /kyb | Completes Know Your Business verification for a business. See the KYB guide for the full walkthrough. |
A launch’s JWT needs the matching
scope and nothing more — scope is strictly enforced, and any other value is rejected with invalid_scope. See Scopes.Sign agreements has one prerequisite: the customer agreement is generated from the customer’s identity (name, address, email), so submit their KYC identity first — for example via POST /ramp/customer/{id}/kyc — or let them fill any missing fields on the signing page. See Customer Onboarding (KYC). In sandbox, the customer is auto-approved once all three agreements are signed.