Issue a Bond virtual card via the Bond API and retrieve card details securely
domain: bond.tech · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate using your Bond API key and customer ID in the Authorization header for all requests
Create a customer record via POST /customers with PII fields; Bond initiates identity verification through its KYC workflow automatically
Once the customer's KYC status reaches APPROVED, create a card account via POST /accounts linked to the customer ID
Issue a virtual card via POST /cards with the account_id and card_type VIRTUAL; the response returns a card_id but not the raw PAN
Retrieve sensitive card details (PAN, CVV, expiry) using the Bond SDK or secure iframe — raw card data is never returned in plain API responses to protect PCI scope
Embed the Bond card detail widget in your frontend to display card numbers to cardholders without your servers handling raw PAN data
Known gotchas
Bond never returns raw PAN or CVV in API responses — sensitive card details are only accessible via the Bond secure SDK or iframe to minimize PCI scope
Card accounts require a completed KYC workflow before issuance; attempting to create a card for a customer with a pending KYC status will fail
Bond is a BaaS wrapper — the underlying program bank imposes its own compliance requirements that Bond enforces; ensure your use case aligns with the program terms
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?