跳到主要内容

getCheckoutSetupUrl

StringWrapper getCheckoutSetupUrl(backUrl, successUrl)

GET /api/2.0/portal/payment/checkoutsetupurl

Get the checkout setup page URL

Hands back the hosted page on which a payment method is attached to the portal's billing account, for the case where money has to be taken later - a wallet top-up or an automatic one - rather than a plan bought now. A portal that already has a payment method on file answers with an empty result; a DocSpace administrator may ask for the page, but once the portal has a billing customer with an e-mail, only its payer may. The call itself changes nothing and may be repeated: the payment method is stored by the payment provider when the returned page is completed, after which GET api/2.0/portal/payment/customerinfo reports it as set. The URL is absolute, carries the caller's e-mail, the language of the request and the currency of the region, and redirects to successUrl or backUrl when the user finishes or cancels. It buys nothing - a plan is bought with PUT api/2.0/portal/payment/url.

Parameters​

NameInTypeDescriptionNotes
backUrlqueryURI (uri)The absolute address the setup page sends the user back to when attaching a payment method is abandoned. It has to be a well-formed URL and must be reachable by that user rather than by the portal.[required] [example: https://example.com/payment/back] [minLength: 0] [maxLength: 255]
successUrlqueryURI (uri)The absolute address the setup page sends the user to once the payment provider has stored the payment method. Reaching it means a method is now on file, which GET api/2.0/portal/payment/customerinfo confirms; nothing has been charged.[required] [example: https://example.com/payment/success] [minLength: 0] [maxLength: 255]

Responses​

Status codeDescriptionTypeResponse headers
200The absolute URL of the payment method setup page, or an empty result when the portal already has a payment methodStringWrapperX-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
400backUrl or successUrl is missing, does not start with http://, https:// or ftp://, or is longer than 255 characters--
403The caller is not a DocSpace administrator or, once a billing customer exists, not its payer; or the portal has no billing service configured--
401UnauthorizedErrorApiResponse-
429Too Many Requests.ErrorApiResponseRetry-After
500Internal Server Error.ErrorApiResponse-
502Bad Gateway. Returned by the reverse proxy, response body may be HTML and not JSON.--
503Service Unavailable. Returned by the reverse proxy, response body may be HTML and not JSON.--

Return type​

StringWrapper

Authorization​

Basic, OAuth2 (scopes: read, write), ApiKeyBearer, asc_auth_key, Bearer, OpenId

HTTP request headers​

  • Content-Type: Not defined
  • Accept: application/json