Skip to main content
Request a scoped virtual card with a funding cap and optional issuer controls. The input accepts MCC filters and an expiry and passes them to the configured issuer integration. Those fields do not establish issuer enforcement. The funding cap must fit the tightest configured envelope amount cap. Consumer card controls separately reject merchant and category locks. Confirm the controls and status returned for the issued card.

Metadata

Annotations

Input schema

Output schema

Auth

Caller’s grant must include the cards:manage scope. Grants whose scope set is a superset of the required scope are accepted.

Request examples

Response examples

Success — card issued with one-shot details envelope:
Idempotent re-call (same idempotency_key) — details_envelope absent:
Funding cap exceeds the tightest envelope cap:

Errors

Step-up flow

cards.issue does not trigger inline step-up. It requires the card-management scope, an authorized vault and a funding cap within the configured envelope. Review the tool’s result and the card’s recorded status. For payments.initiate — which does trigger inline step-up — see the payments.initiate step-up flow.