Integration concept
Six steps from sign-in to handoff
- 01Bank
Bank authenticates its customer.
- 02Bank backend
Requests a short-lived, scoped design session.
- 03Client app
Embeds the CardNexia editor with the program template and constraints.
- 04CardNexia
Submission creates an opaque design ID and an asynchronous review state.
- 05Bank
Receives a signed status webhook or polls the status endpoint.
- 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
| Method | Path | Purpose |
|---|---|---|
| POST | /v1/design-sessions | Create a short-lived, scoped editor session |
| POST | /v1/designs | Create a design draft |
| GET | /v1/designs/{id} | Read a design and its status |
| POST | /v1/designs/{id}/submit | Submit a design for checks and review |
| GET | /v1/reviews/{id} | Read a review outcome |
| POST | /v1/webhooks/test | Send a test webhook to your endpoint |
| POST | /v1/production-handoffs | Start a handoff (issuer-authorized only) |
Example status machine
Every design has one clear state
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
- 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
