# cryptocard.la > REST API to issue and manage crypto-funded virtual cards. Two account types share the same API and base URL: no-KYC (you supply the cardholder's name directly) and KYC (onboard a real, identity-verified person first, then issue their card). Base URL: https://api.cryptocard.la. Auth: `Authorization: Bearer `. ## Docs - [API Reference](https://docs.cryptocard.la/): authentication, errors, idempotency, which path applies to your account, onboarding (KYC accounts), all card endpoints (create/get/list/freeze cards, update spend limits, one-time card number view, list/get transactions), webhooks, signature verification, and current limitations. - [Full reference, single file](https://docs.cryptocard.la/llms-full.txt): the same content as one plain-text document. ## Notes - API keys are issued during onboarding; email hello@cryptocard.la to request one. We tell you at that point whether your account is KYC or no-KYC. - Want to start integrating right away? Ask for a test key for our sandbox environment: https://api-sandbox.cryptocard.la — create real cards and try the whole flow before taking the next step. - Card creation never accepts or moves funds directly: spend limits are set server-side, funding happens by sending USDT/USDC to the card's on-chain `funding_address`. - On a KYC account, a card always belongs to a `user_id` whose KYC `status` is `approved` — there's no way to create a card without onboarding and approving its holder first. On a no-KYC account, you supply `holder_name` directly and skip onboarding entirely. - No-KYC accounts must send the cardholder's real `phone_country_code`/`phone_number`/`email` at card creation — used for 3-D Secure OTP delivery. Missing any of these three returns `invalid_fields`. - IDs (`card_id`, `user_id`, `tx_id`) are our own opaque identifiers, unrelated to any underlying card issuer. - Cards have four independent spend limits (daily/weekly/monthly/per-transaction), settable at creation and changeable anytime after with `PATCH /v1/cards/{card_id}/limits`.