payment/stripeonboarding endpoint provides an interface for managing connected Stripe accounts for shops. It lets you create, view, update and delete these accounts. Additionally, the API generates onboarding links with return and refresh URLs. Access is protected by fine-grained permissions (read/write/create/delete); responses are returned as JSON.
Supported methods
List of all supported methods.Stripe onboarding process
Global parameters such as the operating mode are stored in thepayment.stripe configuration.
Data fields of an entry
Example
Example of rawResponse
Methods for Stripe onboarding
This section describes the endpoints for managing individual Stripe onboarding entries.GET payment/stripeonboarding
This endpoint can be used to load a list of existing onboarding entries for the current shop. Search and filter parameters from the request are taken into account and limited todeleted=false.
To use it, read permissions for Stripe onboarding data are required.
Example
Response
Error codes
GET payment/stripeonboarding/{id}
This endpoint can be used to load a single onboarding entry by its ID. To use this endpoint, read permissions for Stripe onboarding data are required.Example
Response
Error codes
POST payment/stripeonboarding
This endpoint creates a connected Stripe account and creates a local onboarding entry in live or sandbox mode. The result is an onboarding link (URL) through which the setup can be completed at Stripe. To use this endpoint, create permissions for Stripe onboarding data are required.Example
Request body
Response
Error codes
PUT payment/stripeonboarding/{id}
This endpoint updates an existing onboarding entry by its ID and distinguishes two meaningful use cases via thetype field in the request body:–
type = "finish": The entry is synchronized with the current state of the connected Stripe account. Submitted master data, ToS acceptance, payment enablement and payouts are checked and translated into an understandable status (e.g. “missing data”, “ToS not accepted”, “payments/payouts disabled” or “payouts enabled”). Additionally, email, capabilities, the default configuration of payment methods and the unchanged raw response are saved. The result is the updated entry as JSON.–
type = "refresh": A new onboarding link is created so that the merchant can seamlessly continue the setup at Stripe (e.g. after an interruption or when further details are required).
To use this endpoint, write permissions for Stripe onboarding data are required.
