Skip to main content
NextGen is under active development. Capabilities and API reference content are being added regularly. If something you need isn’t documented yet, contact your Onboarding Manager: the capability may already exist and simply not be written up.
Welcome! You’re about to build on Enfuce’s next-generation card issuing platform. This page gets you oriented: how the platform fits together, how to get access, and how to make your first API call.

​
How It Works

1

Get oriented

Read this page for the core concepts, then browse the capability guides below for the areas relevant to your card programme (cards, cardholders, PIN, wallets, transaction lifecycle).
2

Get sandbox access

Contact us to discuss our products, or speak with your Enfuce contact if you’re already a customer evaluating NextGen. You’ll be issued a Client ID and Client Secret for the sandbox/UAT environment, along with your first programId.
3

Authenticate and explore

Use the Authentication guide to obtain an access token, then start exploring the API reference against sandbox data.
4

Agree scope and build

Work with your customer Onboarding Manager to agree your card programme configuration (your card programs, spend control rules, and webhook/data-file subscriptions) and build your integration against the sandbox environment.
5

Go live

Once testing in sandbox is complete, your Onboarding Manager will provision your production credentials and program IDs and guide you to live card issuing and transactions.
6

Manage and monitor

In production, manage your card programme through the API, the MyEnfuce portal, webhook notifications, and scheduled data files for reconciliation, reporting, and BI.

​
Core Building Blocks

NextGen’s data model is intentionally lean. Three entities cover most integrations:
  • Program: A pre-configured set of rules. Enfuce creates one or multiple programs based on your business requirements. A program determines a card’s type (credit/debit/prepaid) and behaviour throughout its lifecycle. Identified by programId, which differs between sandbox and production.
  • Cardholder: The person a card is issued to. Holds identity, locale, and address data, and can be associated with one or more cards. KYC/PEP/sanctions screening happens on your side before you create the cardholder record with Enfuce.
  • Card: The payment instrument itself: plastic, virtual, or tokenised into a digital wallet. Each card has a unique cardId and PAN, and is linked to a cardholderId and an accountId.
Where does the account balance live? Unlike a traditional issuer-processor setup, NextGen is ledger-agnostic: Enfuce can enforce spend controls and perform fraud monitoring, but your own ledger (or a ledger partner’s) holds the account balance and responds to Enfuce’s authorisation requests. The accountId you pass when creating a card is a reference to that ledger account, not an Enfuce-managed entity. See the Transaction Lifecycle guide for how Enfuce and your ledger interact during authorisation, transaction events, and clearing.

​
Make Your First API Call

A minimal integration looks like this:
1

Authenticate

Request an access token via OAuth 2.0 Client Credentials. See the Authentication page for the full request/response example.
2

Create a cardholder

Call the Create Cardholder endpoint tied to a card program with a customerNumber you assign, plus locale and address. The response returns the cardholderId you’ll use next.
3

Create a card

Call the Create Card endpoint with your programId, cardConfigurationCode, accountId, and the cardholderId from the previous step. See Card Creation via Endpoint for the full set of configuration options.
Both the cardholder and card are created immediately and available for use as soon as the request succeeds, with no batch delay.

​
Environments

Each customer receives two environments, sandbox/UAT and production, each with its own token endpoint:
  • Sandbox/UAT: https://auth.[TENANT].ext-uat1-sandbox.mycore.enfuce.com/oauth2/token
  • Production: https://auth.[TENANT].eu.live.prod.mycore.enfuce.com/oauth2/token
Your Onboarding Manager will share your tenant-specific credentials and program IDs.

​
Explore by Capability

  • Cards: Create, configure, and manage the full card lifecycle: plastic, virtual, and tokenised. (Guides · API reference)
  • Cardholders: Cardholder configuration and record management. (Guides · API reference)
  • PIN: Set, change, and view card PINs. (Guides · API reference)
  • Wallets: Digital wallet provisioning (Apple Pay, Google Pay, Samsung Pay) and token lifecycle management. (Guides · API reference)
  • Transaction lifecycle: Authentication, authorisation, and clearing, and how to configure your ledger to respond to Enfuce. (Guides · API reference)
  • Test API: A sandbox simulator for recreating transaction lifecycle scenarios to help you build before going live. (API reference)
  • Spend controls: Rules and rule sets to control how and where cards can be used. (Guides · API reference)
  • Exchange rates: FX rate lookups to support EU Cross-Border Payments Regulation compliance. (Guides · API reference)
  • Issuer fees: You can configure the following types of fees (Guides):
    • CASH_FEE: Applicable for cash withdrawals
    • ATM_FEE: Applicable for ATM transactions
    • MARKUP_FEE: Fee applied in cross-border or foreign-currency transactions

​
Query These Docs from Your AI Assistant

This documentation is also published as a Model Context Protocol (MCP) server, so an AI assistant can search these pages directly and answer with links to the ones it used, instead of you searching them by hand. The endpoint is https://nextgen-docs.enfuce.com/mcp. It is public and requires no credentials. Add it to your assistant in one of two ways:
  • Command-line agents (Claude Code, Codex, and similar): run npx add-mcp https://nextgen-docs.enfuce.com/mcp
  • Desktop and web assistants: add the same URL as a custom connector in your assistant’s settings, then enable it
Once connected, ask a documentation question, such as which parameters the Create Card endpoint requires, and your assistant queries these pages and cites the ones it drew on. Every page also carries its own set of actions, listed in the table of contents beside the page:
  • Ask assistant: put a question to the built-in assistant without leaving the page
  • Open in ChatGPT and Open in Claude: send the current page to that assistant and continue the conversation there
  • Connect to Cursor: add this documentation to Cursor
  • Copy MCP server URL and Copy MCP install command: copy the values you need to connect the MCP server described above
  • Copy page: copy the page as Markdown to paste into any tool
The server is read-only and covers published documentation only. It has no access to your program configuration, credentials, cardholders, or card data, and it cannot call the API on your behalf.

​
Get Help

  • Onboarding Manager: Your primary contact for program IDs, configuration codes, and environment credentials during implementation.
  • Contact us: For new integration or sandbox access enquiries.
  • Release notes: Track what’s new as NextGen documentation and capabilities expand.