Skip to content

Onboard the option's processor account

POST
/api/tenant/{tenantId}/PaymentOptions/{id}/onboarding
curl --request POST \
--url https://api.nimles.com/e-commerce/api/tenant/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/PaymentOptions/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/onboarding \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{ "returnUrl": "example", "refreshUrl": "example" }'

Connects the option’s processor account (e.g. a shop’s Stripe account): creates the account the first time, records it, and returns the processor’s onboarding page until the owner has completed it. Call again after onboarding to record that the account can take payments.

id
required
string format: uuid

The payment option.

tenantId
required
string format: uuid

Your tenant id.

Where the processor sends the owner back to.

Media typeapplication/json
object
returnUrl
string
nullable
refreshUrl
string
nullable

Example generated

{
"returnUrl": "example",
"refreshUrl": "example"
}

OK

Media typeapplication/json
object
fields
object
key
additional properties
string
data
object
connected
boolean
onboardingUrl
string
nullable

Example generated

{
"data": {
"connected": true,
"onboardingUrl": "example"
}
}

Unauthorized: no bearer token, or one that is expired or not for this API.

Forbidden: the caller holds no role that allows this action at this scope. The body is empty, or a problem whose detail names the action.

Media typeapplication/json

An RFC 9457 problem.

object
detail
string
nullable
instance
string
nullable
status
integer format: int32
nullable
title
string
nullable
type
string
nullable
key
additional properties

Example generated

{
"detail": "example",
"instance": "example",
"status": 1,
"title": "example",
"type": "example"
}

Not found: no such item in the tenant.

Media typeapplication/problem+json

An RFC 9457 problem.

object
detail
string
nullable
instance
string
nullable
status
integer format: int32
nullable
title
string
nullable
type
string
nullable
key
additional properties

Example generated

{
"detail": "example",
"instance": "example",
"status": 1,
"title": "example",
"type": "example"
}

Conflict: the item kept changing under concurrent writes; read it again and retry.

Media typeapplication/problem+json

An RFC 9457 problem.

object
detail
string
nullable
instance
string
nullable
status
integer format: int32
nullable
title
string
nullable
type
string
nullable
key
additional properties

Example generated

{
"detail": "example",
"instance": "example",
"status": 1,
"title": "example",
"type": "example"
}

Unprocessable: the body or the change is invalid. The errors are keyed by member.

Media typeapplication/problem+json

A validation problem: the messages by member (or by JSON Pointer for a patch).

object
errors
object
key
additional properties
Array<string>
status
integer format: int32
nullable
title
string
nullable
type
string
nullable
key
additional properties

Example generated

{
"errors": {
"additionalProperty": [
"example"
]
},
"status": 1,
"title": "example",
"type": "example"
}