CardNexia
Book a demo

Developers

A focused SDK and API for card artwork workflows.

Embed the design experience in your app and connect it to your existing card program systems.

integration.jsIllustrative concept
// 1. Your backend: request a short-lived, scoped session
const session = await cardnexia.designSessions.create({
  program: "prg_debit_classic",
  customerRef: "opaque-ref-8f2c", // never a PAN
});

// 2. Your app: embed the editor with that session
CardNexia.mount("#card-studio", { session: session.token });

// 3. Your backend: verify signed webhooks
app.post("/hooks/cardnexia", verifySignature, (req, res) => {
  // design.status: "review_required" | "approved" | …
});
Illustrative only. Names and shapes are not a committed public API.

Integration concept

Six steps from sign-in to handoff

  1. 01Bank

    Bank authenticates its customer.

  2. 02Bank backend

    Requests a short-lived, scoped design session.

  3. 03Client app

    Embeds the CardNexia editor with the program template and constraints.

  4. 04CardNexia

    Submission creates an opaque design ID and an asynchronous review state.

  5. 05Bank

    Receives a signed status webhook or polls the status endpoint.

  6. 06Production path

    The approved asset becomes available to the authorized production handoff path.

Illustrative endpoints

The shape of the API

Not a committed public API

MethodPathPurpose
POST/v1/design-sessionsCreate a short-lived, scoped editor session
POST/v1/designsCreate a design draft
GET/v1/designs/{id}Read a design and its status
POST/v1/designs/{id}/submitSubmit a design for checks and review
GET/v1/reviews/{id}Read a review outcome
POST/v1/webhooks/testSend a test webhook to your endpoint
POST/v1/production-handoffsStart a handoff (issuer-authorized only)

Example status machine

Every design has one clear state

draftsubmittedscreening
review_requiredapprovedrejected
handoff_pendinghanded_offacknowledged

Approval must be authorized by the configured institution workflow. Only approved designs move on to handoff.

Error and cancellation states are documented separately.

Security and reliability

Built into the integration

Security & governance →
  • OAuth/OIDC or signed service tokens
  • Tenant scoping
  • Ephemeral editor session
  • CORS restrictions
  • Webhook HMAC signatures
  • Idempotency keys
  • Replay prevention
  • Signed asset URLs
  • Observability
  • API versioning

Developer content

Documentation on the way

Everything below is on the roadmap and not yet published. Until then, we'll walk your team through the integration directly.

  • OpenAPI referenceRoadmap
  • SDK install guidesRoadmap
  • React integrationRoadmap
  • Sample sandbox appRoadmap
  • Webhook verification examplesRoadmap
  • Bureau adapter schemaRoadmap
  • Test vectorsRoadmap
  • Error taxonomyRoadmap
  • ChangelogRoadmap

Talk it through with our engineers.

Bring your app architecture, card program systems and production route.

Request technical walkthrough