Skip to main content

Recurring Authorizations

Use recurring authorizations when a payment workflow needs repeated merchant charges under explicit constraints. In the MCP surface this is handled by kleepay_recurring.

  1. Create or select a card for the workflow with kleepay_list_cards or kleepay_create_card.
  2. Allocate only the funds needed for the expected spend window with kleepay_wallet_allocate.
  3. Create a recurring authorization for the merchant, amount, cadence, and card with kleepay_recurring.
  4. Review active authorizations with kleepay_list_authorizations.
  5. Cancel the authorization when it is no longer needed with kleepay_cancel_authorization.

What to document for users​

For each recurring authorization, show:

  • merchant or workflow name
  • card used
  • maximum amount
  • billing cadence when known
  • expiration or review date
  • last charge and next expected charge
  • revoke action

Failure states​

Recurring payments can fail when:

  • the card has been paused in the dashboard
  • the card has insufficient allocated funds
  • the merchant is outside the authorization scope
  • the requested amount exceeds the configured ceiling
  • the authorization has expired or been revoked