Paynovus Card Management API

The Paynovus Card Management API exposes a curated set of endpoints for card and account operations through the Paynovus CIP platform.

What is this service?

This API gives integrations direct access to card and account operations through the Paynovus CIP platform. It is designed for authenticated integrations that need to verify service health, confirm their account setup, and manage individual accounts and cards.

Where to start

This site has two sections:

• Documentation (you are here) — explains the concepts, the auth model, the tenant scoping rules, the high-level flows, and how errors surface.
• API Reference — every endpoint on its own page with request method, parameters, example bodies, responses, and a Try it widget.

Use the Documentation to understand how things work, and the API Reference when you're ready to call a specific endpoint.

Core capabilities

Area	What it covers
Account identity	Self-introspection of the authenticated partner account.
Individual Accounts	Onboarding and listing of account-owned individuals, plus their cards and logs.
Cards	Card lifecycle, restrictions, replace/resign, sensitive operations, and limits.
Fees & Delivery	Country delivery methods, issuing-fee and delivery-fee checks before card issuance.

Current stage

Stage	Status	Scope
1	Live	Health check, account identity, account-owned individuals, shared card endpoints.
2	Planned	Additional business-oriented endpoints and broader account coverage.

Environments

Service	URL
Docs (staging)	https://docs.card-management-staging.paynovus.com
API (staging)	https://api.card-management-staging.paynovus.com
Docs (production)	https://docs.card-management.paynovus.com (planned)
API (production)	https://api.card-management.paynovus.com (planned)

All endpoints are mounted under the /api prefix, e.g. /api/partner/me, /api/partner/individual/accounts.

Production environment

All code examples in this documentation use the staging API base URL (https://api.card-management-staging.paynovus.com). Production credentials must be requested separately.

High-level architecture

Client context                CIP-Backend                          IT-Card
┌─────────────────────┐                ┌──────────────────────┐            ┌──────────────┐
│ ES512-signed JWT    │ ──── /api ──▶ auth middleware        │            │              │
│ iss = Partner.url   │        │       │   ├ decode + verify  │            │              │
│ sub = Partner._id   │        │       │   ├ load Partner     │ ──── proxied ──▶│ card ops   │
└─────────────────────┘        │       │   └ hydrate req.user │            │ client ops  │
                               │       │                      │            │ account ops │
                               │       │ assertPartnerCard   │            └──────────────┘
                               │       │ Ownership /         │
                               │       │ assertPartner       │
                               │       │ IndividualAccess    │
                               │       │   └ 4xx on miss     │
                               │       └──────────────────────┘

Next steps

• Getting Started — Make your first authenticated request
• Authentication — Understand JWT generation and key setup
• Errors → — How errors are shaped and how to handle them
• API Reference → — Browse endpoints by area (Partner API, Individual Accounts, Cards, Fees & Delivery)