Skip to main content
You’ll need an Apocor API key (client_id + client_secret). Your Apocor 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.
cURL
Proceed only when status is APPROVED and issuerKycReady is true. See the KYC integration guide for BYOK share tokens and direct document upload.
In sandbox, applicant names containing DENY or REVIEW trigger those mock outcomes.
4

Set up an account and cardholder

Your program and account are provisioned in the Apocor dashboard. Use those ids here, then turn the approved applicant into a cardholder.
cURL
5

Issue a card

cURL
To show full PAN/CVV:
  • Default: GET /v1/cards/{id}/secure-details → short-lived revealToken, then load Apocor Widget.js (/sdk/card/...) and call widget.bootstrap (PAN never hits your servers).
  • PCI DSS Level 1: POST /v1/cards/{id}/payment-details → RSA-OAEP + AES-256-GCM envelope you decrypt with your private key.
Full guide: Viewing card details (PAN / CVV). Endpoints: API Reference → Cards — reveal PAN/CVV.

Next steps

Authentication

API keys and bearer tokens

Cards

Freeze, activate, and reveal card details

KYC integration

Hosted verification, BYOK share tokens, and issuer readiness

API Reference

Card integration endpoints with a live playground