Generates a presigned URL for customer onboarding. If the customer does not exist, it will be created.
This is the primary endpoint for creating customers. You generate a UUID for customerId and bankAccountId,
and Etherfuse will create the customer and bank account records associated with your organization.
Upon visiting the URL, the customer will have 15 minutes to complete the onboarding process (KYC verification and bank account linking).
This endpoint always creates a personal organization — it forces individual KYC.
There is no accountType field; pass business orgs through
POST /ramp/organization instead.
Pass userInfo with the end user’s email and display name. When provided, Etherfuse
pre-creates the user record so the customer’s eventual sign-in attaches to the right user
and we can email them on status changes (KYC approved/rejected, bank account verified, etc.).
userInfo is currently optional. It will become required in a future release — start
sending it now.
Documentation Index
Fetch the complete documentation index at: https://docs.etherfuse.com/llms.txt
Use this file to discover all available pages before exploring further.
API key for authentication. Pass the key directly (e.g., Authorization: your-api-key). Do not use a Bearer prefix.
Customer ID. This id is generated by you, the API consumer, and provided to etherfuse as a way to associate this customer with your organization.
Bank account ID. This id is generated by you, the API consumer, and provided to etherfuse as a way to associate this bank account with the customer.
Public key for the customer wallet
Blockchain type for the wallet
solana, stellar, base, polygon, monad Optional info about the end user (the individual customer behind a personal organization).
Recommended. When provided, Etherfuse pre-creates the user record so that when the customer eventually signs in via the hosted onboarding UI their Firebase identity attaches to the right user. It also enables personalized status-change emails (KYC approved/rejected, bank account verified, etc.).
Will eventually be required for personal organizations. Reject early in your integration if you don't have this data — partners that don't migrate before the cutover will start receiving 400 errors.
{
"email": "[email protected]",
"displayName": "Ana García"
}URL generated successfully
The generated presigned URL. This URL needs to be visited by the customer, and will be used to verify the customer's identity and bank account.