provider: "kernel" to collect a user’s existing card for browser purchases. KERNEL manages the card vault integration; you don’t need a separate provider account or configuration.
Connect a card
- create a vault and a
walletitem withspec.provider: "kernel". the wallet isconnectedright away, with no cards and noaction.connectedmeans the wallet exists, not that it can pay. - invoke the wallet’s
add_payment_methodoperation. it returns a payment method inpending_enrollmentwith a single-usecard_enrollmentaction that expires after 30 minutes. - open the action’s
urlfor the cardholder in your trusted ui. the hosted page collects their card and email. for card entry on your own domain, pass the action’scapture_tokento embedded card capture instead. - retrieve the wallet with the
payment_methodsexpansion. the card is ready to pay when its method isactiveandcapabilities.single_use_card.eligibleistrue.
Make a purchase
- attach the vault when you create the browser.
- create a
carditem for the purchase, referencing the wallet and the merchant, amount, and currency, and setspec.payment_method_idto theidof the card that pays. visa cards also requiremerchant_country, the merchant’s two-letter country code. the purchase is bound to that card; see choose a card for a purchase. - invoke the advertised
authorizeoperation and complete any returned user action. keep action urls in your trusted user interface, outside the agent’s context. - when
fillappears inavailable_operations, fill the checkout, submit once, and verify the merchant’s order record. a completed fill isn’t proof of payment.
authorize takes no browser or page parameters when paying with the user’s own card.
the purchase’s
state.payment_method_id names the card it’s bound to, and state.funding_status reports whether that card can still pay. see check the card funding a purchase.
there’s no general standing approval or spending-limit setting across these paths. your application must verify purchase details before authorization. complete any returned user action and fill before the purchase’s expires_at.
Cards without network tokens
Cards without network tokens
fallback availability depends on the card and checkout. contact support before building on this path.where supported, the cardholder enters a fresh security code through a hosted action for each purchase. fill writes aliases that KERNEL resolves to the stored card details at browser egress. this path doesn’t issue a one-time network security code.the recorded amount and merchant details don’t restrict outgoing payment requests. an expiry or payment window isn’t a single-use guarantee. follow the returned actions and expiry; don’t treat this path as a standing spending authorization.
Reference
- enable payments in a browser agent: the controller, agent, fill, and checkout walkthrough.
- vault items api: request fields, eligibility, operations, and expiry.
- fill single-use cards: fill a card your backend or card issuer already has.
- pricing: vault limits and payment charges.