Dashboard
APIResume Payment Request API - Recover a Checkout | BotSubscription
api.botsubscription.com
GET/v1/endpoint
AuthenticationBearer
Token
Stays in this tab. Required for this endpoint — the value below is what gets sent.
Examples
curl --request GET \
  --url https://api.botsubscription.com/v1/endpoint \
  --header 'Authorization: Bearer sk_live_•••'

Resume Payment Request - Recover an Interrupted Checkout via API

Re-open an existing hosted checkout when a customer closes their browser, loses the original payment link, or retries after the initial response is gone. BotSubscription checks the payment provider's current status first, so a payment that already completed always takes precedence over a stale checkout link—no second payment request is created.

Read status to determine whether a payment request is complete. An amount of "0" alone does not prove completion.

POST/v2/projects/{project_id}/payment-requests/{payment_request_id}/resume

Authorization

Bearer API KeyRequired

The response includes the payment-operation fields, not just a checkout URL and status. Customer identity and stored timestamps are available through Get Payment Request.

API key scope: payment-requests:add (required for restricted keys).

The request body and query string must both be empty.

Path Parameters

project_idstringrequired

The unique identifier of the project.

payment_request_idstringrequired

The unique identifier of the payment request to resume (UUID).

reused: true means the returned payment_url points to the same checkout session—render it, don't start a new flow. When the provider reports the request as already paid or expired, the response instead reflects that terminal status rather than a stale URL.

Last updated: