Overview
TheinvokeIntent() method generates payment tokens (virtual card number, expiry, and CVV) from a previously registered intent. These are single-use credentials scoped to the mandate constraints — right merchant, right amount range, right time window.
No additional authentication required: The intent was already authorized with Passkey during registration. Invoking does not trigger another prompt.
Method Signature
Parameters
Return Value
Example
Flow Diagram
Payment Tokens Explained
Payment Tokens are single-use virtual card credentials generated from the card network. They’re scoped to the mandate constraints — right merchant, right amount range, right time window. If anything is out of bounds, the invocation fails.| Field | What it is |
|---|---|
pan | Virtual card number — use as card number at checkout |
expMonth / expYear | Token expiration date |
cvv | Single-use CVV — changes with every invocation |
Error Handling
| Code | Cause | Resolution |
|---|---|---|
INTENT_EXPIRED | Intent past its expiresAt date | Register a new intent |
INTENT_LIMIT_REACHED | useLimit exhausted | Register a new intent |
MANDATE_VIOLATION | Amount/merchant doesn’t match mandate | Check intent constraints |
CARD_NOT_FOUND | Card was removed | Re-enroll card and create new intent |
Security Considerations
Tokens are merchant-specific: The card network validates that the merchant receiving the payment matches the mandate. Mismatches will be declined.
Next Steps
Browser Automation
Execute checkout with tokens
Update Intent
Modify intent amount or limits