Seismic Card Issuance API

Before you can issue a card, every applicant must pass two checks. Seismic orchestrates both — you never integrate with the card program or identity vendors directly.

Layer	Who decides	API signal
Tenant KYC	You (the integrator)	`status` → `APPROVED`
Issuer KYC	The card program behind Seismic	`issuerKycReady` → `true`

status: APPROVED alone is not enough to issue cards. You must also wait for issuerKycReady: true. Card issuance returns ISSUER_KYC_INCOMPLETE otherwise.

What gets shared?

You never upload passports, selfies, or PDFs to Seismic. Identity providers support a share token — a short-lived credential that lets the card program pull an already-verified profile. Seismic accepts that token and forwards it upstream. Raw documents stay inside the identity provider.

Get your integration settings

cURL

curl -s 'https://api.seismic-cards.systems/v1/kyc/config' \
  -H 'Authorization: Bearer YOUR_TOKEN'

{
  "data": {
    "hostedVerificationAvailable": true,
    "shareVerificationAvailable": true,
    "shareRecipientId": "celeriz.com_139320",
    "sumsubWebhookMode": "seismic",
    "sumsubWebhookUrl": "https://api.seismic-cards.systems/v1/webhooks/sumsub",
    "verificationSync": "POST /v1/webhooks/sumsub on your Core API host, or POST /v1/applicants/{id}/submit to sync and hand off"
  }
}

Field	Meaning
`hostedVerificationAvailable`	You can use `POST /v1/applicants/{id}/kyc-session` and embed Seismic’s hosted widget
`shareVerificationAvailable`	BYOK share tokens are accepted via `kyc-share`
`shareRecipientId`	Seismic’s Sumsub client id — use as the share-token recipient in your identity provider (BYOK only). Never use the card-program or upstream partner id.
`sumsubWebhookMode`	`seismic` = Core API `/v1/webhooks/sumsub` (target); `seismic` = legacy Railway seismic-cards
`sumsubWebhookUrl`	Exact URL to register in the Sumsub dashboard for this environment

Sumsub webhooks (target): register Sumsub against the Core API URL from sumsubWebhookUrl (POST /v1/webhooks/sumsub). Set SUMSUB_WEBHOOK_MODE=seismic and PUBLIC_API_URL on the API host. After the hosted widget completes, call POST /v1/applicants/{id}/submit to sync tenant status and trigger issuer handoff (webhooks may also update status). Use GET …/kyc-status to poll issuer progress. Legacy seismic mode (/webhooks/sumsub on seismic-cards) is migration-only — see Webhooks.

Option A — Seismic-hosted verification

Best when you don’t run your own Sumsub (or similar) account. Seismic hosts the widget and handles issuer handoff automatically.

Create an applicant

cURL

curl -s -X POST 'https://api.seismic-cards.systems/v1/applicants' \
  -H 'Authorization: Bearer YOUR_TOKEN' -H 'Content-Type: application/json' \
  -d '{
    "type": "PERSON",
    "email": "jane@example.com",
    "data": {
      "firstName": "Jane",
      "lastName": "Doe",
      "country": "US",
      "addressLine1": "123 Main St",
      "city": "New York",
      "state": "NY",
      "postalCode": "10001"
    }
  }'

Start a verification session

cURL

curl -s -X POST 'https://api.seismic-cards.systems/v1/applicants/app_abc123/kyc-session' \
  -H 'Authorization: Bearer YOUR_TOKEN'

Response includes accessToken — pass it to the hosted WebSDK in your frontend. externalUserId is the Seismic applicant id.

User completes the widget

When verification succeeds in the widget, call POST /v1/applicants/{id}/submit to sync tenant status and trigger issuer handoff. With SUMSUB_WEBHOOK_MODE=seismic, Sumsub also posts to POST /v1/webhooks/sumsub on Core API — still call submit so issuer handoff is not delayed if the webhook is slow.

Confirm issuer readiness

cURL

curl -s 'https://api.seismic-cards.systems/v1/applicants/app_abc123/kyc-status' \
  -H 'Authorization: Bearer YOUR_TOKEN'

Wait until issuerKycReady is true, then create a cardholder and issue a card.

You can also call POST /v1/applicants/{id}/submit after the widget completes to poll tenant status and trigger issuer handoff in one step.

Option B — Bring your own identity provider (BYOK)

Best for regulated companies that already run their own Sumsub (or compatible) environment. You never use Seismic’s hosted widget.

Create an applicant in Seismic

Save the returned id — you will use it as externalUserId in your identity provider.

Verify the user in your provider

Run your existing KYC flow. Set externalUserId to the Seismic applicant id so records stay linked.

Generate a share token

Call your provider’s share-token API with:

Applicant id — from your provider
Recipient — shareRecipientId from GET /v1/kyc/config (Seismic’s id, not the card issuer)

Example (Sumsub):

POST /resources/accessTokens/-/shareToken?applicantId={id}&forClientId={shareRecipientId}

Seismic imports the shared verification and forwards it to the card program internally. The token expires quickly (typically ~10 minutes). Generate it immediately before calling Seismic.

Submit the token to Seismic

cURL

curl -s -X POST 'https://api.seismic-cards.systems/v1/applicants/app_abc123/kyc-share' \
  -H 'Authorization: Bearer YOUR_TOKEN' -H 'Content-Type: application/json' \
  -d '{
    "sumsub_share_token": "YOUR_SHARE_TOKEN",
    "kyc_vendor_ref": "your-provider-applicant-id",
    "status": "APPROVED"
  }'

Field	Required	Description
`sumsub_share_token`	Yes	Short-lived share token from your provider
`kyc_vendor_ref`	No	Your provider’s applicant id (stored internally)
`status`	Recommended	Set to `APPROVED` to attest verification in the same request

Poll until ready

cURL

curl -s 'https://api.seismic-cards.systems/v1/applicants/app_abc123/kyc-status' \
  -H 'Authorization: Bearer YOUR_TOKEN'

Issue cards only when issuerKycReady is true.

BYOK tenants do not need Seismic-hosted verification credentials. They only need a Seismic API key and the shareRecipientId from /v1/kyc/config.

Applicant response fields

Every applicant includes white-labeled issuer fields:

{
  "data": {
    "id": "app_abc123",
    "status": "APPROVED",
    "issuerKycStatus": "SUBMITTED",
    "issuerKycReady": false
  }
}

`issuerKycStatus`	Meaning
`PENDING`	Issuer account exists; identity not submitted yet
`SUBMITTED`	Share token forwarded; issuer processing
`APPROVED`	Issuer accepted identity — cards can be issued
`REJECTED`	Issuer declined identity
`UNKNOWN`	Could not determine status — call `kyc-status` to refresh

Endpoints summary

Method	Path	Purpose
`GET`	`/v1/kyc/config`	Integration settings + share recipient id
`POST`	`/v1/applicants`	Create applicant
`POST`	`/v1/applicants/{id}/kyc-session`	Hosted widget session (Option A)
`POST`	`/v1/applicants/{id}/submit`	Poll tenant KYC; when approved, provision issuer account and trigger handoff
`POST`	`/v1/applicants/{id}/kyc-share`	Submit BYOK share token (Option B)
`GET`	`/v1/applicants/{id}/kyc-status`	Poll issuer KYC fields only — does not submit share tokens

Troubleshooting

Symptom	Likely cause	Fix
`issuerKycReady` stays `false` after mock sandbox KYC	Mock verification does not produce real share tokens	Use hosted verification or BYOK share tokens against a live environment
`ISSUER_KYC_INCOMPLETE` on card issue	Issuer still processing or share token never submitted	Call `POST …/submit` or `kyc-share`, then poll `GET …/kyc-status` until `issuerKycReady` is `true`
Card issue fails with address / state error	Residential address in KYC is missing state (state of birth alone is not enough)	Re-run verification with full address including state/subdivision, then re-submit issuer handoff
Share token rejected	Wrong `shareRecipientId`, reusable KYC not enabled, or token not addressed to Seismic	Confirm `GET /v1/kyc/config` returns Seismic’s client id; ask Sumsub to enable sharing tenant → Seismic → issuer
`KYC_NOT_APPROVED` on `kyc-share`	Tenant status not approved	Include `"status": "APPROVED"` when attesting BYOK verification

See Error codes for the full list of error.code values.

Next steps

Applicants

Applicant lifecycle and statuses

Cards

Issue cards after issuer KYC is ready

Quickstart

End-to-end sandbox walkthrough

API Reference

Try endpoints in the playground

Get started

Core concepts

Reference

Identity verification (KYC)

What gets shared?

Get your integration settings

Option A — Seismic-hosted verification

Option B — Bring your own identity provider (BYOK)

Applicant response fields

Endpoints summary

Troubleshooting

Next steps

Applicants

Cards

Quickstart

API Reference

​What gets shared?

​Get your integration settings

​Option A — Seismic-hosted verification

​Option B — Bring your own identity provider (BYOK)

​Applicant response fields

​Endpoints summary

​Troubleshooting

​Next steps

Applicants

Cards

Quickstart

API Reference

What gets shared?

Get your integration settings

Option A — Seismic-hosted verification

Option B — Bring your own identity provider (BYOK)

Applicant response fields

Endpoints summary

Troubleshooting

Next steps