Push a card into a Kernel wallet
Server-to-server enrollment of a card by its issuer. Post only to the card_ingest action URL that add_payment_method with enrollment server returned, never to the API host: that URL is served by the card vault, which replaces card.number and card.cvc with aliases before forwarding the request here, so Kernel never receives them. Requests that did not pass through the vault are refused. Authorization is Bearer with an API key of the wallet’s organization that may add payment methods to the wallet. The URL is single use and expires after 5 minutes. Retrying the request that enrolled the card (same card and the same last4, network, issuer_reference and valid_until) returns 200 with the payment method, until the card’s CVC is gone; after that the retry is refused and the card needs a new enrollment. The card’s CVC funds only its first purchase, which can pay without a cardholder CVC page; Kernel keeps it for at most an hour, or until valid_until if sooner, so the push, the authorization and the fill must all happen within that window. Kernel does not bind the card to a merchant or an amount: any API key that may use the vault can spend it while its CVC is valid, so the issuer sets the card’s limits. Request bodies are never logged.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
^[0-9]{4}$Card network
^[a-z][a-z_-]{0,31}$When the card stops being usable. Must be in the future.
The issuer's reference for the card
^[A-Za-z0-9._:-]{1,128}$Response
The card is stored and the payment method is active.