You’ll need a Seismic API key (
client_id + client_secret). Your Seismic contact provisions this from the dashboard — the secret is shown only once.1
Get an access token
Exchange your API key for a short-lived bearer token.Send
Authorization: Bearer <access_token> on every subsequent request.2
Create an applicant
Applicants are the end-users (or businesses) who will hold cards.
cURL
3
Run identity verification (KYC)
Verify the applicant and wait for issuer readiness before issuing cards.Proceed only when
cURL
status is APPROVED and issuerKycReady is true. See the KYC integration guide for BYOK share tokens.4
Set up an account and cardholder
Your program and account are provisioned in the Seismic dashboard. Use those ids here, then turn the approved applicant into a cardholder.
cURL
5
Issue a card
cURL
GET /v1/cards/{id}/secure-details for a short-lived reveal token, then render the fields with Seismic Widget.js — raw card numbers never touch your servers. PCI DSS Level 1 orgs can use Method 2 instead. See Viewing card details.Next steps
Authentication
API keys and bearer tokens
Cards
Freeze, activate, and reveal card details
View PAN / CVV
Widget.js (Method 1) and server-side PCI reveal (Method 2)
KYC integration
Hosted verification, BYOK share tokens, and issuer readiness
API Reference
Card integration endpoints with a live playground