Charge a sub-account
Charge the client’s card on your connected Stripe account and add the minutes it buys to the sub-account’s wallet, at its client rate. Rebilling must be on. Between 10,000 per charge. A sub-account’s minutes come out of your agency wallet, so on a self-serve agency a charge that needs more minutes than your wallet holds tops your wallet up first by charging your own billing card. Two cards can therefore be charged by one call, and if the client’s card then fails, the top-up of your own wallet stands. When that top-up cannot be made, the call is refused before the client’s card is touched and nothing is changed.
The minutes come out of your wallet, at what they cost you. A self-serve agency without enough minutes is refused before the card is charged.
Charges a card now. Needs the billing:charge scope, which billing:write does not include, and an Idempotency-Key header: a retry with the same key returns the first answer instead of charging again. Not available over MCP.
Needs a plan that includes rebilling, and Stripe Connect connected for the agency, even when turning something off. Without either the call changes nothing and answers CAPABILITY_NOT_AVAILABLE (403) or STRIPE_NOT_CONNECTED (409).
Allowed customer roles: agency_admin. The agency is the one the credential belongs to.
Required API key scope: billing:charge.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Headers
Required. A unique value per purchase, 8 to 255 visible characters. Reuse it only to retry the same request; the retry returns the first answer with idempotentReplay: true and charges nothing. A declined card is an answer too: the retry replays the decline, so once the card is fixed, try again with a new key.
8 - 255Path Parameters
The sub-account's GoHighLevel Location ID.
1Body
The amount.
